Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify FIRES non-relationship to FSEP / TBS #56

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify FIRES non-relationship to FSEP / TBS #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/blog/2023/2023-11-14-updates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ Nivenly has received a project application from Pachli, a fork of the Tusky Andr

Pachli’s complete application is visible [here](https://nivenly.org/docs/applications/pachli/). We’re sure both members and non-members have questions about Pachli! For members, since your questions are part of the governance process please put your questions [in the member only area of our Discourse](https://nivenly.discourse.group/c/nivenly-community/5). For non-members, please feel free to ask questions as well in [our Discourse’s public area](https://nivenly.discourse.group/c/nivenly-projects/7). To help us, and the head maintainer of the project, keep track of the question threads we’ve created both of the members-only and general public threads to kick off the discussions.
### FIRES (formerly known as FFS)
Nivenly is also sponsoring Fediverse Intelligence Recommendations & Replication Endpoint Server (FIRES), which is led and being built by Emelia Smith ([@thisismissem](https://hachyderm.io/@thisismissem)). For those who have been following her work, this is a rename of the same project formerly referred to as Fediverse Filter Server (FFS). Nivenly’s support for FIRES is two fold: both the initial technical proposal as well as the initial reference implementation.
Nivenly is also sponsoring Fediverse Intelligence Recommendations & Replication Endpoint Server (FIRES), which is led and being built by Emelia Smith ([@thisismissem](https://hachyderm.io/@thisismissem)). For those who have been following her work, this is a rename of the same project formerly referred to as Fediverse Filter Server (FFS). Nivenly’s support for FIRES is two fold: both the initial technical proposal as well as the initial reference implementation. The FIRES project is not related in any way to FSEP or The Bad Space, and is a completely independent proposal.

First: what is FIRES? FIRES is in part a response to feedback that there needed to be more nuance in moderation than simply allow and deny lists. Instead, the primary goal of FIRES is to provide the ability to subscribe to moderation advisories and recommendations that change over time. The moderation data will also be structured instead of unstructured - basically instead of a single text field, as is the experience today, the data will be highly structured and capture the full history of changes to moderation recommendations and advisories. This allows machines to better interact with the data of moderation recommendations and advisories, such that tools and user interfaces can be built to expose more data to moderators and end users alike.

Expand Down