• 0 Posts
  • 30 Comments
Joined 7 months ago
cake
Cake day: September 24th, 2024

help-circle




  • Both things are technically true: the article is primarily made up of content literally written by the company or people contracted by them for PR purposes, and it is a Good Article (Wikipedia jargon for having passed a review of certain quality standards around writing, coverage and sourcing, but not the higher standard required to be classed as a Featured Article).

    How much of a problem this is probably depends on the subject. Does Juniper Networks have any bad practices which the article omits because the people who researched it (i.e. Juniper Networks) didn’t think they needed to go in the article? You’d basically need an independent observer to research anything that potentially should be in the article but isn’t there, but how many people that aren’t getting paid are invested in researching a corporate networking business?

    There’s absolutely merit to Wikipedia having articles that are written by people paid to write them by their subjects, because a lot of it would otherwise be missing from Wikipedia entirely. But it’s also good to know that many articles are not necessarily written by impartial authors.










  • Everyone else took all the good critiques of this article, so here’s mine.

    We’re still bullish on the fediverse, and on Bluesky, if it manages to become a truly federated platform.

    Bluesky appears to have reached their goal as far as federation. Users can self-host a personal data server (PDS) which federates with Bluesky. If you want an analogy from somebody extremely unqualified to offer it, it’s sort of like bringing a bucket of water to a swimming pool. You can’t go swimming in the bucket, but you can pour it into Bluesky’s pool and swim in there. If the pool closes down or implements segregation and if somebody else opens a swimming pool, you can take your bucket to their pool instead. However, if nobody else wants to open another swimming pool, your bucket is useless. In this analogy, buckets are only useful to very slightly fill somebody else’s swimming pool and for no other purpose. It’s a very good analogy.

    Bryan Newbold, the protocol engineer at Bluesky, said the following about PDSes and federation:

    Overall, I think federation isn’t the best term for Bluesky to emphasize going forward, though I also don’t think it was misleading or factually incorrect to use it to date. An early version of what became atproto actually was peer-to-peer, with data and signing keys on end devices (mobile phones). When that architecture was abandoned and PDS instances were introduced, “federation” was the clearest term to describe the new architecture.

    i.e. In Bluesky’s terminology, federation is not a future goal they’re hoping to achieve, it’s what they’re already doing right now.

    The (ActivityPub) fediverse is different, because … damn, I really screwed myself with this swimming pool thing … it’s like a bunch of boats in the ocean. There’s one-person dinghies and giant cruise ships, all with different owners. You can bring your own boat, or you can hitch a ride with a friend or a generous stranger. If you want to hang out in a different boat from the one you arrived in, that’s fine too. Ultimately, we all float on the same ocean which we all have to share. Crucially, nobody is in charge of the water. There’s rules on the boats, but the ocean is just the ocean. If your boat crashes into an iceberg and sinks, the ocean will still be there. You might lose some of your stuff, but there’s plenty of other boats to pick you up.

    The failure state in both cases is better than nothing. With Bluesky, you lose the swimming pool, but keep the bucket. With ActivityPub, you lose the boat, but keep the ocean. If Bluesky dies, ideally you can take your federated identity with you to an alternative service that exists in the future, but you no longer have access to Bluesky, because it’s gone. When a Lemmy instance dies, you pretty much have to start over: register a new account, subscribe to all your communities again, etc. But the whole fediverse is still there: all the communities you were subscribed to, the people you followed, all your old comments, they’re still out there floating on the ocean.


  • It’s true this is a thing that you can do, but the experience seems pretty degraded vs. just registering an account with a Lemmy/Mbin/PieFed/Sublinks (did I miss any?) instance which is natively configured for the kind of threaded conversations that exist on this segment of the fediverse. The instructions basically amount to “Go to a Lemmy instance and use its interface to find a community you’re interested in, then copy the link to the discussion you want to interact with and paste that into your Mastodon instance’s search bar, then reply to the post that appears. It’s that simple!”

    If you only interact with threads occasionally or you just want to try it out from Mastodon, this is workable, but you need a lot of patience for the busywork that’s involved.






  • Maybe this is a me problem, but especially on the threadiverse side (Lemmy/Mbin/PieFed), how much are we really in tight-knit communities based on our servers? I’m from Fedia, but I don’t really interact with Fedia people any more than I do anybody else, or even bother to take notice of where other people are from, unless they say something especially goofy. Communities in the “subreddit” sense are more likely to feel tight-knit than servers

    I definitely get how allowing people to skip choosing a server is good for some types of potential fediverse users, I just don’t think Gmail works as an analogy for that. When Gmail was in its invite-only era, people weren’t paralyzed by choices of providers, they specifically wanted the one that was the best, and that was Gmail.