Auto-import of deny lists
Technical Discussion
7
Posts
3
Posters
46
Views
-
NodeBB has a very simple allow/deny list capability at present. You paste in a bunch of newline-separated domains, and we block (or optionally, only allow) them all.
On the road to more fine-grained controls, I discovered that IFTAS publishes a Do Not Interact list in an importable CSV format.
As maintenance of these lists is important (adding new entries as well as handling removals), it looks to be increasingly important that I add into NodeBB the functionality to follow these lists automatically and update as necessary.
-
The problem with the CSV format, is that it doesn't tell you what was removed, only the current state of the data, so you'd need to store previous CSV files to detect removals by diffing new versus old.
-
@julian you might want to check out what GoToSocial does on this front -- it seems very well thought out
-
This is not an issue if you are rebuilding the instance wide deny list every time it is updated.
In that case, whenever the list is rebuilt any removed entries will simply not appear in the new list.
-
julian in which case you loose anything you manually needed to add. We've had so many conversations about this..
-
thisismissem not necessarily, I'm planning to build this out as a separate collection of CSV lists, in addition to a list you manually curate. 🙂
-
Just spend the tiny bit of extra time and implement basic support for federation policies. Keep track of data snd where it comes from, such that you can react to changes over time
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
I'd generally discourage RFC7591 in decentralized systems due to the fact that it creates client sprawl (this is currently a problem with Mastodon's client registration mechanism, which is why we created CIMDs) — every client in RFC7591 is a distinct client, with its own client_id and client_secret, which can make client management interfaces difficult to implement (e.g., every time you login on a mobile device or SPA, you'll get a brand new client_id). CIMDs solve this by anchoring client metadata to a URI, and using that URI as the client_id.
If you need to test clients using CIMDs in development, there is cimd-service however, it's currently targeting the AT Protocol ecosystem (so has a few specifics that at present there that would not necessarily make sense of ActivityPub)
-
@reiver@mastodon.social add in NodeBB as well. Markdown first, and probably HTML too, although it will probably be sanitized to death on the way out.
-
@mariusor that's too bad. All I have left is mussels, French fries, large-scale bureaucracy, and peeing statues.
-
@reiver #WriteFreely uses Markdown by default too, but of course sends out HTML to the fediverse
-
@reiver Markdown or its subset is supported by almost every platform except Mastodon.
But PeerTube is the only software I know that puts markdown in content instead of HTML.
-
@evan I lived in Burssels for some many years, you won't tempt me with beer. 😈
-
@mariusor let me ask, what are your opinions on beer?
-
@evan yes, this is the one, I realized I already added it to my ticket list: https://todo.sr.ht/~mariusor/go-activitypub/337
