I like to code, garden and tinker

  • 0 Posts
  • 39 Comments
Joined 9 months ago
cake
Cake day: February 9th, 2024

help-circle


  • 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.




  • Being an admin of an instance, I can’t even see my own history of visited posts. I can’t verify this, but I doubt this information is being stored in the database currently.

    This being said, each instance has full control over their API server and the web-based application being served, so they could add monitoring to either to gather this data. If they did this on the API end it would be undetectable. Running your own instance is the only fool proof method, otherwise you need to trust the instance operator.



  • Every field I’ve been in has these boxes distributed for pollinating. From the product page:

    There is no need for box returns and frame exchanges when cardboard nuc boxes are a fraction of the cost of wooden nucs.

    So it’s sold as a bonus that this does not need to be returned, so it’s common enough practice. I know they are suppose to be used to seed new boxes, but farmers generally don’t care. They want the flowers pollinated, the bees will probably die from the pesticides so no use in worrying about them.

    Edit: There is an article from the guardian on the harmful conditions bees endure on almond farms. I am near smaller farms, so maybe this practice (of using nucs to pollinate) is not as wide spread as I thought. Regardless, bees are routinely mistreated in various agricultural settings.