freamon

I screenshotted this from their 'trending' page, which suggests that their content is garbage and their tech is fucked.

He fixed things to get the missing communities back, but it looks like subsequent runs of the crawler lost them again, so now it's rejecting updates because the difference is too great (it always used to do this, so I don't know how it was publishing with so many missing before).

Anyway, it looks like I'm going to have to do the most NSFW imaginable - look at someone else's TypeScript project. I'll get back in touch with him if it doesn't correct itself, but it'll be nice if I can figure out what the problem is first.

Upstream crawler is missing about 20k communities - https://data.lemmyverse.net/ normally shows about 30k.

I've messaged the maintainer.

Hmmm. Speaking of Fediverse interoperability, platforms other than yours (Pandacap) typically arrange things so that https://pandacap.azurewebsites.net was the domain, and something like https://pandacap.azurewebsites.net/users/lizard-socks was the user, but Pandacap wants to use https://pandacap.azurewebsites.net for both. Combined with the fact that it doesn't seem to support /.well-known/nodeinfo means that no other platform knows what software it's running.

When your actor sends something out, it uses the id https://pandacap.azurewebsites.net/, but when something tries to look that up, it returns a "Person" with a subtly different id of https://pandacap.azurewebsites.net (no trailing slash). So there's the potential to create the following:

1. https://pandacap.azurewebsites.net/ sends something out.
2. Instance hasn't heard of that, so looks it up, and creates a new user in its database, with the returned ID (https://pandacap.azurewebsites.net)
3. https://pandacap.azurewebsites.net/ sends else something out. Instance looks in it's DB, finds nothing, so looks it up and tries to create it again. The best case is that it meets a DB uniqueness constraint, because the ID it gets back from that lookup does actually exist (so it can use that, but it was a long way around to find it). The worst case - when there's no DB uniqueness constraint -is that a 'new' user is created every time.
4. Repeat step 3 for every new thing you send.

If every new platform treats the Fediverse as a wheel that needs to be re-invented, then the whole project is doomed.

It's the crawler at lemmyverse that's down - https://data.lemmyverse.net/ shows that it hasn't updated in 11 days

Already posted 4 days ago btw: https://lemmy.world/post/16488547

Tragically, this also means that, even after 31 years, I've still never 'get good' enough.

Speaking of wildly inaccurate:

Not sure Lemmy gets to throw stones (it'd probably miss).

Not sure where to post this. Sometimes (in ways that are difficult to replicate), I get a JSON response for a reddthat post in my browser instead of an HTML one. It's happened before on mobile (Chrome) and today also desktop (MS Edge), so I was able to make a screenshot:

I'm assuming it's related to 0.19.4, but maybe others have seen this behaviour before the upgrade. Apologies if you're already aware - I had a quick look for other mentions but didn't find any.

Sorry. Maybe I used the wrong term. I meant to say it's not part of the CommonMark spec (as supported by Lemmy) - like spoilers, there's identifiers that have gained popularity, but they're still not properly official. I did do a quick web-search before I made that comment, which suggested there are some sites that use a single tilde for strikethrough.

I didn't intend any criticism of your post - I was just cheekily using it to have a tangential ding at notions of Fediverse interoperability.

With apologies for being off-topic ...

Lemmy: we're a Fediverse app, so can communicate with lots of other ones!
Also Lemmy: here's some non-standardised Markdown, with no indication that it is Markdown, or which variant of strikethrough we support, and a 'mediaType' of 'text/html'

Oh. Then I'm genuinely sorry. I thought we were both having fun, engaging in a good old-fashioned flame war. Add that to 'incorrect assumptions' pile then, I guess.