Re: your edit - please feel free to open an Issue for PieFed about it. It’s MBIN content in Lemmy’s communities, so it’s something that needs attention (we should show it, even if Lemmy doesn’t). I’ll have a crack at fixing it next time I’m working on the code.

'Bin follows the same format as Mastodon for inline images, which is different from Lemmy.
Mastodon puts the details for an inline image inside an ‘attachment’ field, with nothing in the ‘content’ fields, whereas Lemmy doesn’t use an ‘attachment’ field at all for them, and includes the HTML for img src in the content.
It’s always been the case that Mastodon didn’t show images from Lemmy comments. I don’t know if the reverse is a new thing or if it’s always been like that.

It depends. It seems like Lemmy batches up its activity to send to remote instances - so, per instance, it sleeps for a bit, then sends what it has. If both a Create and an Update are in the same batch, Lemmy just sends the Update. If they don’t happen to be in the same batch though, it sends both activities.

(this is outsider observation, not insider knowledge)

I wouldn’t do this personally, but if I did, I think I’d at least pipe the results to head -n 1 to only act on the first result.

Please use your mander account to inform OP that their instance is wildly behind .world - see here

The delay and eventual deletion of comments and votes will have an obvious effect on mander’s “hot” and “active” algos.

If you look at this post on mander, it’s not got any of the comments, so there’s no point anyone using a .world community to answer OP’s question.

You’re right about the cause: Lemmy’s front-end isn’t giving its backend enough time to do everything it needs to do for an unfamiliar commentary.

It works better if you copy / paste the link into Search. MBin effectively redirects all these links to its Search anyway, so maybe that’s an option.

lemm.ee have upp’d to 0.19.4, and presumably turned on the Image Proxying thing - this is what I get for: https://lemm.ee/post/34040618

{"error":"unknown","message":"Request error: error sending request for url ([http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)](http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)): operation timed out"}

It’s probably a temporary hiccup, but Lemmy has bigger problems with PeerTube videos, in that you can subscribe to channels from there, but - last time I checked - they don’t update with new videos.

For comments, PieFed could do with more work too. Direct communication between us and channel owners works okay - example post - but a comment from, say, a Mastodon user wouldn’t show up here. The reason is that, unlike Lemmy, PeerTube do not ‘Announce’ anything other than new posts. This solves the Lemmy/Mastodon problem where Mastodon users can subscribe to Lemmy communities, but then have to deal with individual ‘boosts’ of every comment in reply to a post. Instead, PeerTube directly send an ‘Update’, with endpoints for a ‘Replies’ collection and a ‘Likes’ collection. Currently, PieFed does nothing more than check that the post body hasn’t changed when it receives these updates, but - technically - it should also check these endpoints for new activity. It might not be worth doing this every time though, maybe once a day would be enough.

I’ve had that problem too (messing around with test instances) - for anyone else wondering why: it’s because the RSA keypair for me@mydomain has changed, and remote instances fail to validate message headers signed with the new private key, because they’re still using their copy of an old public key.

That’s great to hear. There’s zero API at the moment though, let alone a stable one. PieFed is a monolith, without the backend / front-end split that necessitates an API.

It easy to add one, pending the addition of some missing features and a code reorganization that needs to happen anyway. At that point, hopefully some interested app developers will also be involved, to shape the API into something they may wish that other app’s APIs were like.

My initial response was: that sounds a bit like a ‘fake community’, something for which I thought the consensus was ‘bad idea’. Moreover, it’d arguably be a fake community full of fake posts.

Lemmy has 2 types of modlog - one for each community and one that’s instance wide. Would the plan be a community just for the instance, or something that merged actions from both?

That’s the book I was referring to, yep.

I think most bread that’s available to buy is actually junk. Even the ‘wholemeal’ stuff, which itself obfuscates what you actually want: wholegrain. Ideally, the carbs percentage shouldn’t be more than 5 times the fibre percentage (according to the ‘How not to die’ book), but I’ve found that very little that actually meets that.

This is why people can become obese without understanding why: the over-processing of food considered as staples.

This isn’t really my area, but I’ll have a crack. From what I understand, Lemmy uses the ‘meta og:image’ tag to grab a thumbnail. Inspecting your site, I can see that that tag is in the html head. However, if you just ‘curl’ the URL, then it isn’t in the results. Using ‘curl’ for URLs from sites that are known to work in terms of generating thumbnails (theguardian and bbc), the tag is visible in the result.

This suggests that your site is using further scripting on page load to provide the meta tags, whereas perhaps Lemmy can only get them if they are provided immediately. There are other sites (like Reuters), who use additional scripting, that Lemmy is unable to get thumbnails for also (e.g. https://lemmy.world/post/16203031)

Assuming that kind of functionality involves JavaScript, it depends on how much it involves. From what I understand, PieFed is designed to be accessible in low resource / low bandwidth environments, which downloading megabytes of JS isn’t compatible with.

It would probably need to get to the point of PieFed having an API, and then a front-end (with a design like Alexandrite) can use as much JS as it likes, because it’s something the user has agreed to.

PieFed also got a mention in this week’s Fediverse Report - for my part, I’ll try not to let the fame change me.

There seems to be some decent channels that are local to that instance (some PeerTube integration was recently added to PieFed, so I’m going by the list on this post ). From there, you can watch stuff from other instances, if course.

I think it’s more just for discovery. They provide a guide here which recommends https://tilvids.com/ as a PeerTube instance you can sign up with.

https://fedi.video/ has organised a bunch of channels into playlists that has some crossover with your topic list.

You can’t meaningfully just tag ‘main’, you need to include an instance too. https://activitypub.academy is good resource to test and verify this stuff out for yourself.