Neat. It took me a while to realise what was going on: the post on Lemmy and the blogpost are two separate entities. The Lemmy post is a link to the blogpost, and the blogpost uses the post_id to fetch the comments (so I guess this means you have to make the blogpost, make the Lemmy post, and then go back and edit the blogpost with the correct id?)
The script is inspectable on the blog - I can see it does:const url = 'https://lemmy.ml/api/v3/comment/listpost_id=21617067&limit=100&max_depth=8&sort=Top&type_=All';
So I suppose there's an inbuilt limit for comment depth and number of replies, but if you start down the road of working on that, you'll eventually find that you've re-invented a front-end, and there's no end to it.
What the duckquill guys are doing is a bit fudgy, in that they're getting another website to do the federation legwork for them, but the results are pleasing enough.
MBIN makes upvotes visible, but PieFed doesn't. The thread you linked to is about PieFed anonymising votes, so they aren't revealed on instances like MBIN.
For 'Action Horror', I've liked The Hunt (2020), Ready or Not, Totally Killer and Strange Darling (technically not a horror, but it's about a serial killer)
I watched Red Rooms recently, and that's French (Canadian), so if anyone asks you what you watched recently, you can say 'Les chambres rouges' and sound all intelligent and stuff.
In Lemmy terms, everyone here is a 'Person', sending a 'Note' activity for the fediverse@lemmy.world 'Group'.With Castopod, it classes your podcast as a 'Person', and each episode as a 'PodcastEpisode'.
If Castopod classed your podcast as a Group, the same as PeerTube does for video channels, then integration would be relatively easy. A Group for a podcast would make more sense to me, but FunkWhale have made similar decisions, probably due to the dominance of Mastodon within the Fediverse.
As mentioned, you could probably tag your episodes with the address of a pre-existing Group (e.g. a community on Lemmy), but that pre-supposes that Lemmy knows what to do with the 'PodcastEpisode' type (a quick look on their GitHub suggests that it currently doesn't)
It's a trade-off, I guess. Admittedly, there's not much benefit the user (though they could be warned via email if their account is going to be de-activated). There is however a benefit to the community, in that it can provide more reliable data to see if it's trending in popularity (a 100 extra users isn't significant if it thinks it has 30k users, but it moves the needle if that number is at a more realistic level).
I recognize most of the users there even in the big communities with over 30k members
Communities with 30k members could really do with pruning the completely inactive ones. It's not like there's any commercial reasons to pretend that places are busier than they actually are.
I think it's asking a lot - it's not unreasonable for libraries to convert the markdown format for embedded images into IMG SRC, but then the clients can't play them because they're not images. Ideally, I think, there should be different markdown for embedded videos and audio (but it doesn't look like there's anything official).
These clips play for me on PieFed, but only because after the markdown translation, they get regexed into the correct AUDIO tags.
In that thread, Gargron (the Mastodon dev) saying that they have groups on the back burner is a bit of an understatement (the code to support Lemmy-style communities has been sat languishing for ages).
There's a user here, who was '101' at reddthat, then piefed, then feddit.org, and was 911 at lemmynsfw, and is currently 911 at programming.dev, who posts a bunch of articles over a week or so, then deletes their account and moves on to another instance. They're up to something, surely. (the only real downside to this behaviour - that I can think of - is that new instances won't be able to get their posts, because Lemmy doesn't return posts for deleted users)
Oh, right. I was confused by this before, but I understand it now after reading yours and Otters answers, and seeing https://rss.ponder.cat/c/medicine@lemmy.ca - the bot posts to its local version of a remote community, and it federates out like it it normally does.
Am I right in assuming that - API wise - the bot only interacts with ponder.cat, and doesn't make calls to the remote instance? (I'm wondering if there's any barriers to it operating with communities that aren't on a Lemmy instance).
Does the bot resolve the human first, check what they moderate, and then resolve the community if they moderate it, or just always resolve the community, and then compare its moderators with who made the request? If its the latter, this could be a way for bad actors to crowbar a community onto your instance (assuming it doesn't purge it if things don't match up, of course).
What would have happened if Otter had sent /add https://lemmy.ca/feeds/c/medicine.xml medicine@lemmy.ca ? Would this be like that time when someone put 'google' into google.com, and the Internet blew up?
Fair enough. I'm not trying to recruit you, or present rivalries where none exist. We can communicate reasonably well regardless of whatever platform we prefer, which is the whole point of this Fediverse thingy anyway.
PieFed has some design principles, including being accessible on lower-end devices and for those with unreliable bandwidth, which mean that it's default UI is never going to look like apps which involve downloading a sizable chunk of Typescript.
I'm okay with its look. Partly because it's themeable, and there's a theme called 'Card Shadow' which looks more modern imo. And partly because Lemmy can feel quite slow showing 20 posts at a time, whereas PieFed throws 100 at a time. And also because there will eventually be an API, allowing people to view it how they want (similar to Lemmy - lemmy-ui is maybe not that great, but there's other frontends which I think are an improvement)
This feels like something that would be scriptable using Lemmy's API - see https://lemmy.readme.io to view and demo the endpoints.