• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle










  • I agree, but there’s a non-zero chance I don’t have a full picture of things yet, and maybe things aren’t that bad. Or won’t be that bad.

    On the surface, inconsistencies like this seem like they might encourage users to group themselves on a few massive servers that have a lot of local content guaranteed to be consistent rather than spreading themselves across many small instances (power law graph goes here.)

    But maybe not. I don’t know. Maybe the system naturally converges toward clusters of interests where each instance is primarily focused on a few things, and while the federation mechanism exists and is mostly useful, it is a secondary feature behind a primary use-case where folks preferentially engage with their local communities.

    Overall, I wonder how much of all this is colored by expectations we’ve developed while using Reddit.
    All this fediverse stuff is built on very different foundations than things like twitter or reddit, and while it’s easy to gloss over it because the UIs look superficially similar, they’ve made some fundamentally different trade-offs.

    But maybe the consistency stuff could get better over time too. Maybe there’ll be a smoother experience to better flag when and why things are inconsistent (“instance X hasn’t sent us activity updates since T”, “instance X has partially defederated from us”, etc.), and maybe even offer targeted palliative measures rather than a generic disclaimer.
    All this stuff is under fairly active development still, so there’s hope.


  • Welp, I’m new too, but I think this is more or less working as intended.

    The federation mechanism is a “best effort” thing, so there’s literally no guarantee that you’ll get the same view for the same thing loaded through two different instances.

    I started writing a userscript to “normalize” URLs so clicking on a link to kbin.social on a different instance would transform the link URL to keep you on your original instance, but with the distinct possibility of missing content because of it, I’m not sure it’s actually a good idea.

    The auto-refresh-and-btw-lemme-close-the-image-you-were-looking-at behavior isn’t happening on every instance, but it definitely happens on lemmy.world. Maybe this is an artifact of the websocket approach, and that’ll go away in 0.18? No idea.

    At this point, the usage pattern I’m leaning toward is to find good communities/magazines, subscribe to them, and stick to the “subscribed” view. The most consistent results will always be with subs that are local to the current instance, so if most of your subscriptions are on instance X, you probably don’t really want to have your account on instance Y.


  • There have been efforts to build reputation systems that don’t rely on central servers, like early day bitcoin’s Web of Trust, which allowed folks to rate other folks with public key crypto, thus ensuring an accurate and fair trust rating for participants, without the possibility of a middle-man putting their thumb on the scale.

    One problem with it is that it was still perfectly practical for bad actors to accumulate good ratings, then cash out their hard-earned reputation into large scams, such as the “Bitcoin Savings & Trust” (for $40 million in that particular case), which quite possibly made it measurably worse than not having a system that induced participants into making faulty judgments in the first place.

    I think the main practical value of something like reddit’s karma is an indication of age and account activity, both of which can probably be measured in other, if less gamified ways.