• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle

  • A custom made Google Sheet to track everything - maintenance, repairs, insurance, and fuel ups. I’d like to move to an app that supports all of the above, but getting everything into an importable format was messy (tried it with Fuelio), and I gave up after a while. The fact that I’m also writing down parts purchased prior to installation does not make this easier.

    My plan is to try and convert it all into plaintext accounting format (probably Beancont with a tailor-made plugin), but so far I’ve been mostly kicking that ball down the street.



  • Exactly. The issue is with the source of electricity, not with the AC itself. Not to mention that leading by example is nice, but it’s not always the best course of action. An individual avoiding AC is a drop in the water, and not going to save the planet, while suffering immensely. Hell, even if every single individual stopped using AC at home (which isn’t even close to reality), that wouldn’t have a significant effect, compared to what corporations, factories, etc. are doing.


  • Yep - and in that case, what you interact is, is your instance. You have no direct interaction with the Threads server, whatsoever. Your instance pulls that content (which is publicly available!), and shows it to you. If you comment on it, you do so on your instance, and it federates that comment back to the Threads instance (where the data federated is publicly available - it’s the content of your comment, and your handle). There’s nothing malicious going on here.

    That’s not to say that something bad can’t happen in the long run. E.g., if people get used to content from Threads, and then Threads suddenly stops supporting ActivityPub (or forks it with negative changes), many people might be lured to start using Threads in order to keep accessing its content. That’s definitely a potential issue. But the technical side of federating with Threads is absolutely benign.