This is an opportunity for any users, server admins, or interested third parties to ask anything they’d like to @[email protected] and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today.
Note: This will be the thread tmrw, so you can use this thread to ask and vote on questions beforehand.
Right now, instances with transphobic and racist content like exploding-heads are still listed on join-lemmy.org. Are you planning to implement a Server Convenant like on joinmastodon.org? To be listed on joinmastodon.org, an instance needs “Active moderation against racism, sexism, homophobia and transphobia”.
Have you considered a feature like “sibling community”?
What I mean is, for example, car community on server 1 marks itself as a sibling community to a car community on server 2. Similarly server 2 marks itself as a sibling community to server 1, ie it is two-way.
When communities have been linked bi-directionally, any post and comment are shared between the two sibling communities.
This would allow bigger communities to form out of smaller communities, thereby preventing discussions from being fragmented and showing the true size of Lemmy, across servers.
We have an open issue for collections of communities, but not for any complicated trees of communities. Creating and linking community trees sounds really complicated, and I don’t know how all that would work.
I don’t know how the code is currently working, but I like this feature idea and would suggest to start very simple and proceed from there.
For example you could: a) Make a list of communities that are siblings with their id and instance b) add a toggle to view sister community posts yes /no c) query all communities, list the last x posts from each with time constraints, e.g. not older than 1 day or hour depending on the community post frequency d) list them sorted by time of x , depending on what was chosen
The biggest issue I see with this simple approach, besides others, is that different communities are different in terms of activity / post frequency. So ideally the better, but more effort, way would be to let each community instance communicate their posts themselves via a query with activity metric parameters. Basically the amount of returned posts would depend on common parameters set by the most active instance.
It’s not yet thought out, but just getting an mvp started and test the waters would probably be better than having it perfect right away while working on it for months
pretty good idea, i figure moderators would be shared between communities?
I think the ama is over? But I like this idea! Not sure of the implementation headaches, but it seems a lot more feasible than the other proposals I’ve heard, most of which involve making community names globally unique
I’m gonna be asking hard questions, I think, sorry about that. I hope you consider it tough love considering our past interactions.
As an instance admin, I have some questions:
-
How are you doing? I know there was a lot of pressure when things blew up and it seems to be calming down a bit now.
-
How is Lemmy doing financially?
-
Considering past releases and their associated breaking bugs (including 0.18.3), what measures are you taking to help prevent that?
-
Can we consider the possibility of downgrades being supported?
-
Why are bugs affecting moderation not release blockers? Does anything block releases?
-
Are there plans to give instance administrators a voice in shaping the future of Lemmy’s development?
As someone who is trying to help with Lemmy’s development, I have some other questions:
- What do you think are the biggest problems with Lemmy as a software project and what are your priorities for Lemmy?
- Considering fairly low amounts of developers contributing to Lemmy, how are you working to help new people get into the project?
- Do you worry about the message it sends to potential contributors when the main developers are working on a different project which competes with the former? (Example: Lemmy-ui vs Lemmy-ui-Leptos)
- Considering most work is done voluntarily, how are you trying to organize and prioritize work?
- Do you believe you are stretching yourself too thin between Lemmy, Lemmy-ui, Lemmy-ui-leptos, Jerboa and Lemmy.ml? If so, what are you doing to help you focus?
Alright second part:
- The biggest problem is definitely that there are too many things to do, but only the two of us working on it fulltime. The day only has so many hours and its impossible to keep up with everything. Thats why community contributions are really important.
- The amount of contributors is very high compared to a few months ago, its not easy to keep up with all the pull requests. Its going to take some time for processes to adjust to the new scale, and for new contributors to learn how everything works.
- This is a question for @[email protected]
- People work on whatever they are passionate about. Generally that works quite well.
- I am only working on Lemmy and thats already a lot. So another question for @[email protected]
Wow lots of questions here.
- Im doing well, its exciting to know that so many people like the software Ive worked on for the last years. The first month after the migration was really stressful, but by now its calmed down a lot. Plus there are many contributors now which are helping a lot.
- Unfortunately the user donations are just barely enough to pay our salaries, by my calculations the income from Liberapay, Patreon and Open Collective is around 4000 USD per month. Luckily we still have some NLnet funding left, and should be able to work on those milestones now that things have calmed down. I hope the user donations will increase so that they can pay us proper salaries. Maybe even hire additional people, but that seems very optimistic now. It would also be good if we could find other funding sources besides NLnet, as its not clear if they will fund us another year.
- I think the “breaking bugs” were really minor considering how we had to constantly rush out performance and security fixes. This should get better as we dont need to make emergency fixes, and have more time to let the community test release candidates before making the full release.
- Supporting downgrades means that someone has to test them and report/fix problems. We dont have time for that, but feel free to do it.
- Like I said, our recent releases had urgent performance/security fixes so we didnt have enough time for testing. We also didnt find out about these problems until later. Part of the problem is that keeping up with issues is almost a full-time job on its own, so I rarely read them anymore. If you see something important reported, do let me know.
- No concrete plans, but I definitely think that admins are the main actors who should have a voice in development. Its impossible for us to listen to all the individual users, because there are too many and they often dont have the necessary technical knowledge. If you have some ideas how to facilitate communication between devs and admins, let me know.
Are we almost done? Nope, only halfway. Will answer the second half a bit later.
-
@[email protected], can’t reply to the thread here because the user was defed from us which is a pretty frustrating design for the purposes of reading a whole thread from another instance, but i’d just like to say that if you don’t self crit here you need to delete your avatar, maybe upload a picture of spez instead, because he says the same shit :) like a lot of your other posts but by god this is liberal shit that basically no one wants to see
I’m not asking anything because I’m a potato when it comes to software. I just wanted to drop by and say: thank you both for Lemmy. The platform is amazing, and it’s clear that you guys are pouring some heavy love (and labour hours) in it, as it’s improving at an amazing pace.
Thanks! We’re glad ppl are finding Lemmy useful, and enjoying using it!
🥰
Any plans for improving SEO? One of Reddit’s biggest strengths was being able to get very relevant results with a simple internet search. In time can you see something similar for Lemmy, even with its decentralized nature? I really you for doing this, thank you for your time!
Sorry, no question, only: Thank you for your hard work :)
o7. Glad to be of service
How do you see Lemmy working with duplicate communities on different instances? For example if Lemmy.World and Lemmy.ml have a PersonalFinance community, are people expected to cross-post? Or have you conceived of a system to allow people to find the right community efficiently?
I asked in the other thread about GDPR.
Nobody thinks it’s very interesting but if instances don’t follow gdpr, the entire network is at risk of legal consequences.
So please bring this up, even though it’s not very fun.
deleted by creator
I’m personally a hard copyleft developer, so I’d prefer that people making apps and tools for the lemmy eco-system, open source them, to benefit the community as a whole. Nearly all lemmy projects have adopted that standard, and are using the GPL and other hard copy-left licenses, and sharing their code freely with the community.
One example: various devs of lemmy apps have asked me how we build comment trees. Because lemmy’s source code is open, I was able to share the exact code from lemmy-ui (typescript) and jerboa (kotlin). This is not something closed source developers are able / willing to share.
So I continue to recommend that developers heed calls to open source their applications. I developed my ThumbKey android keyboard, specifically because my requests to the MessageEase developers to open-source their codebase, after development had stopped, went unheeded for years.
Side note, but I’ve seen a lot of the discourse around Sync confuse FOSS, with making money. Of course developers deserve to get paid for their labor time! The thing is, FOSS makes no demands on how you monetize your software: “free as in freedom, not free as in beer”, is the saying. So its entirely possible to open source your app, and still charge for it if you like. And If someone wants your app for free (say via an unlocked APK), they’ll get it, whether its closed source, or not.
And yes, if an instance decided to insert ads, or becomes full of blog/cryptospam, I’d def recommend other instances defederate from them. I’d rather not lemmy become the ad-machine that other social media has become.
I definitely didnt expect it, nor did I expect that there would suddenly be more than a dozen different apps. But its not a problem, the more choices users have the better. Those who like such clients can use them, thout it affecting anyone else. Plus monetization of apps could potentially help to fund development of Lemmy itself.
For instances with ads its pretty much the same, more choice for users. But I really doubt that model can have any success considering how many free instances are around which are run by volunteers. Defederation should be unnecessary assuming that ads are only shown to local users.
What do you think of the neoliberal hell that lemmy.ml is right now?
I dont follow /c/worldnews so I dont see much of that. Also hexbear is federating now, so it might easily swing back the other way again.
I don’t share your optimism but I appreciate it!
For me the whole point of fediverse is not depending on a single party for your socials/subs. But the current climate in each instance forces users to have accounts in multiple instances.
As a Lemmy user I believe account migration should be a default Lemmy feature which enables true federation for end users. Any plans for this feature in the near future?
What’s your oppinion on lemmy being used by a few hundreds of people for quite some time and then recently exploding overnight with new instances and tens of thousands of new users. That certeinly changed some things…
Any plans to make it easier to interact with links to other instances?
The QoL value to automatically open links to other instances inside my current instance would be enormous.
I asked this in the original thread but I’ll repeat it here:
-
Are there any limitations with the ActivityPub protocol you find limiting? Do you have recommendations for future versions of the protocol?
-
Do you have any thoughts on the AT Protocol (a potential competitor to AP)?
Limitations no, if anything the protocol is too extensive and lets you do too many things (or do the same thing in different ways). But thats somewhat expected for a protocol which can handle all types of social media platforms. I think the protocol is fine as is, but it needs minor changes here and there to keep up with how it is being used in the real world. The FEP process is doing a good job of that.
From what I know the AT protocol used by Bluesky is entirely centralized, so it doesnt look like a competitor yet. They claim that it will be decentralized in the future, but I will believe it when I see it. For now the decentralization seems more like a marketing gimmick.
I’ve been following BlueSky closely for a while and I’ll just add a few points here:
-
There is currently a federation sandbox for developers, it’s definitely on the way but it is a significantly different model than AP. Severs are really “dumb” and it has an emphasis on using a handful of services to crawl the network and generate a pipeline of all posts.
-
Moderation and custom algorithms are also a part of the decentralized model. Custom algorithms are out now, and custom moderation services are also under development.
Having played with both AP and ATP a fair amount they definitely both have strengths and weaknesses, very different approaches to decentralized social networking.
-
-
