rglullis

joined 1 year ago
MODERATOR OF
[–] rglullis@communick.news 1 points 57 minutes ago

If this is so important to you, you are still very much free to start your own instance and see how far it goes.

[–] rglullis@communick.news 1 points 1 day ago

If registration are closed, mods would be exclusively from outside. And, since reports are not federated, this communities would be prone to difficulties for moderation. Unless reports are correctly federated, I don’t think this is a good idea.

It wouldn't be that difficult to write a little bot that can keep track of each moderator is on each community, and make the report on the instance of the moderator directly.

centralization of domain names under you.

The idea is to have the domains under the control of this collective.

Can you name any advantage??

  • Less concerns about political fights among "user" instances affecting communication among communities
  • Less tribalism regarding "what community is the canonical one". Users and admins are of course completely free to create their own communities, but for the majority at large they could just look at the topic-based instance and think "ok, that one will be a good entry point".
  • Less load on all servers. LW has a good chunk of the most active communities, so all activity from other users end up going through that. More instances with cleaner separation => better load balancing.
  • Easier content discovery: no matter if users go to a small or big instance, they can be pointed to the different servers to browse according to their interests.

hardly anything huge to really break the inertia or status quo of things as they’re now…

As it is right now, yes. But I am working for a potential future where we can migrate 10, 20, 50 times more users than we already have. Consider that I am also working on a tool to help people migrate from Reddit and in making some modifications on the Voyager app to integrate automatic migration from Reddit to Lemmy. If the gates finally open, this will be very much needed.

[–] rglullis@communick.news 1 points 1 day ago

My idea would be to have a community request functionality. I am halfway there with fediverser. People can request communities to be created in a given instance, but it still missing the part where members can provide the data (name, description, icon, logo, etc).

[–] rglullis@communick.news 23 points 2 days ago (1 children)

Could all of you go outside for a little bit, touch grass, smile at a stranger?

Sometimes I get angry at myself for wasting my time in pointless discussions, but this is next-level wankery. If you know that hexbear is a pig hut, don't come here to complain that you are full of mud and pig shit in your face.

Reported as off-topic.

[–] rglullis@communick.news 3 points 2 days ago (1 children)

Well, surely, but this constraint is there by design. The point of these users is not to attract users, but to have thematic communities that can be followed by users elsewhere on the Fediverse.

[–] rglullis@communick.news 4 points 5 days ago

benefit your administrative influence from your instances

They are not going to be "my" instances.

acknowledging any objective perspectives.

Oh, I thought it was pretty clear: my objective with these instances have been to build the infrastructure necessary to get people out of Reddit. I want to gain from the growth of the network, where I expect to profit from getting customers on my hosting business.

I don't need/want to make money out of these instances, I am just commoditizing the complements.

[–] rglullis@communick.news 4 points 5 days ago
  • Your key is your identity. If it's lost or stolen, you can not revoke it. That alone will make it virtually impossible to be used as an official application protocol for any organization.

  • Usability is even worse than anything on ActivityPub

  • Moderation is entirely punted to the end user.

  • (not technical, but relevant) it is completely dominated by Bitcoin maxis

[–] rglullis@communick.news 4 points 5 days ago* (last edited 5 days ago) (2 children)

A type of federation where there is no "home" for a community any more.

This is not federation anymore, but an entirely different architecture. Nostr works like this, but it also has its flaws.

[–] rglullis@communick.news 4 points 5 days ago* (last edited 5 days ago) (5 children)

Dear Lord, I had no idea one could be so lost and still be so confident when making an argument.

I am not trying to be mean, it's just that you are arguing against things that are completely made up.

So instead of one admin being able to take it all down we have multiple

Shared ownership is a policy to prevent single-points-of-failure. Every large-ish instance has multiple admins. This is even a requirement in the Mastodon Covenant: your instance is only listed on the joinmastodon site if the instance has at least two people who can independently access the admin panel.

Could go and notarize shared ownership of a bare metal server I suppose?

You don't need any of that. As long as the collective has control over the domains and that backups are created and available for everyone, admins could simply move the instance to a new place with a new deployment and a DNS change.

It does not mean that every admin needs to have direct access to the server, and it does not mean that the server will go down if one of them goes rogue. Every minimally competent organization has security processes in place to avoid that.

But we have multiple admins, so these instances would be uniquely able to process very large numbers of users on account of having more than one admin?

I can't even imagine how you go to this non-sequitur. The idea of having multiple admins is only to ensure that these instances are not under control of a single individual and would not be represent a systemic risk to the overall Fediverse.

If you want communities to be resistant to server removal

Another non-sequitur.

So that even if the original instance is gone, everyone keeps interacting with their local federated community-copy

How is that working out for the communities on feddit.de, and the many other instances that disappeared in the last year? Did you notice they are gone?

In particular because that still doesn’t solve the problem because now you got people able to either moderate each others copy

Another non-sequitur. Are you sure you have a clear understanding of how federation works?

[–] rglullis@communick.news -4 points 6 days ago (7 children)

From your response, it seems that you did not read the blog post. The instances are still going to be connected to the Fediverse, the idea is just to keep user registration closed. Users from other instances will continue to be able to follow and interact with it.

[–] rglullis@communick.news 0 points 6 days ago (1 children)

Feel free to register a football domain. I will host it for you, free of charge.

[–] rglullis@communick.news 1 points 6 days ago

I just think that letting people making accounts tied to their favorite topics would get more people interested in joining them.

Could be, but I guess we now just arguing opinions. And given that I am personally hold the opposite view and I don't want to be be identified by my interests, I am not going to push for something that I fundamentally disagree with.

 

I have a number of Lemmy instances meant for discussion groups around specific topics. They are not being as used as I expected/hoped. I would like to set them up in a way that they can be owned by a consortium of different admins so that they are collectively owned. My only requirement: these instances should remain closed for registrations and used only to create communities.

 

Another SFW community: !guitarporn@sfw.community . Whether you have a large collection or just that one special piece of gear that you love, this is the place for you to show it off.

 

!system76@hardware.watch is a community to talk about and get support for their hardware, their POP!OS Linux distribution and the upcoming Cosmic DE

 

I'm spending more time than I should playing this with my kids on the phone...

!mariokart@level-up.zone

 

!tennis@matchpoint.zone

A community to discuss all levels of tennis, from tour professionals to recreational players.

 

I'm resuming my work on Fediverser, and I need as much help as I can get to build the Recommended community map. This crowdsourced data will be one the key points for instance admins that want to make use of the Fediverser services, and it will help immensely for people who want to migrate away from Reddit.

How does it work? The front-page gives you a list of all the subreddits with its corresponding recommendations of Lemmy communities. The ones that have no recommendation go to the top of the page. One example. You can open the page for that subreddit entry and make all the suggestions that you think are appropriate.

Every suggestion goes into a queue which I can then review and merge to the main database.

One of the things that I will be adding soon is the ability to request a community to be created. For subreddits which there is no equivalent community, people will be able to fill a form (similar to the "Create Community" page on Lemmy's default client) which will check what is the best participating instance in the network, and if the instance admins approve, the instance can be created right away.

How can you help?

  • Categorize the subreddits that have no entry.
  • Reaching out to the mods of the uncategorized subreddits
  • Creating community requests for the ones that are still missing.

Thank you!

 

I went to look into the activitypub federation package from Rust and noticed that it does not support JSON-LD. This took me to a search into other libraries, which got me to RDF-based crates. Just thought it was a good idea to share.

 

I'm exploriing the idea that would be the "reverse" of Libervia: an offline-first AcitivityPub application that keeps all information in the client and only relies on the server to be the receiver of the inbox messages. To make sure that the client can synchronize properly, I am considering two approaches:

  1. The server and the client need to use the same database which has a replication protocol (like CouchDB/PouchDB)
  2. The server receives the messages in the inbox via HTTP, but relays to the client via XMPP.

The first idea simplifies things a bit, but forces the client to use a specific tech stack. I'm also not sure if the server needs to have everything replicated, just the messages that the device haven't seen yet.

I'd also be interested in something like MUC, because I would use to let the server use rooms for things like Mastodon's "follow tags".

Lastly, because I'm planning to do this as a browser extension, it would have to be something that runs on the browser. xmpp.js seems like a good candidate (lots of contributors and reasonably well documented), but the last commit was from two years ago. Is it still being used/maintained? If not, is there any other recommendation?

view more: next ›