You might need to have the ‘show nfsw’ setting turned on. Anyway, they look like this:

So the theory that they were downvoted for spamming someone’s feed likely has validity.

Back again, as reply to post: @andrew@pythag.net, @sfc@pythag.net

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)

okay

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: @andrew@pythag.net

Cool. Paging you (although you should only get one notification): @andrew@pythag.net
Also: paging @sfc@pythag.net

Neat. Just have to do it the other way now.

@sfc@pythag.net

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.

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

Hmm, yes the dichotomy indeed.

Bonus repost:

Just for clarity: it’s not viewable through the API. As others have said, you need to spin up an instance. In contrast to the API, this means it’s not free (due to server hosting and domain name costs), and it’s not necessarily easy (for the non-techies).

I haven’t watched much Trek but I thought I’d check out Strange New Worlds (I was Sci-Bi-Curious).

meme: https://dmv.social/post/367939

template: https://lemmy.world/pictrs/image/2481645c-57c0-445e-90f3-ee2a1e0f740b.webp

It’s only the lack of pencils in SW that stops this guy from killing you with one.

Probably, yeah. I made a post about how best to spoiler-protect stuff, but given the current state of Lemmy, it’s maybe best if we just wait a week or two.

Apologies. I left a gap 'cos I’d assumed Ahsoka’s finale would be more meme-worthy. Instead of it being … what it was.

I’ll renew my efforts for next week. Get in touch if there’s an idea you want to riff on, and we can dedicate a day to it.

Well, this is news worth getting out of bed for:

(Don’t worry too much about stuff we’ve already seen btw, anything older than a month would be fair game for reposting anyways)

I know what you mean about trailers - I always avoid them for films because of how much they give away. The Ahsoka one isn’t too bad, and it’s useful as something to refer to as what should be considered a base level of knowledge about a show. Otherwise we end up in the crazy situation of saying that Ahsoka appearing in the new Ahsoka show is a spoiler.

For things that are unarguably spoilers though, the post suggests waiting ‘a couple of weeks’. A meme I posted was reported, even though I’d followed the ‘usual guidelines’ of waiting a week.

We’re reluctant to curb people’s creativity though, and obviously the thing that’s just happened is going to drive much of the original content we especially appreciate. So hopefully, if people follow the suggestion about how best to prevent anyone accidentally seeing something too soon, we can reach some sort of compromise.