You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a non-ruby dev I'd love to hook into manyfold events, without messing up the codebase :)
So how to make it more hackable without overcomplicating a REST interface?
possible solution
I'd love to be able to respond to database CRUD operations (when a user is created/updated/deleted e.g.) or trigger an external process elsewhere on my server.
Perhaps turning database-table read/write/update/delete-calls into WebSub events can help keep the manyfold codebase/features small.
This allows many (less interesting) features to be developed outside of the codebase, shifting the burden of non-core maintenance elsewhere.
context / background
Matrix conversation:
<sqz> Hi James, thanks for manyfold.
Any thoughts on easy 'hooking' into events for non-ruby devs?
Does activeadmin support webhooks/cli-hooks or something?
afaik postgres has triggers/pg_exec(), but I was just curious if there's other ways.
<james> Hey sqz, you're most welcome! Event hooks is a really cool idea, I hadn't thought about it, but I love that sort of thing, so yeah...
could do something like websub, or atom feeds, or anything really
and of course there's already stuff in activitypub as well
Could I get you to open a feature request on GitHub with some ideas of what sort of things you'd want to get events for, and what sort of interface you might want?
WebSub is probably my ideal...
<sqz>
Haven't heard of WebSub..but after reading about it, it looks like a W3C-favored flavor of webhook subscriptions ❤
The text was updated successfully, but these errors were encountered:
I'm thinking about how this fits alongside and complements ActivityPub, and security.
If we assume websub, then you get a publish event with a URL; Then you can use the REST API to get any extra data you want. I don't want to be leaking out inaccessible data over less secure channels, so that makes sense in that it provides a way of getting a "ping", but you still need credentials to get the actual data. We could also allow the use of public hubs, we wouldn't necessarily need to send secure data in the event.
The implementation of that is actually really easy... hmmm.
Agreed.
ActivityPub is great for 'hey this person made this public thing' (to the world).
Getting "pings" is enough imho, because as an admin you have access to REST/filesystem/database anyways.
problem
As a non-ruby dev I'd love to hook into manyfold events, without messing up the codebase :)
So how to make it more hackable without overcomplicating a REST interface?
possible solution
I'd love to be able to respond to database CRUD operations (when a user is created/updated/deleted e.g.) or trigger an external process elsewhere on my server.
Perhaps turning database-table read/write/update/delete-calls into WebSub events can help keep the manyfold codebase/features small.
This allows many (less interesting) features to be developed outside of the codebase, shifting the burden of non-core maintenance elsewhere.
context / background
Matrix conversation:
The text was updated successfully, but these errors were encountered: