Just passing through.

  • 4 Posts
  • 222 Comments
Joined 5 months ago
cake
Cake day: April 24th, 2024

help-circle




  • A lot of people use Mastodon as an RSS feed where they can leave comments. This would basically allow you to subscribe to the content of a writer, and get it full-form straight in your feed.

    I could also imagine following artists on Pixelfed, throwing money in their tip jar to keep posted on their newest creations.

    I think there’s a lot of potential here. But monetisation is always tricky on the internet, of course.




  • Yeah, the pitchfork crowd manages to shut down everyone who tries to do something genuinely good for the community, while leaving all the bad actors running wild in the background.

    I mean, we always knew loud voices in the open source community were toxic as fuck - that’s obvious enough from the Linux mailing list. Giving these people their own social network to ruin was wildly optimistic from the beginning. It’s a wonder it hasn’t gone worse.

    It’s amazing how computer nerds posting on the fucking fediverse can be so sceptical of seeing their content leave the platform they’re currently on. Like that’s not the whole goddamn point of posting here in the first place.

    Also, Bridgy.fed rules. Anyone out there on Mastodon or Bluesky: Please opt in! :)





  • If I understand correctly, there’s a central pump running behind the scenes in any AT implementation. You feed content into the central hub, and it pumps it out to everyone connected to it. Bluesky itself provides the one major pump that feeds its network right now.

    So in that sense, Bluesky is a centralised network with decentralized users.

    Frontpage is building a different pump, spreading different kind of content to a different type of platform. So there’s no obvious connection between the Bluesky pump and the Frontpage pump - that’s why they’re talking about bridging in the post.

    It almost seems a bit silly - in order for two AT hubs to talk, you need to build a bridge for them. At that point, you could might as well have built an AP protocol and made it work with Bridgy.fed.

    Furthermore, all “instances” running Frontpage would process data through the same central hub. If that goes down or they run out of funding, it’s all over.

    I’m applauding the Frontpage crowd for trying something new. But I’m not entirely convinced I see the benefit compared to what we’re doing over here.



  • I think support for boosts is a game changer for interoperability. As a Mastodon user I wouldn’t really want to follow a community even if it was well implemented, but I’m happy to follow users who boost content I’m interested in.

    Boosting content is the way posts spread on Mastodon. If anyone follows me from Mastodon they will see all the content I boost; if they enjoy it, they might re-boost to their followers and the ball starts rolling. And that’s how you suddenly get comment sections where Mastodon users are actively participating.





  • I feel like dark theme is often tricky on different monitors - If the font is too heavy it’ll look awful, if it’s too light it might look bad on low resolution displays. Combined with different colour contrasts on different screens, and it gets really difficult to know what people will end up seeing.

    The headline - “MBIN SERVERS” - looks great on my 4K monitor, but slightly less good on a worse one. The same goes for the text stating that “Also view servers on FediDB and Fediverse Observer”, but it’s not so bad for the white text. The hyperlinks, however, might suffer from a lack of contrast with the background (a slightly too dark blue) combined with very thin text on low resolution monitors.

    I guess brighter hyperlinks could also benefit the names of instances.

    It’s not something I ever noticed myself when using the site, but keeping it in the back of my head while looking at it I can see why some might have some problems with it. :)