Upgraded. All went pretty smooth. Good job peeps!

Very nice

It’s an ongoing spam wave

The denuvo cracker? You follow her recommendations?

Technically I’m from digg

Still 404 on my end

They did run a revolt server for a while, but they apparently had to revert back to discord for reasons.

I’m getting a 404

EAC is heaxbear, confirmed!

Omg that logo. GoL is a hexbear confirmed!

That’s not how copyrights work.

[…]Looping through the list you’ve been given, and making extra queries adds complexity and delay, when the expectation from the user is that this list should appear pretty quickly.[…]

While you’re correct about this, this could be handled dynamically. Simply fetch the list of posts quickly as usual, and then start polling for crossposts in the background and if any two appear in the current frontpage the user is seeing, merge them.

My counter to that, would be that if you aren’t using the API in the way the developers expected, your app has ceased to be frontend, and is instead its own program that’s scraping data from it.

Not at all. That’s not what scraping means.

I just completely disagree with the idea that a frontend should stick to what the backend design is, especially for a FOSS project.

Frontends generate the main feed by querying api/v3/post/list. This doesn’t provide any crosspost info - for that you have to go into the post itself by querying api/v3/post. As such, frontends would have to do a fair bit of extra work to wrangle the required information for a main feed that combined crossposts.

Most frontends already display available crossposts so you’re not wasting anything more than grabbing all the comment sections as well.

I’d argue that you have a problem as soon as you start saying ‘frontends need to do some extra work’ - it breaks the dynamic between backends and frontends. Backends should be big, complicated things, worked on by people familiar with the project, to provide all the logic, whereas frontends should be light, relatively easy to write, runnable on devices with limited resources, and mostly focused on how the information provided to them should be displayed. They should store the user’s preferences, and login details, and that’s it - everything else should come from the backend.

I don’t agree at all. There’s space for complex frontends which attempt to adjust the feed according to their own logic, as well as minimalistic frontends which follow the backend’s design explicitly.

So I just installed it to check and it doesn’t do that. It just makes crossposts a bit more visible.

However it looks like a neat app so I’ll take it for a drive for a bit

Does it show all comments in the same place like I suggest, or does one have to click on each crosspost to see them?

This is what this post is suggesting, yes

That’s a 404. Is there a git repo? I could use obtainium

Link plox

All posts would be made with hashtags like Mastodon, and then each community would just configure “Include all posts with this tag in our community”. The big issue then is who moderates tags? I think a system like Bluesky has would work well, as you mention. People can moderate tags and other people can follow their work, or not.

You’re describing something like microblogging though. That’s how that works already. We don’t need to duplicate that in theadiverse. However, just a way to see merged comment sections from different communities for the same URL would go a long way to avoid too much splintering of discussions.

Site admins and developers at least get their $500/month from kofi

Just lol. Someone please arrange for my 500 per month >_<. We have one of the largest instances in the threadiverse and we don’t even get 1/5 of that :D