cultural reviewer and dabbler in stylistic premonitions

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

help-circle






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


  • ok, but, does ActivityPub have portable identity and/or content addressability yet, so that when some of those servers (which are often hobbyist-run and/or tenuously funded) inevitably cease operating their users can continue on a different server? 👀

    It’s a rhetorical question, and the answer is no.

    otoh, atproto’s PLC DID method is also not really decentralized… but at least the rest of their system is actually substantially more decentralized architecturally than AP is.

    To anyone interested in reading a very informative in-depth discussion of this topic, I recommend the blog post How decentralized is Bluesky really? by ActivityPub co-author Christine Lemmer-Webber (followed by this and this).






  • fuck google generally, but in this case that mastodon post’s characterization that “Respondents overwhelmingly reject the suggestion” is not accurate - lots of people in that thread are in favor of removing it and those who aren’t aren’t making a strong case to keep it.

    imo client-side XSLT never needed to be implemented; afaict its primary use is styling RSS feeds and I doubt many people ever actually read RSS feeds styled that way even if millions of feeds are/were.

    some important context here

    tldr: This obscure “feature” is a significant source of vulnerabilities which attackers are able to compromise endpoints with right now. The GNOME project’s libxslt is used by all modern browsers and has been largely unmaintained for a long time, and it is a pretty sure bet that it has lots more remotely-exploitable bugs (in addition to those which have already been discovered and not yet fixed, or for which fixes are not yet widely distributed).

    it sounds like there is also a mostly-working JS replacement for this C++ code; if it is actually possible to ship that and avoid breaking any sites it would be preferable, but, otherwise, i for one would certainly be in favor of dropping browsers’ XSLT support (which was only ever for XSLT 1.0 anyway!) completely ASAP.






  • Huh? That press release quotes the The Environment Agency’s Director of Water and National Drought Group chair saying “Simple, everyday choices – such as turning off a tap or deleting old emails – also really helps the collective effort to reduce demand and help preserve the health of our rivers and wildlife” and includes “Delete old emails and pictures as data centres require vast amounts of water to cool their systems” in its list of ways people should save water at home.

    I admit I made this post without clicking through to the actual press release or seeing more than the paywall preview of the article; for a humorous post like this, i think just the headline from a paywalled article (if it’s from a reputable source) is sufficient. Now that you got me to read the actual press release, I see I was correct to assume that 404media’s amusing headline was in fact accurate.

    How would you suggest they report this story differently? Highlighting the ridiculous part is what makes it worthy of reporting on it in their context at all.




  • With the Mac SE and II, the switched to ADB, which looked like a PS/2 port, but you could daisy chain your mouse, keyboard, and other inputs like tablets or joysticks all into one jack in the back of the computer.

    The port looks similar - both are mini-DIN - but ADB has four pins while PS/2 has six.

    ADB was first introduced in 1986 on the Apple IIgs, and later was used in all Macs from the SE until the iMac. For the first few years there were two ADB ports, but in 1990 (maybe starting with the Mac IIsi?) they reduced it to one and started shipping keyboards with ports to daisy chain the mouse from.