I write articles and interview people about the Fediverse and decentralized technologies. In my spare time, I play lots of video games. I also like to make pixel art, music, and games.

  • 52 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: November 30th, 2023

help-circle

  • Hey, thanks for asking! It largely boils down to money, people, and time. I’m currently a full-time student, and struggling to stay afloat.

    Here’s all the things I currently do:

    • Research / Testing (gathering info for stories, tracking down info for sources, testing apps and platforms)
    • Writing articles, interviews, guides, and reviews.
    • Content Editing pieces submitted by contributors
    • Scheduling for Podcast interviews
    • A/V Production
    • Podcast Distribution
    • Music Promotion
    • Graphic Design (thumbnails and such)
    • WordPress development (features and data)
    • Social Media Management (11+ accounts)
    • Instance moderation
    • Event coverage
    • Manage a Contributor Team
    • Fundraising
    • System Administration

    I’m probably missing a few things. It’s a lot! And, while I’ve been able to balance this out for a long time, my severe burnout has seen diminishing returns. I’m at a point where articles are getting finished days and even weeks after something has happened, which… isn’t great.

    All of this stuff is more or less being done for pennies an hour. It’s not sustainable.






  • The list of shout-outs in the main announcement pertains to projects who have partnered with the SWF, and intend to support it and collaborate.

    It’s also worth keeping in mind that there are more than 80 different platforms in varying states of development. Yeah, Lemmy is one of the bigger ones, and OG Threadiverse, but the list of platforms to name is absurdly long at this point. I think it makes sense for them to focus on the protocol, and immediate partners.












  • Good question. For now, we have a basic process for submitting icons, which requires adding details about the project repo, information on the icon, and Copyright attribution for whoever created / owns the brand.

    We recently incorporated a JS library that allows us to generate the font from the SVG files themselves, which also builds the preview pages that can be viewed at icons.wedistribute.org. With a bit of extra automation on Codeberg, we could basically update the preview page and generated set every time a new icon gets merged in to the main branch.

    Our goal is to get to a point where new releases automatically get created, and an archive of the assets gets attached as well. That way, once a milestone gets completed, a new release will get put out with minimal amounts of work.




  • Interesting insights!

    The original reason we started this was actually for our own development. Our site includes project icons and colors in dedicated tags, which link to dedicated topic hubs. As we started working on this, we realized that there wasn’t a really good resource, and that we would have to build something from scratch.

    Those symbols that you see are typically Unicode. Icon fonts are generally a CSS hack, in that a collection of SVGs have been converted into a font. The Unicode strings can be thought of as “letters” for that font. You’re absolutely right that there are accessibility limitations, but the tradeoff is that people get an easy way to use their favorite project icons to represent where they are on the Web.

    At the very least, you won’t have any uBO problems with our site, as the font is incorporated directly into the theme we’re using. We’ll likely explore making a WordPress plugin next, so people can add these to their profiles and menus and other places.






  • Not yet, but it doesn’t seem like it would be too hard to add in support for that. I think one of the core ideas here are that you could take NeoDB and use it as a foundation for any review system you want to integrate. Hook up to a service on the search side, support data import on the backend, suddenly you have a way to not only create the reviews, but populate the objects being reviewed with the necessary metadata.



  • I agree with you in spirit, but some of this stuff needs to be spelled out for people interested in the space. Not every person that builds for ActivityPub is overly aware of technical and cultural expectations. A lot of that knowledge exists in someone’s head somewhere, and the Fediverse does a pretty poor job of making assumptions about those people.

    Case in point: one of the stories linked in the piece discusses a guy that implemented ActivityPub on his own, got it to work, but didn’t know enough about the space. People thought it was a crawler, turns out it was a blogging platform, but the drama ignited to the point that someone remote-loaded CSAM on the dude’s server using Webfinger. Dude was in Germany, and could have gone to prison simply for having it.

    We can’t hold two contradictory positions, where we invite people to build for this space, and then gaslight them over not knowing things that nobody told them about. More than ever, we need quality resources to help devs figure this stuff out early on. This article is one small step in service to that.







  • I wrote a counter-point to this a while back: https://wedistribute.org/2024/05/forking-mastodon/

    I’m not saying “don’t do it”, but realize that the amount of commitment required to make a hard fork even moderately successful is vast.

    It’s telling that the biggest project in the space is barely able to pay more than a handful of people to work on it, and it still develops at a snail’s pace. Notably, those are the people who deeply understand the system and its internals. While it’s not impossible, you have to be realistic about how much further a group can get when they don’t have the insight or technical chops required to take development further.