• Head admin @ lemm.ee, a general-purpose Lemmy instance
  • Creator of lemmy-ui-next, an alternative Lemmy frontend
  • Lemmy contributor

ko-fi

  • 2 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • Regarding your question:

    Lemmy federation basically works by copying stuff from their source instance to all other federated instances. So if I write a comment on lemm.ee, other federated instances will get their own copy of my comment. They will also all know that the “authority” for this comment is lemm.ee.

    If an admin on another instance decides to delete their local copy of my comment on lemm.ee, then they are always free to do so (for example, some instances might want to moderate more strictly), but any actions they take like this are limited to their own instance - for the rest of Lemmy, lemm.ee remains the authority for this comment, so individual remote instance admins taking actions won’t have any effect on any other instances.

    As for the original topic of modlog federation, basically it just boils down to this: just like with the comment example above, Lemmy instances also save a local copy of incoming federated mod logs. The Lemmy software does not yet have 100% coverage in terms of federating mod logs (for example, there are no federated logs yet for instance admins banning remote users), but this coverage has been increasing, and I expect this will eventually get to 100% (just needs more dev time really).

    Also, if some instance admins try to tamper with their mod logs, then other instances can still see the real history, because there is no way for an instance admin to delete copies of their mod log from other instances.



  • Most actions federate, any exceptions which aren’t federated yet are generally just there because the federation logic has not been implemented (but improvements are constantly being worked on).

    Generally federating the modlog is mostly just there for informative purposes. As in, we can check what mod actions were taken on instance A through the modlog on instance B (and there is no mechanism in Lemmy for other instances to retroactively remove or hide federated modlog items, btw).



  • IMO, in practical terms, 3 key things should imapct instance choice:

    1. Basic instance rules (including things like community creation policy, nsfw allowed, etc)
    2. Federation policy
    3. Instance infrastructure (hardware & how it’s managed)

    Content specialization really shouldn’t matter IMO, because as long as the federation policy is OK for you, then you can participate in any communities, regardless of what instance they are on. In other words, even if you’re super interested in french cinema, there is no need to centralize all users interested in this topic on a single french cinema instance. Thanks to federation, users from all instances (accounting for federation policy) should be able to become fully fledged participants in any french cinema communities.

    Of the points I listed above, #1 and #2 are easier to include in an instance introduction, I’m not sure how to properly and reliably reflect #3 in any kind of overview. At the end of the day, I think most users tend to figure out their long-term home instance a while after they first join Lemmy, and quite often, it’s not their original instance, so maybe it’s not that important to emphasize the initial instance choice too much?



  • Sorry if you were just making a joke, my sarcasm detector is not really working anymore (/s at the end would help). But if not, this comment really perfectly captures the entitlement in open source.

    Now imagine you spend months (or even years) of your free time to build something for people to use freely, and the result is that you get endless comments from random strangers, telling you that you work for them and that you need to respect and be grateful to them. I honestly am impressed that open source still exists at all at this point.


  • I just want to add a counter-point to the argument that Lemmy devs are somehow opposed to contributions. In my experience, there has been no resistance to contributing any type of change (I have personally added niche features for running Lemmy in a distributed manner, optimizations, bug fixes, etc). In fact I would claim the complete opposite - I have received plenty of support and good code reviews from maintainers whenever I have wanted to contribute anything.

    I think there is truth to the claim that Lemmy maintainers don’t have a lot of patience for people making demands and snarky comments, but that is very different from being opposed to contributions. Also, after running a big instance for a while now, I completely understand this lack of patience - when some of your users just keep being rude to you, it wears down your patience. It’s easy to patiently and kindly respond to the first 100 rude users, but at some point after that, it just becomes gradually more mentally exhausting, to the point where it’s basically impossible.

    Even the example provided in the blog post: I don’t think snowe had bad intentions, but I do think they had clearly misinterpreted the situation with that issue, and their comments were needlessly condescending.


  • sunaurus@lemm.eetoMildly Infuriating@lemmy.worldLemmy posts redundant
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    6 months ago

    I think the OP is talking about Lemmy having both a content preview and a text area for link posts.

    Some users tend to write their own summary in the text area, so when opening up a post, the result will be:

    • Large title written by the OP
    • Automatic preview of the page, generated by Lemmy
    • Text summary of the page, written by the OP

    I agree that this is a bit clunky in terms of UX


  • Honestly… it’s not great. I would not recommend it unless you’re playing with somebody who is not put off by constant bugs and general jank.

    In terms of bugs, I’ve had several occasions where one player can no longer open the map - it just starts opening the quest log instead of the map. I’ve also had a few occasions of the screen just going completely white. Also, I’ve had a player just become locked in a dialogue with no way of exiting.

    For an example of jankiness, one key aspect of the whole game, dialogues, is just completely awful:

    1. Both players can begin separate dialogues at the same time, one just gets muted
    2. It’s impossible to automatically begin a dialogue with two players, one player has to start it, and the other has to “listen” to it as an additional step
    3. It’s impossible to switch control of dialogues during a dialogue. This is constantly an issue, because sometimes, dialogues are triggered when you walk past some invisible checkpoint. Basically you’re forced to always have your high charisma player to walk in front and hope they end up triggering all the dialogues.
    4. It’s impossible to contribute to dialogues in any way as the “listening” player. Even if you have some aspect to your character that might provide an interesting line, you are just locked out.
    5. If both players speak to a character in succession, the exact same dialogue gets repeated. It’s jarring and completely breaks immersion.

    There’s more, but I’m kind of getting more and more annoyed at the game as I write this, so I think I will just stop here, you probably get the picture 😅

    I think the co-op is a complete afterthought in this game, and I will probably be replaying it in single player for a hopefully better experience at some point.



  • I think it works best if you have a lot of screen real estate. My sweet spot is around 5120x1440p (either ultrawide or two monitors) with about 5 desktops. I never overlap windows and it works amazingly for me.

    I used to do this with Gnome, nowadays I use the exact same workflow in Mac OS, and I feel super productive with it. I haven’t used alt tab in about a decade now 😃

    For me, it only works with good keyboard shortcuts for the following:

    1. Quickly moving between desktops (for example, super + <desktop number>)
    2. Quickly moving windows between (for example, super + shift + <desktop number>)
    3. Quickly snapping windows to areas in the current desktop (for example, super + arrow keys)