 FediDB is an essential service to the fediverse, and while I appreciate the success, I do understand the need for redundancy, transparency and continuity. We should have multiple FediDBs, and they should be able to ingest/process/relay data accordingly. So I'm going to build this, later this year once I catch up with Sup, Loops, PubKit and Groups. 4 comments
@_elena Good question! So for software listings/stats, I have to manually curate the software list to prevent issues, for example, WordPress and some other fediverse software will use distinct identifiers which could pollute the software list by including single user Wordpress servers. I have an idea on how to fix this, by creating a github repo with a json file containing the software info, we can make this a community effort, and maintain an up-to-date list without my approval  @dansup thank you for the thorough explanation! I had been wondering about that⦠And thank you for all the brilliant work you do for the Fediverse @dansup I keep meaning to see if I can build some interesting fedi interop with Fluvio. It's architecture should be really well suited to relay data ingest with stats processing. Just need to get through our latest launch and have things settle down a bit so i can learn more about fedi data protocols. https://github.com/infinyon/fluvio Disclaimer: i work on building fluvio but need to know a lot more about fedi internals |
Gregory's Server
@dansup Iβm super grateful for your work on FediDB - I consult it daily π
Quick question: how come there are no stats about Piefed? Is it because it is still technically in beta?