I don’t use Lemmy, what’s the issue with search on it? I don’t see any obvious issues with the one on your instance at a glance.
I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.
I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.
#fedi22 (for fediverse.info)
I don’t use Lemmy, what’s the issue with search on it? I don’t see any obvious issues with the one on your instance at a glance.
My preference for dark modes is more about design choices than the actual dark/light divide.
Light modes tend to have way less separation between UI elements, with borders and differences in background colors barely visible. It results in them blending together and making it harder to identify different parts of the website than on dark mode. They’re also much more likely to use actual white backgrounds, when dark modes usually use anything other than actual black. I really hate both white and black used as backgrounds, they’re both bad imo.
I do use light modes on websites where it actually looks better than the dark mode design. But sadly those are too rare.


Huh, interesting.
I’m using Mbin and we don’t need it, I just assumed Lemmy was the same.


I never used websites like Twitter and Facebook either. Sure I have looked into stuff like Mastodon, Friendica, Misskey, etc. But you’re never going to get me to actually use them, they’re not the kind of social media I’m interested in.
When it comes to the threadiverse, I actually use Mbin, not Lemmy. I did try both Lemmy and Piefed, but Mbin fits my tastes as an Old Reddit user best out of the three.


Does Lemmy need the double space? This isn’t Reddit after all, and it’s the only Markdown implementation I’ve seen with that requirement for line breaks.
I didn’t. My country focuses more on apprenticeships than higher education, and I wasn’t the type to be really ambitious. So I never really explored my options and just went with the flow.


Not using Lemmy myself, but I assume this is about the name in the url vs the name in the UI. Displayname is probably how Lemmy itself displays the community, but name is what’s in the URL and in the fediverse handle.
What if there were a way to do this with multiple fediverse services? What if you have an article, and the comments are 1 lemmy user, 1 mastodon user, 1 misskey user, 1 friendica user, ect ect ect? Basically start making ANY fediverse service a viable way to leave a comment, which can be replied to by any other fediverse user, regardless of service?
That’s just the base promise of ActivityPub, the basis of the fediverse. It’s not a hypothetical, but rather reality.
That scenario you mentioned, it’s not only Lemmy users that could reply there. All the ones you mentioned would have had access to that blog’s comment section and been able to leave replies.
So if you have user@lemmy.world, and you go to his community, you see a thread, you comment…your comment is now in the comments section of his blog.
That’s just literally the same as me looking at this Lemmy thread from Mbin, leaving a comment, and it appearing on Lemmy.


I’m not on Lemmy, but I have the “Active” sort set as my default.


Not sure if you’re already aware, but that relative link there is broken in Lemmy, Mbin, and Piefed.
If you used it manually, I’d suggest not using relative links in posts targeted at users from software that hasn’t implemented them yet.
If it’s some automated feature, I don’t think it should be in the source property of the federated JSON in the first place.
deleted by creator
Once upon a long time ago, some old man gave a monkey an apple and then love happened and they leveled up into humans. May have been 100 or 200 or more years ago I don’t do historian.
There are others, yeah. But they’re not threadiverse. They’re quite different types of social media from Lemmy. Since OP is using Lemmy, that’s why I’m recommending Mbin, not one of those.
Like I said, if you want more integration than what Lemmy offers, do consider switching to Mbin instead. It targets both, the threadiverse and the microblogging side of the fediverse.


All that’s needed is the reminder (as visible as possible) that content you are looking at is incomplete and you can find the more complete version on this or that URL or app.
That’s what Mbin does, it displays a banner on federated user profiles explaining that they may be incomplete, with a link to the same profile on the originating instance.
NOSTR is not any more a protocol of the fediverse than ATProto and Matrix’s protocol are.
This is the first time I’ve seen anyone consider it as being part of the fediverse. Are there even any federated platforms that federate with it? If we can’t talk to it, how is it federated with us?


the same way it makes sense for Lemmy/Mbin/Piefed to only show posts made on a community.
To be fair, that’s not how Mbin works. Its communities also capture microblog posts that weren’t originally posted to a community, based on the community’s configured hashtags.


This article’s core argument seems to be that Pixelfed is violating the ActivityPub protocol by not displaying posts that do not contain images. That’s just not true at all. I’m interested to know where the protocol ever has such a requirement.
The principle behind a communication protocol is to create trust that messages are transmitted.
And they have been transmitted. They’ve been filtered out after transmission, but the protocol did its job.
If a message is not delivered, the sender should be notified.
Perhaps. But that’s not in the spec. There’s no obligation to notify iirc that a post got filtered out on the target instance.
Even if Pixelfed sent Reject(Note) back for every post without an image, would Mastodon even display that to the user anywhere? Would most users want to see that for every post not containing an image multiplied by every Pixelfed instance it got federated to? I’d personally interpret that as spam.
Lemmy doesn’t really target compatibility with Mastodon. It does have some of it by using the same federation protocol, but it’s all incidential and not actually directly supported.
If you wish for proper support, I recommend switching to Mbin instead. It’s a Lemmy-like project that aims to work with both Lemmy and Mastodon.
When it comes to communicating between Lemmy and Mastodon though, this is what I know:
You can mention any Mastodon user the same way you’d mention a Lemmy user. They will get your mention and will see the post or comment you mentioned them in. Your instance doesn’t need to be federating with the Mastodon instance in question for this to work, as long as you’re not explicitly defederated from each other.
Lemmy communities show up on Mastodon as users, so Mastodon users can browse and follow them. They basically function by boosting (retweeting) every post made to them. So all you need to do for your posts to show up on Mastodon is to have a user on there follow the community you’re posting in.
Mastodon users can post to Lemmy communities by mentioning them, as if they were a user. Lemmy will display them as threads despite them being microblog posts, Mbin separates Lemmy-style threads and Mastodon-style microblog posts in your feed.
Interacting with Lemmy communities directly isn’t too common for Mastodon users, hence the low amount of contact between the two. If you want to increase your discoverability, add hashtags to your posts. Mastodon iirc mainly relies on hashtags for discoverability.
Lemmy does NOT let you browse Mastodon posts or follow users on there. Mbin does though. So again, if this is something you want, do consider switching instead.
I use Mbin. Used to be on kbin.social, then switched to an Mbin instance when that went under (after trying out both Lemmy and Piefed).
Mbin is a more open alternative to Lemmy which has dedicated support for microblog posts as well, including features like boosting (retweeting) and following. Unlike Lemmy’s focus on the threadiverse only.