Another traveler of the wireways.

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

help-circle
  • Alongside others mentioned (tags/flairs, multi-communities, keyword filtering, etc.) another feature I’d like to see added/improved is notification settings.

    Something like…

    In account settings:

    • Enable/disable all notifications.
    • Enable/disable post reply notifications.
    • Enable/disable comment reply notifications.

    For others’ posts/comments and per posts/comments:

    • Enable/disable post reply notifications.
    • Enable/disable comment reply notifications.

    With those settings you could more easily tune out all notifications or only opt into those you’d like to see, and opt out of those you’re done with (say your post/comment got popular and you’ve had your fill from the replies).


    Unrelated to notification settings, it would also be nice to be able to block communities from the front page via the … More menu in the default web UI.















  • I think a better title & question would be, “Why is Mastodon struggling to thrive?”

    It’s surviving no problem, but it’s not thriving for a multitude of reasons. Some are pretty well covered across comments here & in the linked discussion, and are more or less reiterations of prior discussions on the matter.

    Ultimately I think as much as many of those reasons are correct, the biggest reason is the same as ever: network effects. All the jank and technical details could be endured and adjusted to if there was sufficient value to be had in doing so, i.e. following accounts of interest/entertainment, connecting with friends, etc. That’s proven to varying degrees by those that have stuck with Mastodon. In turn, however, it’s also clear by how many bounce off that for many there’s still insufficient value to be found across Mastodon instances to justify dealing with all the rough edges.

    If Mastodon had enough broadly appealing/interesting people/accounts across its instances, people might deal with the various technical and cultural rough spots the same way they deal with similar on other social networks they may complain about yet won’t leave. There still aren’t enough of those sorts on there for many though, so Mastodon simply survives but doesn’t thrive.


  • Yes but no. Due to architectural differences, federation under AuthTransfer protocol is simply different compared to ActivityPub. In its own terms it is federated as individuals’ data is stored in personal data servers (PDSs) connected to a relay, which currently is only the Bluesky relay, that roughly speaking connects them to other personal data servers.

    You can technically operate your own personal data server apart from those operated by Bluesky, but I think it’s fair to say the vast majority on there don’t. It’s not clear yet, apart from fully holding your own data, how useful it is to operate your own given you only have one relay to use anyway at the moment.

    So even in its own terms Bluesky really isn’t federated in much of a meaningful sense yet. The problems are twofold: a major part of their pitch is making federation Just Work™, keeping the underlying tech out of mind to mitigate confusion, but you can’t have your cake and eat it too here. Eventually, if you’re really committed to meaningful federation, you have to teach people about the value of operating their own personal data servers, at minimum, otherwise what was the point in separating it out in the architecture?

    Problem is, that goes against their pitch to their audience and spoils the appeal. It’s telling a good joke only to kill it by explaining to the one person that went, “I don’t get it.”

    Secondly, they’ve already upfront said that relays may be cost prohibitive for many people to operate, resulting in only a few ever being spun up. If that remains the case and is true, then even if a few were spun up, that’s not any more federated or distributed than the rather consolidated web we see now. How much of a difference would it make if the social web was running on AuthTransfer and the major relays were owned and run by Meta/Facebook, Twitter/X, and Google?

    Congrats you have your own data in a personal data server…But are you really the one running it, or did you just opt into the PDS entryway offered by Facebook/Twitter/Google/etc. because sorry, what’s that about a server?







  • This is buried toward the bottom of the release notes so I’m bringing it up here:

    Added instance-level default sort type

    Any admins out there considering changing their instance sort settings or asking people on their instance if they’d like this changed, given that we can individually set sorting anyway? Taking into account the inclination of people to never adjust default settings (I remain deeply curious about this tendency, as an aside), I think it might be worth at least bringing up to one’s instance community.

    If they decide they want it to remain the same, all good, and even better, it raises some people’s awareness that they can change it themselves.


  • I think while some of this may be people being people (i.e. tendency to only discuss issues/problems vs accomplishments/solutions), I think there’s also a technical element to it as well in Lemmy’s case.

    Up to the latest release of Lemmy (as of writing this is v0.19.4), admins couldn’t adjust the default sort setting, which was Active. Read the docs on the sort setting and Active does what it says, surfaces those posts with recent commenting activity (taking into account score as well).

    So you get this unfortunate mix of: people gravitate to discussing negative stuff, people tend not to change default settings (since despite defaults being Active, we can change these if so inclined), and the default sort settings surface whatever is being most discussed/commented on, resulting in this sort of negativity feedback loop you’ve observed.

    I noticed and posted about this a few months ago, have tried to upvote and comment on less negatively-focused posts occasionally, but I think this may be an interesting example of a small scale systemic issue as it takes more of us doing similar to address what’s being encountered. However, as more instances update to v0.19.4, I’ll be interested in seeing if admins decide to switch away from the Active sort setting to try to address this in their own way.

    I don’t know what sort setting may be better for instances to run with instead, but I’m glad they now have the option. In the meantime I think it’s worth reminding people that they currently have the option to change their default sort settings to something different to try to see different kinds of posts. Personally I switch between New and Scaled to see a variety of posts beyond many of the regular doom and gloom posts.