More abuse of this post for testing PieFed user mentions (sorry if you seeing this). Other direction this time.
@andrew_[email protected]
More abuse of this post for testing PieFed user mentions (sorry if you seeing this). Other direction this time.
@andrew_[email protected]
Back again, as reply to post: @[email protected], @[email protected]
EDIT: autocomplete was originally messed up, but this shows Mentions as raw and filled in by Lemmy's UI (both are clickable on PieFed, and this edit shouldn't notify anyone again)
Remote comment that doesn't get a Mention until the edit (although it'll have to be to andrew, 'cos I replied with the wrong account).
Edit: @[email protected]
Cool. Paging you (although you should only get one notification): @[email protected]
Also: paging @[email protected]
I'm guessing that this post is supposed to be a link to a video like this one: https://m.youtube.com/watch?v=sg0SmgoSMg4
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:
https://pandacap.azurewebsites.net/
sends something out.https://pandacap.azurewebsites.net
)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.If every new platform treats the Fediverse as a wheel that needs to be re-invented, then the whole project is doomed.
You might need to have the 'show nfsw' setting turned on. Anyway, they look like this:
nsfw
So the theory that they were downvoted for spamming someone's feed likely has validity.