I discovered this after upgrading our instance yesterday, which also upgraded all frontends to their latest versions as well. After I did, our Tesseract frontend stopped working and I noticed immediately as it’s been my primary for a while. Initially I thought it was an API version mismatch, but no, it was much worse.

Someone pointed out that the developer of the frontend added an explicit hidden and unmodifiably blacklist which includes any and all instances to the left of Kissinger. There’s a commit which also explains their specious reasoning about our instance specifically, as it seems we’ve been on their shit list for a bit longer than that.

This instance and its admin staff encourages identity politics, groupthink, mob mentality, and extremist solutions to societal problems. Users who advocate violence are not moderated so long as the admins agree with the target. Caution and critical thinking are advised when interacting with this instance or its users.

When you use tesseract to connect to one blacklisted such instance , you just get a message informing you that Tesseract is “incompatible with that instance” which leads one to think of a technical issue, like an API mismatch, rather than the dev being an opinionated coward.

Isn’t it funny how all the software developed by turbolibs, like Piefed and Tesseract, end up with hidden control mechanisms from developers who think they know better than everyone else? That they don’t just think they deserve to tell you what you should think, but they should manipulate you to think it? Isn’t it funny how libs go on about how bad it is to support lemmy due to the ideology of the devs behind it, and yet lemmy has 0 opinions as a software? It does make one think…

Anyway, I forked - it as one does - and disabled the blacklist, but since this is a massively ideologically compromised software, I’ll doubt I’ll keep this frontend up after Lemmy 1.0. I think we’ll bring up mlmym again now that someone’s maintaining it again.

Cross-posted from “Lemmy Release v0.19.20 - Reduced Memory Usage” by @dessalines@lemmy.ml in !announcements@lemmy.ml

I’m planning to upgrade to this version ASAP as we’ve been having some RAM issues in the DB recently which is causing the “daily hiccups”. I can’t promise this will fix it, but I can hope. Expect some short downtime in the near future.

EDIT: Done

You know that little information thing below posts telling you which other communities a specific post has been posted to?

That one, won’t appear if you crosspost a pure-text post. Sure you’ll get a link in the body, but lemmy won’t “intuitively” know the two posts are connected.

By using an image in the URL of the post, not only do you give your text post a thumbnail, but you allow lemmy to easier link them together when cross-posting.

If you’re wondering “But where the hell do I find an image for each post”, well, Generative AI to the rescue! I always just fire up Lucid Creations and use it to generate something fitting to the subject, or just something pretty at 768x512.

cross-posted from: https://lemmy.world/post/276633

Been using this one for over a decade. Works with Firefox’s bookmark keywords feature.

Make a new bookmark, set the link as follows:

https://lemmy.world/c/%s (or your own Lemmy instance)

And in the “Keyword” field, use “c” or “lemmy” or whatever.

Now, when you want to visit a specific Lemmy community on your home instance, you can simply type:

“c community_name” in the address bar, or “lemmy community_name” in Firefox and it will automatically open the community.

Hey y’all I wanted to make something clear. While the lemmy.dbzer0.com allows anyone to create community because I feel there’s a lot of creativity to be found by giving people this freedom, I also don’t want a sea of flotsam in our communities list.

So while I’m not going to shut down community creation, I am planning to start curating the available communities a bit more from now on.

What it means for you is that if you plan to create a community, I expect you to actually have a plan to grow it. Not just register the name so that you squat on it and hope other join so that you end up the top mod other users built-up.

Practically this means that we expect to see some activity on those communities, a sidebar that explains what it’s about, reasonable names and titles etc. Please also do the effort of adding a banner and an Icon. I’ve developed a free Generative AI art tool you can use even!

Communities which we perceive to be abandoned or squatting will be summarily purged. My plan for now is to purge empty communities within 1 week after giving a warning. I haven’t decided how to deal with communities which have posts and subscribers yet, but if it’s inactive long enough and the amount of posts is trivially small, I’ll probably start purging those within a month. I do not think I’ll purge communities with significant amount of posts and subscribers however.

I also plan to post a report about purged communities when we do so, so that people are aware.

Thanks for reading. Let’s try to keep the quality of the divisions by zero sufficiently high.

EDIT/UPDATE: Recent versions of lemmy make this even easier by allowing turning the !instance format into a relative link to your instance. For example !div0@lemmy.dbzer0.com. However when you do this, don’t use the auto-fill option which turns it into a markdown link, as that will break this functionality.

When you link to another community on lemmy with a absolute link like so Div/0 this links to that community directly from that instance’s domain. This means users who follow that link from other instances, will not be able to comment or subscribe. They will have to go back and edit their URL manually to workaround this.

If you instead link to a community using a relative link like so Div/0 it will lead them to the community using their own instance as a mediator, allowing them to interact with it naturally.

The source for the above relative link is like this [Div/0](/c/div0@lemmy.dbzer0.com). So basically just add only the /c/... part and ensure your instance’s domain is at the end