Lemmy doesn’t seem to get much recognition in the wider Fediverse - it tends to get bundled as part of ‘other apps’. Mastodon is much bigger, so better integration with Lemmy probably gets deprioritised below their own issues and feature requests (e.g. I was reading today that Markdown support is often requested, but the base version still doesn’t have it)

I don’t think it’s technically impossible - all the information that another site needs to properly interpret some activity is in the JSON that’s sent. I get the sense that it might be unrealistic to expect Mastodon to make the necessary changes though. It seems more of a political issue than a technical one.

It’s partly an issue of keys. Every fediverse actor has a private key and a public key. When my instance sends this to fediverse@lemmy.world, it’s signed by my private key, and lemmy.world uses my public key to verify it. When fediverse@lemmy.world sends this comment out, it uses it’s own private key to sign it. It can’t just re-transmit my comment, because it doesn’t have my private key. All it can do is Announce that I’ve made the comment (and sign the Announce).

Mastodon treats Announces as Boosts, so every post/comment is interpreted as a thing that fediverse@lemmy.world has boosted, so you get all these un-connected posts appearing. I think it’s mostly up to Mastodon to remedy.

It works better if a Mastodon actor posts into a Lemmy community, then you get the mix like you imagine. e.g.: https://mastodon.world/@Flash/112095241193510662 (this particular post was crowbarred into Lemmy via !tails@lemmon.website, but it would be the same if the author had done it.)

Wait, what? A user posts a thing to a server, and that thing isn’t then duplicated to 50 other servers … yeah, I don’t see how that can work.

(I’m just kidding - your site looks neat.)

(sorry to intrude). This has had a few cross-posts on Lemmy - this one technically wasn’t, but it seems Lemmy has picked up on it. If you want some ALT text, and to reply to author of this image, the link that goes to !tails@lemmon.website provides that.

Yeah it was pretty nifty in lots of ways. Loads of emulators, of course, and doing stuff like compiling apps directly on the device itself was neat.

Frustrating in lots of other ways too, though. I don’t think the Pyra ever really got off the ground, unfortunately.

This was always an impressive emulator - it was originally made for the Open Pandora (an ARM-based mini-computer not much bigger than a DS). It’s always been free for that - it’s just, you know, you’d have to own an Open Pandora (I do!)

Not quite, no. I know what it isn’t at least.

I’ll keep going - I’m sure the article’s author is someone who genuinely uploaded some confidential info and then became really involved with privacy/GDPR etc, and not someone who was always been really involved with privacy/GDPR issues and now has a story to fit.

I’m gonna find this guy’s image …

https://monero.town/pictrs/image/00000000-0000-0000-0000-000000000000.jpeg … nope
https://monero.town/pictrs/image/00000000-0000-0000-0000-000000000001.jpeg … nope
https://monero.town/pictrs/image/00000000-0000-0000-0000-000000000002.jpeg … nope
https://monero.town/pictrs/image/00000000-0000-0000-0000-000000000003.jpeg … nope

Mmm, I’m sure it won’t take long. Just have to remember to do it all again for .jpg, .webp, and .png.

Anyway, I’ll let you know when I get it.

Informing a human that their work has already been done for them by a bot is oddly appropriate for this post.

It’s been censored out, but it looks like it’s heading for Shit Creek, appropriately enough.

Not that I’m aware of, just communities that seem like they might fit, but don’t quite:

!communitypromo@lemmy.ca
!communityspotlight@lemmy.world
!newcommunities@lemmy.world
!newcommunities@discuss.online

I’m sure you could make a more meta-type post in one of these though.

A quick Google suggests you’re correct - big sites have implemented their own versions, but it looks like everyone has spent the last decade arguing with other about a CommonMark standard.

I think it’s because spoiler tags in lemmy have been custom-made for some reason, whereas all the other stuff is standard markdown. Voyager is a web app, so it can maybe only render whatever the engine it relies on can render.

Edit: Turns out I’m 2 for 2 on making incorrect statements in this comment.

I’ve compiled lemmy a few times - it’s fairly straightforward. I’ve tried to compile kbin before, but gave up bored and pissed off with the instructions - they seem endless, and like a big list of ‘edit this file’ (with no indication for whether you’re adding or updating info), ‘now edit this file’, ‘now go back and edit the first file again’. I know mbin isn’t kbin, but the instructions are the same.

I was trying because someone from there subscribed to a community I made just using ActivityPub, but nothing I’ve sent there has actually appeared. If you send the wrong stuff to lemmy, it errors. It’s not always the most useful message, but it’s at least a ‘400 Bad Request’, not the ‘200 OK {}’ you get back from kbin. What does it want? Does it not like ‘Create/Page’? Is there a problem with the content? I don’t know, because I can’t [be bothered to] compile it, and the tech specs for these 'bins lead to a 404.

Oh wow. That really illustrates it. Your approach to a social media site is very admirable (so much modern stuff assumes that just throwing more CPU cycles / RAM / bandwidth at the problem is a solution).

Flippin’ eck. Seeing a familiar Lemmy post on there, clicking it and seeing the whole thing render instantly was a bit of a shock after getting used to Lemmy’s more pedestrian loading of stuff.

It seems a very optimistic viewpoint that, actually, Lemmy would have more content, it’s just that all the people who would be making it are, like, really busy with other stuff right now.

Ooof. That makes me feel better about that time I accidentally brought ‘Test Post 1’ into production by commenting on it.

It’s me deciding. Recommendations for interesting people on Mastodon to follow are welcome (either in this post, or the sticky ‘About this community’ post).