Let guess: Bot wants to use "it / its" pronouns. The same as 'DroneRights' did, who despite the similarly in name to 'DragonRider', and despite the fact that all these accounts are an obvious, boring, attack on trans rights, are all, like, totally different people.
I read that tweet as something that wasn't really about Fallout: New Vegas, and more as something using it as a vehicle for a joke (about adult women being nostalgic for the games they played as teenage boys).
If you fetch a community that your instance hasn't previously heard of, you can typically query the community's 'outbox' collection to get recent posts. So in Lemmy, you get 50 old posts, and then - once someone has subscribed - new posts start coming in.
Different platforms have different formats for their outboxes - Lemmy uses Announce/Create/Page, a.gup.pe and PeerTube use Announce, with a URL that leads to a Note or Video, wordpress uses Create/Article. Because Lemmy already understands its own outbox format, it's able to get old posts from other Lemmy instances. It doesn't get old stuff for a.gup.pe, PeerTube, or wordpress though.
So you might be wondering what outbox format nodebb uses - to which the answer is none. The outbox leads nowhere useful (they're in good company with MBIN on this). Anyway - this is why fetching a nodebb community won't come with any of its existing posts (but - as mentioned - new stuff will come in for subscribers)
Season 3 of a TV show comes with a significant wage increase for everyone involved, so 3 seasons (at least) is something that the sellers of a show always want, but the buyers are trying to avoid.
On Netflix, it's become a pattern of all shows only getting 1 or 2 seasons, unless they're mega-hits, or dirt-cheap to produce in the first place.
How well a show wraps up after 2 seasons often depends on how much the writers want to do the streamer's job for them. Tokyo Vice was a (rare) example of a good, self-contained, 2-season show.
A comment here distinguishes between the 'plain text' that's allowed by the spec, and MarkDown as a markup language (it's confusingly named, I guess, but that's what Wikipedia categorises it as too)
Lemmy mostly federates with Lemmy, but everything else out there (PeerTube, PixelFed, etc) has been developed to work well with Mastodon (sometimes to the Fediverse's detriment), so your Mastodon account should be all you need.
Another commenter (who's contributed code to Lemmy) pointed to a link that provides the specification for that field: "A simple, human-readable, plain-text name for the object. HTML markup MUST NOT be included."
So in this case, it's more that the JSON looks a bit ambiguous: 'mediaType' is only referring to the format of the text in a post's body, but - unlike me - you'd also need to be aware of the spec to know that it doesn't apply to the title.
For clarity, I wasn't intending to say that PieFed treats that field as HTML (it treats it as text), I just meant that if you were looking at that JSON, and being a bit lazy like me and not looking at specs, then it wouldn't be unreasonable to assume that the 'mediaType' field also refers to 'name' (rather than a 'content' field which this post doesn't happen to have).
Anyway, this seems to be even more reason why MD shouldn't be put in titles, and front-ends shouldn't be encouraging the practise by rendering it.
You can, but maybe you shouldn't. Given that this post is in the fediverse community, I don't feel too bad about mentioning that Lemmy is part of a federated network with PieFed and MBIN (I try not to bollock on too much about the platform I happen to be using).
In the ActivityPub JSON for this post, there is no indication that this field contains MarkDown. If anything, it says the opposite, it says it contains HTML. It's therefore not unreasonable for other platforms to render it as such.
Given this, and the poor support for mobile clients indicated in the comments, and the fact that it's only a subset of MarkDown tags, but include ones that aren't part of CommonMark standard, I'd argue that it's not necessarily a good idea.
OP won't see your image unfortunately, because of a difference in how embeds are handled (Mastodon's use of image attachments to Lemmy's use of MarkDown has been fixed in one direction, but not the other).
It uses postgres for the DB - I think that and redis are designed to operate at very large scales, so it wouldn't be them.
My guess would be that it's something in the interpreted nature of Python - this seems to be why a familiar dismissal of PieFed is a concern about how it will scale.
That said, this site shows that Python is the most popular language for Fediverse apps (just), the likes of Mastodon are written in another interpreted language (Ruby), and I think there are more big websites running Python (with Django or Flask) than people realise. So I don't know, really, I'm just following other people's lead on this. I don't imagine that any problems would be insurmountable though: an admin could restrict the amount of signups, or if new users mean a few more donations, they could just throw money at the problem (more cycles for one server, or splitting up tasks across multiple servers).
In terms of incoming federation, PieFed sites are dealing with as much activity as any general Lemmy instance. It's not happened yet, but I suppose it's possible that problems will become apparent if the amount of local users gets over a certain size. A limit on the amount of users per instance isn't necessarily a bad thing though (it's cheap, and hopefully easy enough, for someone to spin up another one).
What's unclaimsies and how badly does it break the lore?
Skeleton Crew is set in the world of children as much as it's set in the world of Star Wars, and is concerned as much with pirate lore as it is Star Wars lore. "Claimsies" and "unclaimsies" is just "finders, keepers!" and another child's attempt to reverse that.
There's a key moment in the show where it combines those two concepts - the made-up words and rules of children, with the made-up words and rules of pirates -
::: spoiler spoiler for episode 7
A droid decides that a call of "unclaimsies" is "close-enough" to pirate lore that it will let them re-take a ship that's been commandeered by a pirate.
:::
This is all quite old drama, and the issue itself is fixed now, but at one point someone kicked off about how if you uploaded a picture to Lemmy, there was no easy way to delete it (you could delete your post, but the image would still be there at whatever URL was created for it, and it wasn't even that easy for admins to find and remove it) - so I'm guessing that it stems from that.
Oh yeah, sorry. I didn't mention that the API isn't available on production sites like piefed.social. I've been messing around with a build of Thunder on my dev instance, and - among other things - the app doesn't uses the same V3 endpoint that Lemmy does, so it'd always need to be a different version than the one that's currently available for Lemmy.
No, it's not geared up for that. There's a platform called sublinks where the intention is to be initially compatible enough with Lemmy that it can be a drop-in replacement, but they haven't released anything yet.
It's not so much that we expect the developers of Lemmy apps to retool. The hope is that, if we can provide a sensible, well-documented API, then it will appeal to front-end developers looking for a project. Also, if there are any devs of Lemmy mobile apps who are unhappy with Lemmy's API for any reason, then getting involved with PieFed's whilst it's still in development, offers them a chance to shape one to their desires.
Speaking of Thunder though - I've been able to compile it for desktop, and get it working with PieFed's API in the state it's in now. I've no experience with Flutter / Dart or front-end development, so it suggests that - for open source Lemmy apps, at least - it doesn't need to be the original author who ports it, and that the actual details a particular API are only a relatively small part of creating a good mobile app.
Let guess: Bot wants to use "it / its" pronouns. The same as 'DroneRights' did, who despite the similarly in name to 'DragonRider', and despite the fact that all these accounts are an obvious, boring, attack on trans rights, are all, like, totally different people.