Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

What is the biggest reason that makes you hesitate to adopt ?

OptionVoters
ActivityPub protocol seems too complex8 (14%)
Not familiar with TypeScript/JavaScript ecosystem13 (23%)
Lack of documentation or tutorials6 (11%)
Integration with existing systems looks difficult7 (12%)
Performance/scalability not proven5 (9%)
Security and stability concerns2 (4%)
Debugging/testing appears challenging3 (5%)
Insufficient community support3 (5%)
Too much time required for learning8 (14%)
Team/company resistance to adopting new technology2 (4%)
Sean Tilley's avatar
Sean Tilley

@deadsuperhero@social.wedistribute.org · Reply to Fedify: an ActivityPub server framework's post

@fedify For me, the hard part is actually knowing how to work with the wider JavaScript ecosystem. Fedify itself seems pretty easy to work with, but as someone newer to JavaScript, picking the parts for backend, frontend, and middleware is overwhelming.

Nordnick 🐘's avatar
Nordnick 🐘

@nick@hhmx.de · Reply to Fedify: an ActivityPub server framework's post

@fedify@hollo.social

[X] Using a different / own approach 😉

Mahmoud - محمود عبدالجواد's avatar
Mahmoud - محمود عبدالجواد

@mahmoudajawad@mastodon.online · Reply to Fedify: an ActivityPub server framework's post

@fedify where is "I don't have time to do it" option? Also, TIL one can post such a lengthy poll.

Maddy's avatar
Maddy

@maddyunderstars@aus.social · Reply to Fedify: an ActivityPub server framework's post

@fedify Personally I just enjoy doing it myself. Fedify is a great project and I will happily use it for anything new, once I'm sick of writing it from scratch myself lol

just small circles 🕊's avatar
just small circles 🕊

@smallcircles@social.coop · Reply to Fedify: an ActivityPub server framework's post

@fedify

First option I'd describe as:

protocol seems deceptively easy, while actual wire reality is full of prohibitive complexity.