Emelia 👸🏻 @thisismissem@hachyderm.io
Public

Okay, FIRES reference server 0.5 is now out, this will probably be the last release before 1.0.0

This release contains the ability to import changes into a dataset from a mastodon, fediblockhole or domain-only CSV file, helping people migrate to using FIRES for datasets.

If you've historical copies of your CSV files, you can import each version and any missing rows will be detected and retractions will be suggested for those domains. I've already tested this out with some versions of the @iftas DNI denylist (thanks @jazjaz :twt: :wales_flag:!)

It also obviously includes the datasets, changes API and snapshot API from version 0.4.x, which was quietly released 10 days ago.

Docker image: github.com/fedimod/fires/pkgs/

Changelog: github.com/fedimod/fires/blob/

Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

github.com · GitHub

0
0
2

If you have a fediverse account, you can quote this note from your own instance. Search https://hachyderm.io/users/thisismissem/statuses/115534983117929778 on your instance and quote it. (Note that quoting is not supported in Mastodon.)

Emelia 👸🏻 @thisismissem@hachyderm.io
Public

RE: hachyderm.io/@thisismissem/115

Another API endpoint I'm considering adding is snapshot deltas, so if you have a snapshot at change_id A, and you want a new snapshot with just changes since A, then you can download that delta.

It should be possible to implement, and would provide an alternative to retrieving all the updates since the initial snapshot & merging them into local state.

Part of the reason I'm thinking about this is to build a reference consumer app, if I can, in the next two weeks

0
0
0
Emelia 👸🏻 @thisismissem@hachyderm.io
Public

RE: hachyderm.io/@thisismissem/115

One thing I'm currently a little stuck on is how to provide a backwards compatible export of data from a FIRES dataset. This would be a inherently lossy process since no domain denylist csv formats support retractions, and because FIRES supports more than just recommending blocking of domains.

I could provide a CSV export of just recommendation's for domain entities, and leave it to the consumer to manually apply retractions, but this feels kinda wrong.

Interested in people's thoughts.

0
0
0