• 0 Posts
  • 41 Comments
Joined 4 months ago
cake
Cake day: November 5th, 2024

help-circle


  • People get these confused a lot, but russia has 2 coups in the 90s-

    1991 was a failed anti-reformist “left wing” coup that deposed Gorbachev and ended with the fall of the USSR and Yeltsin in power.

    1993 was a successful right wing self-coup that allowed Yeltsin to fully consolidate power away from the Russian parliament and towards the presidency. More hamfisted and violent, but in essence similar to what is happening in the US right now

















  • Yes, and I’ve been yelling at them about the problem of scaling down for a while, since the same “relay” service needs to be both a firehose and a full mirror. This requirement (and thus scalability) of running a relay is becoming a big problem even for the main devs. According to them however you can mitigate this to a reasonable amount for a home lab (~8 cores, 16gb ram, ~2Tb ssdl) if you simply don’t store any backlog and just retransmit posts https://bsky.app/profile/why.bsky.team/post/3lbjdux6ubc2f

    This is what they’re doing internally to manage the load and are also working on implementing relay sharding/scoping to let you just index a small slice of the network, which should eliminate the problem. https://github.com/bluesky-social/atproto/discussions/3036 and here’s someone implementing a proof of concept third party version https://bsky.app/profile/pet.bun.how/post/3lbwnx2rxxs2o

    It’s true that the main devs’ priorities are building the large scale parts first and then worrying about downscaling, the whole point was always to replace twitter and work at a similar scale, which requires hard tradeoffs. I do worry that they’ll run out of money before they can do the work to let the ecosystem become sustainable by itself.

    But I have faith (for now) because they have people I know from when they worked on secure-ssb and dat protcols, which are truly decentralized but never took off for other reasons.