• 1 Post
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle


  • Aesthetics are the same bogeyman excuse used to justify really any significant change in a phone since IP ratings first came in with. I recall back when USB-C was first showing up in smartphones, there was a time where simultaneously some manufacturers were pushing for the change and others trying to push back on it, with both groups citing aesthetic reasons.




  • Coming from reddit is fun app, I don’t really understand how what you’re proposing would work. You want the same functionality of having a separate account on each instance, but consolidated into one app to easy switch between accounts/instances, right?

    If we translate this use case into the existing rif app layout, the subreddit selector panel on the left would need to have like lemmy instances instead of subreddits, with communities nested under each instance.

    So you would have a different frontpage for each instance, which consisted of only the posts for communities hosted by that instance. Maybe I’m on the wrong track here, or you have a better idea of how it’d work.

    How is that better or more intuitive than just having one personal frontpage for all of your subscribed communities? That way you don’t even need to make a conscious decision to browse beehaw posts, they’re just in the same feed as everything else.

    I feel like it’s more about the way you’re thinking about posts being hosted on a particular server and what that means. In the context of Lemmy it only means something where the post you want is on an instance that’s been defederated from for whatever reason, and even then only in terms of community discovery. Otherwise it’s kinda meaningless in terms of your interaction with posts.

    Thinking of the given community as a community ‘on beehaw’ per se is only really pertinent in cases where the fact it’s on beehaw alone has some kind of impact on how you interact with it, e.g moderation style. But even in that case, moderation style could equally be an attribute you ascribe to the community itself, rather than beehaw. e.g. preferring r/games over r/gaming.

    This way it makes more sense to think of the community as a lemmy community than a beehaw one, which seems fairly intuitive to me. Plus, that way the instance is doing the link aggregation and not your phone, which would be problematic for users and for scaling the ecosystem


  • Yep the original post on the beehaw instance is like a master record of the post that lives on their server and only their users and users from federated instances can interact with it. Meanwhile the act of a lemmy.world user subscribing to a given beehaw community triggers the lemmy.world instance to archive posts there and create separate self-contained records of them which only lemmy.world users can interact with


  • Yeah, that’s federation. In terms of the principle in government as well as its application in the lemmy protocol.

    lemmy.world and beehaw.org are defederated. However, this doesn’t mean that you can’t see beehaw posts as a lemmy.world user, or vice versa. But (let’s say you’re a lemmy.world user) if you comment on a beehaw post, you’re commenting on a replicated version of the post that is hosted on lemmy.world. It is not synced with the original post hosted on beehaw, and you will only be able to see comments from other lemmy.world users and comments from before beehaw defederated.


  • Federation is by definition a union, a mutual agreement. A and B are either federated or they aren’t, there is no “A is federated with B but B is not federated with A”.

    So if A and B are federated and B and C are federated but not A and C, and your scenario happens, the person on B sees your comment but the person on C doesn’t see it and can’t reply to it.