Open outlaw-dame opened 2 weeks ago
Currently fedionfire uses mastodon.social feed via API key, because for some reason fedi.buzz lags far behind. The whole point is to be real time. Haven't yet figured out how else would get more feeds combined... so it's basically anything mastodon.social gets federated.
Suggestions welcome.
At least in theory, you can open multiple event streams and instead of doing the magic directly in the EventListener (line 879++, move that to a common function that gets called from multiple event callbacks. Have not tried it to see if there are browser limitation on the amount of open connections.
Are you able to include content from bridgy fed? Mostr.pub and Momostr.pink
Bridges:
https://relay.fedi.buzz/instance/bsky.brid.gy
https://relay.fedi.buzz/instance/momostr.pink
https://relay.fedi.buzz/instance/mostr.pub
https://relay.fedi.buzz/instance/newsmast.social https://relay.fedi.buzz/instance/newsmast.community https://relay.fedi.buzz/instance/flipboard.social https://relay.fedi.buzz/instance/flipboard.com https://relay.fedi.buzz/instance/mozilla.social https://relay.fedi.buzz/instance/social.vivaldi.net https://relay.fedi.buzz/instance/me.dm https://relay.fedi.buzz/instance/twit.social https://relay.fedi.buzz/instance/moth.social https://relay.fedi.buzz/instance/threads.net
I know previous you were worried about admins resources. The instance relays I selected belong to companies and nonprofits that won’t encounter the issues like everyday admins.