Prismo △

@prismo
1.8K Followers
17 Following
260 Posts
Any visual artists (non-video for now) here up for becoming beta testers of Abelio? :) Hit me up or mention anyone who might be interested!

🚨 INTRODUCING: a new in-progress #rubyonrails #activitypub engine that aims to make it able to add AP features to any Rails app.

It's still a work in progress but i would really love to hear your feedback and ideas on that! Feel free to message me here or open a discussion on github repo.

See README for more details:

https://github.com/mbajur/activity_pub_app

PS: A new kind of AP service/app will be based on this, more info soon :)

#fediverse #development #ruby

GitHub - mbajur/activity_pub_app: Rails ActivityPub app. Soon to be extracted into a separate engine

Rails ActivityPub app. Soon to be extracted into a separate engine - mbajur/activity_pub_app

GitHub
Any name ideas for a tumblr/photoblog #activitypub alternative? #needhelp #fediverse #fedihelp

What's the most complete and handy #activitypub library out there? go-fed/activity ?

#needhelp #dev #federation

Looking for a libre tool to collaboratively archive huge amount of high-res photos. Preferably with ACL and a good API layer to be able to build something on top of that. Any ideas?

#opensource #libre #needhelp

@wraptile @bhaugen also, you totally can use graphql endpoint with curl. Its not gonna be easy for More complex queries but you totally can do that.

Ps. Graphql is never gonna be an official go-to api of prismo. Its gonna be a secondary one at most. I decided to try the C2S route as a primary one

@wraptile @bhaugen i think all the graphql apis i've been working with so far were totally friendly (say, github). Also, in terms of developer-consumer friendliness, IMO even the worst graphql implementation is nicer to work with than the Best rest api (given they both share exact the same amount of data). Especially that graphql auto-suggests fields and self-documents itself. But, if the implementation is bad, its not really graphqls fault
@bhaugen long story short: in GraphQL consumer has a full control over how returned data is modeled and structured. JSON:API enforces you to use it's predefined scheme. Also, it really suck to parse a JSON:API response when there are includes attached (even most of node.js clients does it asynchronically as a Promise)
@wraptile @bhaugen and also, graphql is not really reinwenting the wheel as there is no such wheel yet :) graphql is amazing thing designed to make you Able to fetch anything you want in a single query. I think you Just did not used it enough to appreciate its pros :)
@wraptile @bhaugen setting Keys and headers is not something graphql specific. Its a mechanism of authenticating the request, any api standard can (and actually should) utilize that