I am currently winding down the Mastodon bots I used to post sunrise and sunset times. The precipitating event is that the admin of the instance hosting the associated accounts demanded they be made nigh-undiscoverable, but the underlying cause is that it’s become increasing clear that Mastodon isn’t, and won’t ever be, a good platform for “asynchronous ephemeral notifications of any kind”. I’d also argue (more controversially) that it’s simply not good infrastructure for social networking of any kind. There are lots of interesting people using Mastodon, and I’m sure it will live on as a good-enough space for certain niche groups. But there is no question that it will never offer the fun of early Twitter, let alone the vibrancy of Twitter during its growth phase. I’ve long since dropped Mastodon from my home screen, and have switched to BlueSky for text-centric social media.

  • Blaze (he/him) @lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    2
    ·
    4 days ago

    If lemmy-federate goes down, we’re back to square one.

    No, because Lemmy-federate is only supposed to be used as a “first subscriber” for a community.

    Once there are other subscribers to that community from the remote instance, then the lemmy-federate could go down, the federation would still be in place.

    Example

    • !funny@sh.itjust.works is first federated thanks to lemmy-federate to my instance (dbzer0)
    • I see that community and subscribe
    • Lemmy-federate goes down
    • As I am still subscribed to that community, dbzer0 still federates that community