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.

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

Integrate with Fediseer tags #295

Open
db0 opened this issue Jan 19, 2024 · 4 comments
Open

Integrate with Fediseer tags #295

db0 opened this issue Jan 19, 2024 · 4 comments

Comments

@db0
Copy link
Contributor

db0 commented Jan 19, 2024

Fediseer is a service which allows instance admins to crowdsource and collaborate on instance management. One of the features it has is self-tagging of instances as you can see here.

The fediseer also provides a full REST API anyone can use to retrieve this data.

I want to suggest that instead of hardcoding instances to the the various topics as seen here, you use the tagging functionality to retrieve and discover instances.

If you want to have specific topics only, you could then incentivize the admins to tag their instances with the names you're looking for. For example to retrieve all instances self-tagged as technology: https://fediseer.com/api/v1/whitelist?endorsements=0&guarantors=0&tags_csv=technology&page=1&limit=100

Alternatively this would allow you to set up a cascading selection to allow people to discover smaller instances. For example AI might be under technology. So someone clicking on technology, will see all instances tagged as technology but then see also potential filtering for AI, FOSS, Renewable Energy etc.

Likewise, an instance could natively appear under more tags. For example lemmy.dbzer0.com might appear under Politics > Anarchism, Technology > AI, and Neurodivergence

This will help discoverability of smaller instances without forcing the owners of this repo to constantly keep it updated with new instances manually.

@dessalines
Copy link
Member

I don't know that we'd want to rely on an external service for the instance list. I'd be happy to link it from the top of that page if you'd like. Feel free to make a PR for that.

@Nutomic
Copy link
Member

Nutomic commented Jan 23, 2024

I think this makes sense because the instance list from fediseer is much more actively maintained than the one in joinlemmy. It would also reduce our workload as we wont have to manage the list anymore, or think about including/excluding specific instances. Additionally we could easily list only trustworthy instances using a minimum number of endorsements received, or requiring endorsements from a hardcoded list of trusted instances.

Anyway someone would have to be willing to implement this.

@dessalines
Copy link
Member

That looks too overkill for our purposes (especially hierarchical tagging). Also we might not want to host everything that's on fediseer.

@db0
Copy link
Contributor Author

db0 commented Jan 24, 2024

You don't have to. You can choose to display only guaranteed instances and with potentially more than X endorsements. You can disallow instances that specific other instances have censured, etc. The idea is to crowdsource the maintenance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants