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

help-circle

  • At some point I exceeded 500, but I also have firefox simple tab groups (formerly known as panorama) so I’m usually not looking at a window of more than 100 at a time, and any tabs I haven’t visited since last launch aren’t loaded into ram until I click over to them so they behave more like bookmarks except instead of creating/organizing/cleaning up bookmarks in addition to tabs I just browse/organize/close tabs. Each rabbit hole I go down gets a tab group so if I’m done with a topic I can just close the whole group.



  • The only realistic thing that the NDA could have contained was stipulations around leaking details about Threads. Who cares. Some admins probably wanted an inside look so they agreed to not leak any details. That does nothing to put their instances under the control of Meta. Yeah sure the admins are “controlled by the contract”… to not share any secrets about Threads. Again who cares.

    People dreaming up scenarios about the NDAs including clauses that let Meta control instances or their admins are delusional. As someone working in tech I sign NDAs all the time when I visit my friend’s companies. It doesn’t mean they have any control over me besides stopping me from leaking stuff that I see inside the company.



  • Random thought related to gold, but I wonder if it would be feasible to make some kind of fediverse tipping system that allowed people to give tips that showed up as something gold-like or award-like. Could be neat, but validating the payment when multiple instances are involved could be challenging without getting instances involved with payment gateways and finance regulations. I’m sure it could be done with crypto but that would probably be offputting to most people.







  • Yep, having a bunch of front page posts complaining (not trying to put it harshly) about the content just makes it look like the problem is worse to outsiders and doesn’t help perceptions. Let people talk about what they want, but vote accordingly and people will get tired of talking about reddit as less and less people engage with those posts. This post being here is causing more reddit-related engagement. Upvote the kind of content you want to see and it’ll rise up higher, becoming more visible and creating a virtuous cycle of positive engagement.

    Likewise, my only time spent on reddit is to upvote reddit drama discussion. Doing so will help push people who are “just tired of the drama and want to post” to find the fediverse a more enticing place to participate in.




  • When I say bidirectional disconnection I’m talking only about directly between the defederated instances in question since some people are suggesting that the instances are still directly sharing content in one direction. In your example the instances are still bidirectionally cut off, you’re just suggesting that a third instance could relay content between them. That would be theoretically possible but I don’t think it works like that currently, because that idea gets shot down in Mastodon for several reasons, including the fact that trusting content relayed to you from an intermediate server could open up the possibility of the relaying instance tampering or impersonating user accounts or faking content.


  • Yes this, and I could totally see the startrek instance growing into a hub for sci-fi related communities for example. More important than whether we are spread out is that the possibility and capability we have to spread out or migrate instances keeps instances in check by ensuring they don’t have leverage or lock-in over the communities. Currently I think the main risk is communities living on 1 instance, but better instance migration tools would mostly mitigate that - imagine if you could migrate a community (which in underlying activitypub terms is very similar to a user account) to a different instance, the same way mastodon accounts can migrate between instances and keep followers.


  • This is the correct answer, lots of people think defederating is one-directional when it’s not. It’s 100% blocked communication both ways, meant to be the nuclear option as a last resort (sadly the lack of other moderation tools makes it a second resort after reaching out to the other instance).

    If defederating still allowed any communication, it wouldn’t be useful if a remote instance was malicious and exploiting protocol-level bugs and trying to exploit other instances. Defederating should protect against that too, hence 0 communication whatsoever.

    The uni-directional option would be limiting a remote instance, which unfortunately isn’t implemented here.




  • The only tragedy I see here is that there aren’t more granular tools to allow beehaw to create the space they want without needing to deferate wholesale. But I agree, user choice is a critical part of the fediverse, and that includes the choices of instance admins. We should try to avoid fragmenting the community not by criticizing differing moderation styles and trying to force everyone to federate, but by making a gradient of moderation tools that allows admins to curate their spaces how they want without having to resort to the nuclear option, which sadly seems to be just about the only option in Lemmy’s moderation toolbox, which has never been stress tested like this before so it’s neither Beehaw’s fault for using the hammer they have, nor is it Lemmy/kbin dev’s fault for spending their time working on features that the previously miniscule community needed. The onus is on us to work with the devs to communicate where the deficiencies are and to help them bring moderation tooling up to speed , similar to the wide range of tools available to mastodon admins.

    That imo is the way to move forward and fix things here