Some people think that privacy, openness, and user consent are all at odds with one another. Here's a guide on how to navigate all three as a developer.

Sometimes, developing a new app, platform, or concept for the Fediverse can seem like a minefield. Here’s some rules of thumb on how to maintain goodwill with the community, and ideas of how to do it.

    • Sean TilleyOPEnglish
      3•5 months ago

      Google Fonts

      Yeah, I need to work on that. It’s been on the back burner, because writing and publishing has kind of been a main focus for me in recent months. But, this hasn’t been the highest priority, mostly because modifying WordPress and making it behave correctly can be a massive pain in the dick.

      I’ll get around to it when I’m able.

  • AliceEnglish
    -2•5 months ago

    Be transparent. An honest. That’s all? You don’t need a fucking article dancing around that

    • Sean TilleyOPEnglish
      2•5 months ago

      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.