- cross-posted to:
- linux@lemmy.eco.br
- archlinux
- linux@sopuli.xyz
- linux
- cross-posted to:
- linux@lemmy.eco.br
- archlinux
- linux@sopuli.xyz
- linux
Check out https://lemmy.kde.social
deleted by creator
deleted by creator
So full disclosure, the instance is not 100% official since it is not hosted on kde infrastructure, as this would create too much work on KDE’s sysadmin to maintain another service.
But I manage it, and I’m a long-term KDE contributor (5 years now), maintaining most user-facing websites and various applications (Kalendar, Tokodon, NeoChat, Kontrast, …). I’m part of the KDE Promo team (I have access to all the existing kde social media accounts) and of the fundraising team. And in the past, I was moderating r/kde, but I deleted my account a while ago already. And finally, I already maintain https://kde.social, which hosts the mastodon accounts of a few kde applications as well as of a few other contributors. (all that in my free time)
Hopefully, this is legit enough :) And I will add the link to the Lemmy instance in the footer of kde.org
deleted by creator
deleted by creator
@UrbenLegend @carlschwan
If you look at KDE’s mastodon (https://floss.social/@kde) you will see that they boosted Carl’s toot announcing it (https://floss.social/@carlschwan/110595345431992114)
Everyone subscribe! We should make it at least the main KDE community.
Love me some officially supported federation!
Here’s a link directly to their community: !KDE@lemmy.kde.social
deleted by creator
Before you had to fiddle with the markdown link manually. As of v18, you can just type out the name of a community in the
!name@instan.ce
format, in plain-text, and it will become a working link.I believe links like this will be sorted automatically in Lemmy 0.18 but until then links are like this without the space between ] (
[!community@instance] (/c/community@instance)
Currently if the community hasn’t been discovered by your instance then you’ll get a 404 error like I just did, apparently it’s a known thing and you need to search for the community before accessing it, see here - https://github.com/LemmyNet/lemmy-ui/issues/1335
They are on lemmy.ml, they are already on v18, same as me with sopuli.xyz.
deleted by creator
deleted by creator
Unfortunately my instance (https://feddit.de) is not federating with it yet.
Do they need to approve each and every instance manually? I thought it would happen automatically as soon as someone is trying to subscribe to a “channel” of another instance. No?
I’m not familiar with the exact process yet. But doesn’t that mean if you wanted to run an unfederated instance, you’d need to manually block every other instance there is?
That’s how I understood it. There is maybe a way to blacklist everything (like using a wildcard) or disable federation? I don’t know. Maybe I will try to run my own personal instance just to learn how it works :)
By default, lemmy will federate openly with any other instance. You can then block specific instances. (Disallow-list)
You can additionally disable federation altogether, or only federate with a specified list. (Allow-list).
Thank you for clarifying that.
It seems to work now, I’m on feddit.de too and I just subscribed to !KDE@lemmy.kde.social
Why start a new one? We already have tons of users and content here.
Because it’s better in term of health of the fediverse if we don’t end up with only a few big instances like lemmy.ml. Also people can interact with lemmy.kde.social while not being on that instance
deleted by creator
I mean it requires a validation from the mods to be accepted. Makes it slow for people to join in tbh.
I’m trying to keep the size in check and limit the possibility for users of this instance to spam other instances.