Bilbo Baggins

  • 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle

  • Every instance just needs to store the communities they use, just like now. But once cached, any other instance could grab those messages from any of those instances. It’d be a peer to peer sort of organization.

    I can think of lots of caveats regarding freshness of content and trust and ensuring the tree of instances is auto organized to minimize depth. Maybe for trust you could have signatures for all content signed using keys that every instance could pull from the original instance just once every now and then.

    Upvotes and responses would just travel up the tree in the reverse trip from the way content came down.

    But, I think it’s similar to other things that already exist. These problems seem solvable.












  • Totally agree about the amount of coordination overhead. That is a huge amount of time to do anything.

    But even so, it’s even slower, by a lot, once you pull the ripcord and need to keep the site working while you update it.

    Prior to release you don’t need to have branch and release then QA then deploy. You can just modify schemas and drop existing user data without needing to migrate anything. You can change the look of the interface without angering users who generally hate change.

    Just the cycle of releasing new features carefully is a ton of overhead.

    I’ve spent entire days just rolling out code to change which domain name is used to refer to some images because doing it quickly would overwhelm the image servers due to the caches being unpopulated. 100% of that would be unnecessary prior to going live.