Nerd about the fediverse, based in Portland, Oregon. 🌲 Nice to meet you! 👋
Blog & Podcast: jaredwhite.com
On Mastodon: @[email protected]
I’m squarely in the AT protocol is not the Fediverse camp. Fine if people want to enjoy Bluesky, but the Fediverse is built on top of the W3C protocol ActivityPub. AT is incompatible. Cool that there’s a bridge, but a bridge between incompatible protocols will always be a bit of a hack in my book.
I’m totally fine with the SWF engaging with Meta just like they would any other entity building software using ActivityPub.
Funding on the other hand is a different story. It sounds like Meta contributed to an overall fund in order to launch the SWF. OK, I suppose — but if there’s specific funding down the road for some specific project or funding in some way which appears to influence decision-making on which projects to work on or how to approach them, that’s when I have a huge problem with it.
My hot take is that short-term posture doesn’t matter all that much. If you have bad posture but you get up every 20 minutes and stretch/do chores/exercise for 5-10 minutes, you probably erase the original issues.
My one-two punch, if you’re looking for advice: make sure you use a chair that makes good posture easy, with your keyboard+mouse & monitor height well separated on your desk (if computing’s the main thing you’re doing as you work). And then make sure you’re getting a lot of activity throughout the day. Spans of 2, 3, 4, etc. hours just sitting at your desk will be really bad for you, no matter how good your posture is.
I guess what I’m saying is if you can either focus a lot on posture or focus a lot on physical activity routines, prioritize the latter. But both are certainly important.
Some things never change…
Yeah, that’s not remote, that’s on-call. 😅
You seem to be incorrectly stating what is on Wikipedia, which leads:
That last bit is absolutely key: a collection of services using a common protocol. Imagine if two different email servers didn’t both speak SMTP. Imagine if two different web services didn’t both speak HTTP. The Internet as a singular entity is only made possible because of protocol interop between all of its constituent parts.
To say “the fediverse” is comprised of multiple incompatible protocols goes against that grain, and to go back to pre-ActivityPub-as-W3C-specification days as an argument that it’s fine to label multiple incompatible protocols as all being components of “the fediverse” is a stretch.
To me, this isn’t a let’s-agree-to-disagree-issue, honestly. While the term “fediverse” is arguably colloquial and doesn’t necessarily imply any specific technical attributes, it ceases to be useful as a term if Fediverse Platform A cannot in any way communicate with Fediverse Platform B because the two platforms happen to be using 100% incompatible protocols. Aside from a third-party bridge, the AT protocol used by Bluesky is 100% incompatible with ActivityPub used by Mastodon, Threads, and others. Therefore, they cannot both be simultaneously services in the fediverse.