@julian are there any plans to add #RSS support to #NodeBB?
Fediverso
7
Post
4
Autori
13
Visualizzazioni
-
-
@pfefferle you probably want to tag @julian@community.nodebb.org instead of @julian@activitypub.space
-
@pfefferle you probably want to tag @julian@community.nodebb.org instead of @julian@activitypub.space
thehole@dasforum.org both work 😁 I have push notifications turned on for both.
-
pfefferle@mastodon.social there is, actually! It was something we added over a decade ago.
Just add
.rssto any topic or category URL (no slug). -
pfefferle@mastodon.social there is, actually! It was something we added over a decade ago.
Just add
.rssto any topic or category URL (no slug).pfefferle@mastodon.social it does occur to me that there's no UI for it anymore. We can consider adding it back.
-
undefined Piero Bosio ha condiviso questa discussione
-
@julian fair enough, just expected you not to see it due to your profile text 😅
-
-
here's a side-project we might work on. writing up what a *good* RSS feed coming from a social network would look like.
they all seem to rush through it and often leave out one crucial bit. if we just wrote up a simple profile they probably would all just do it that way.
interested??
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@julian Congrats on ActivityPub.space btw- made an account. Looks cool.
-
@julian All I did was make both /actor and /relay accepted follows from /actor, going through the issues in their repo and you showing me the resolver page is what made me try it. https://github.com/yukimochi/Activity-Relay/issues/90
-
incentive@mastodon.circlewithadot.net so what was the issue, a bug in Activity-Relay?
The LitePub section on FEP-ae0c: Fediverse Relay Protocols: Mastodon and LitePub is pretty vague about deviations from expectations. It would be good to shore up this FEP a bit.
-
@julian Confirmed! "relay-server | INFO[0263] Sent MutuallyFollow Request : https://activitypub.space/actor
relay-server | INFO[0263] RelayState reloaded "🤝
-
-
@julian I rebuilt the docker image with some changes in resolver - you're welcome to try again in the meantime if you wish - if not I can return to this tomorrow :)
Appreciate you looking into this with me.
-
incentive@mastodon.circlewithadot.net The code suggests that when parsing the follow request, it's checking object and ensuring that it is one of:
https://www.w3.org/ns/activitystreams#Public It's own ID (so, https://relay-us-east.circlewithadot.net/actor)NodeBB is sending https://relay-us-east.circlewithadot.net/actor, so it should satisfy that constraint, but I am not sure where in the Activity-Relay code it is failing out.
