Post · bonfire.cafe

The master list of PieFed instances is retrieved from the fediverse.observer API. Then an API endpoint on every instance in the list is queried to see if they opted in and to get information about the instance that fediverse.observer does not have.

This happens once per day.

Instance admins can choose to filter out any other instance and defederated ones are automatically filtered.

Tim Chambers

@tchambers@indieweb.social replied · 2 weeks ago

@rimu @renchap The idea that it is built into the UX of every #piefed server itself is also interesting.

Renaud Chaput

@renchap@oisaur.com replied · 2 weeks ago

@tchambers @rimu Yes it is, but I am worried about letting users pick their server from any server that opt in. You really want users to go on *well-managed servers* and avoid servers that depend on a unique person (high risk of the server disappearing), without proper moderation or correct operation practices. And that is without even without discussing about bad actors starting to exploit this.

Tim Chambers

@tchambers@indieweb.social replied · 2 weeks ago

@renchap @rimu For Mastodon I could imagine it being those that signed the Server Covenant, and in my original straw man idea I suggested other site quality metrics….(uptime over last X years, etc) https://docs.google.com/document/d/18kmf-WKenzmyGLIhQ2NUHa8kz-K9yrVwBtZ3rGpmVPA/edit?usp=drivesdk

Renaud Chaput

@renchap@oisaur.com replied · 2 weeks ago

@tchambers @rimu The server covenant is purely declarative, I think that if we start sending the general public to a pool of servers there needs to be more checks here. But we have ideas in this area that I hope we will soon be able to make progress on.

Tim Chambers

@tchambers@indieweb.social replied · 2 weeks ago

@renchap @rimu Great! Happy to help any way I can 👍

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.0-rc.2.21 no JS en

Automatic federation enabled