Auto-import of deny lists
Technical Discussion
7
Posts
3
Posters
48
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
-
@silverpill@mitra.social Oh, it seems to ignore the proof part.
-
@hongminhee It only includes the standard AP context. Do you have a workaround for that as well?
-
@silverpill@mitra.social Yeah, it seems!
-
-
@reiver I'm the last person to recommend against CBOR, but if querying is what you want and you're not on embedded, why not store your JSON-LD data in HDT?
-
I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.
https://j12t.social/@j12t/114581086678041245
...
I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.
CBOR might actually be a way of doing that.
...
For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.
#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD
-
@astro@c3d2.social well I certainly don't want to give you work! Please don't worry too much about it.
The FASP concept is good but sounds technically difficult to implement, so I'm a little wary of it at the moment. I'm a fan of simple APIs especially for public data.
-
@julian @evan If I provided them, I would probably implement https://github.com/mastodon/fediverse_auxiliary_service_provider_specifications/blob/main/discovery/trends/v0.1/trends.md but haven't done so yet. Is that suitable for you? If so, I should do it soon.
