I like to code, garden and tinker

  • 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: February 9th, 2024

help-circle

  • Centralization is a weakness. These services can be targeted by governments that want to limit communication. Free speech is a commodity, and servers host this free speech. If a hostile organization, such as a government, targets a channel of free speech such as those hosted on a platform that makes it easy to setup a mastodon instance, this become an easy target that will affect a large portion of users. If you are serious about freedom, you have the freedom to self-host your own platforms.



  • My question is, why give it for free? Has their product developed enough to win in the AI developer space? Are we reaching the point where you could self-host an AI code assistant as good as copilot? Or are projects such as johnny.ai (renamed, I’m not going to advertise it) challenging Microsoft’s market share in the AI developer space?

    My only guess is Microsoft wants you to get used to their ecosystem and further ingrain developers into their development ecosystem. At best, once you are used to their ecosystem you’ll stick with them out of familiarity. At worst, they can use your input (prompts, refactors, etc) to further the development of copilot.

    To me this smells of typical subsidizing of a product to capture market share then lock in that market share. Anything I’m missing?

    Edit: johnny.ai seems to be a domain offered for resale by godaddy. I didn’t mean to link them but I’ll leave it here, don’t give godaddy money as they are a terrible domain name registrar.




  • Just the act of refusing makes the act of seizing your phone legal or not. If you legally give them your phone by your own will, they are able to use all evidence they find in the courts. If you deny to give them your phone, and they seize it anyways and access it you have a valid path to throw the evidence they discover out as an illegal search and seizure of your property. I’m not a lawyer but that is the general thought process on denying them access to your property.


  • I personally rather trust that my device isn’t able to be unlocked without my permission, rather than hope I am able to do some action to disable it in certain situations. The availability of such features is nice, but I would assume I would be incapable of performing such actions in the moment.

    My other thought is, how guilty is one perceived if they immediately attempt to lock their phones in such a matter, by a jury of their peers? I rather go the deniability route of I didn’t want to share my passcode vs I locked my phone down cause the cops were grabbing me.












  • As for the data transfer costs, any network data originating from AWS that hits an external network (an end user or another region) typically will incur a charge. To quote their blog post:

    A general rule of thumb is that all traffic originating from the internet into AWS enters for free, but traffic exiting AWS is chargeable outside of the free tier—typically in the $0.08–$0.12 range per GB, though some response traffic egress can be free. The free tier provides 100GB of free data transfer out per month as of December 1, 2021.

    So you won’t be charged for incoming federated content, but serving content to the end user will count as traffic exiting AWS. I am not sure of your exact setup (AWS pricing is complex) but typically this is charged. This is probably negligible for a single-user instance, but I would be careful serving images from your instance to popular instances as this could incur unexpected costs.