cultural reviewer and dabbler in stylistic premonitions

  • 183 Posts
  • 573 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle









  • Python does have a year option that they are not using.

    No, it doesn’t:

    help(datetime.timedelta)
    Help on class timedelta in module datetime:
    
    class timedelta(builtins.object)
     |  Difference between two datetime values.
     |
     |  timedelta(days=0, seconds=0, microseconds=0, milliseconds=0, minutes=0, hours=0, weeks=0)
     |
     |  All arguments are optional and default to 0.
     |  Arguments may be integers or floats, and may be positive or negative.
    



















  • with BlueSky I’d have to account for the data volume of all users on the platform as a whole, bringing the data volume way up to tens of terabytes

    I think this is a common misconception based on some critics’ incorrect assumptions and back-of-the-envelope math. See the atproto overview for the different components involved, and then this post (from a BlueSky employee) “A Full-Network Relay for $34 a Month” for some numbers.

    If I understand correctly, to run a “full nework relay” does mean to consume all of the text posts from all known servers, but not necessarily all of the media, and not necessarily to keep data you aren’t interested in for any long period of time.

    Also, you can run your own PDS and/or App Views without running your own relay at all. And, you can also use multiple other people’s relays.

    Disclaimer: I’m not an atproto expert, and I haven’t set any of this up myself.






  • The blog post also says this:

    There is one other thing which Bluesky gets right, and which the present-day fediverse does not. This is that Bluesky uses content-addressed content, so that content can survive if a node goes down. In this way (well, also allegedly with identity, but I will critique that part because it has several problems), Bluesky achieves its “credible exit” (Bluesky’s own term, by the way) in that the main node or individual hosts could go down, posts can continue to be referenced. This is possible to also do on the fediverse, but is not done presently; today, a fediverse user has to worry a lot about a node going down. indeed I intentionally fought for and left open the possibility within ActivityPub of adding content-addressed posts, and several years ago I wrote a demo of how to combine content addressing with ActivityPub. But nonetheless, even though such a thing is spec-compatible with ActivityPub, content-addressing is not done today on ActivityPub, and is done on Bluesky.

    My comment should have been clearer; what I meant when i said it is more “decentralized architecturally” I was referring to the data model part of the architecture as opposed to the physical server infrastructure currently operating it. The latter is obviously quite centralized still, but the former is designed for resilience against nodes unexpectedly (and permanently) failing.