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.
Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.
You can also find major news on join-lemmy.org
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.
Neither @nutomic@lemmy.ml or I are too familiar with the GDPR, so we don't know everything that it requires. Lemmy doesn't do any logging of IPs or other sensitive info, but of course instance runners could be doing their own logging / metrics via their webservers.
We have a Legal
section under admin settings, that's an optional markdown field, that can probably be used for it. We'd need someone with GDPR expertise though to help put things together. Lemmy is international software, not european-specific, so we have to keep that in mind when supporting GDPR.
As a person who oversaw the implementation of GDPR in a large software house (which wasn't EU specific, but had to in order to operate legally in the EU), the requirements were:
For us, this was multiple ad companies. We had to e-mail each one, ask them about their GDPR implementation (most of them were somewhere between "we're thinking about it" and "we have an e-mail address you can send something automated to and we'll get to it sometime within the next month"), and then build an automated back-end system to either query their APIs for automated deletion, or craft/send e-mails for the more primitive companies.
As far as the data being deleted, it was anonymized IDs that were tied to their advertising IDs from their mobile phones. I used to try and argue that "no, it's anonymous" - but we also had some player data (these were games) associated with that, so we ended up just clearing house and deleting everything on request.
So, legally, this means every instance - in order to be GDPR compliant - would have to inform every instance it federates with that a user wants their data deleted. If you're not doing that, you're not fully compliant.
Kind of shitty, but that's how it went for me. (this was back when GDPR was first being released)
Edit: Also, the one month thing was relevant: you have 30 days to delete GDPR stuff after receiving a data clear request. I don't recall what the time was for a "see my data" request. Presumably, though, on Lemmy the latter is superfluous as all your data is already present on your profile page. An account export option would be enough to satisfy that.
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?
Its a problem, and at the same time a feature. For example, you can have two communities named !news
, that pertain to completely different topics based on their instance:
This also isn't unique to lemmy, since reddit too had tons of duplicate communities for the same topics.
Just like on reddit, the network effect will run its course here: unavoidably there will be a lot of cross-posting on duplicated communities, until people center around their favorites, based on quality of content.
There are a few tools out there too, like https://lemmyverse.net/communities , that can help people find communities to subscribe to.
Overall tho, I'm against the concept of "combining / merging communities" that are run on different sites by different people. These should be curated and controlled by the people who created them.
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!
Lemmy-ui supports SEO, and also has opengraph tags. If there's anything else needs to be added, we're open to PRs.
Side note: For me personally, as @FrostySpectacles@lemmy.ml suggested, SEO shouldn't be a focus. SEO is such a gamed system, catering to a few giant search companies, and results are increasingly becoming unusable, especially in the past few years. I can barely find the things I want to search for, and almost always have better luck using internal sites search engines. So I'd rather focus on improving lemmy's search capabalities and filtering, than catering to google.
I second this. I know SEO is a controversial term with Lemmy's core audience, but being able to find posts through a search engine is pretty darn helpful. It'll also help more people find their way to Lemmy, which will diversify the range of communities.
If you're not sure where to start, Google's free Search Console can give you insight into how your site ranks, how people are finding you and which factors are preventing instances from appearing in search.
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”.
I'm gonna be asking hard questions, I think, sorry about that. I hope you consider it tough love considering our past interactions.
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?
Wow lots of questions here.
Are we almost done? Nope, only halfway. Will answer the second half a bit later.
What's your opinion on app developers making Lemmy clients with tracker-infused ads on their free version? Is it something you ever anticipated when you were first developing Lemmy?
EDIT: Also a similar one, what about instances potentially deciding to display ads out of nowhere? Could defederation be a tool here to discourage that?
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.
Hope multiples are ok ...
Haha youre a very curious one :D
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.
Any plans to improve the sorting algorithm so that there's a good balance of fresh posts at the top that's also fairly active? And to help promote smaller communities that would have otherwise been dominated by the posts from bigger instances.
Any concerns about duplicate communities across multiple instances? People have made the argument that it's like having different flavors of subreddits on Reddit, but it's a flawed analogy. Individual instances have incentive to make their own communities flourish, whether or not there's a duplicate already available.
Its been bothering me too, that the large communities have been swamping out smaller ones.
As one solution, the closed PR linked in this issue has some more context, but we plan to add a Best sort, that retains the qualities of hot, but gives a boost for small communities over larger ones. This shouldn't be too difficult to add, as its very similar to hot.
Another benefit of lemmy being FOSS, is that we have the option to add many more sorts as time goes on.
Any concerns about duplicate communities across multiple instances?
As some instances grow, server costs are becoming significant. Right now, servers are only funded through donations. Do you see the development of anything else to help fund server costs?
If lemmy is working as intended (many small, connected servers), hosting costs should be small: like < $10 USD / month. (images are another issue, but I'll answer that in other comments).
Of course we don't plan on adding any monetization directly into lemmy or its UI, including ads, or required payments. Right now at least the best way is to put donation links in your site sidebar.
First of all, I'd like to say thank you and that I appreciate your work. Lemmy is great and I've found a new home (at least for the foreseeable future). I first joined lemmy.ml once I learned about lemmy, and I have to say I had a good experience there. You guys even responded directly to my noob questions, and I honestly felt welcome which helped me decide to stay.
My questions are about account migration. As you may have already seen, I'm not with lemmy.ml anymore. The reason is I saw you guys stickied a post encouraging users to use different instances (since the server was having trouble with the influx of redditors at that time). I figured I'd help by first moving to a smaller instance. I have no regrets, although switching was a bit tricky since I had to start from scratch.
What are your thoughts on account migration? Is it in the works or is it something that's a little far into the future? No pressure since I know you guys are busy with other stuff.
Account migration is not in the works, and I consider it very low priority. Unlike Mastodon, Lemmy isnt focused on individual users, so it doesnt matter much if you start posting from another instance one day. If its important for you, you can always put a link in your profile to your other accounts. I would rather implement a way to export/import account data. Thats much simpler and can also be used as a backup in case your instance goes down.
Hi! This isn't really a question, but I was a former admin on Lemmy.ml and I just want to say that I really appreciated the opportunity to be on your team and it was a really valuable experience for me! I'm no longer an admin due to inactivity and personal life events causing me to no longer have the time to serve such a role, but I enjoyed the time I was and I really hope I was able to make a positive contribution to the instance!
Thank you for your continued work developing this project and running your instance comrades! This is still by far my favourite fediverse platform, actually, favourite social media in general. I intend to continue using both Lemmy.ml and Lemmygrad and I hope I can continue to contribute by using Lemmy when I have the chance!
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.
First, just want to say thanks for building and maintaining Lemmy. It's an incredible project, and it provides an incredibly valuable public forum that's completely open. This is the way internet was always meant to work before it got hijacked by corporations.
The questions I'd like to ask would be whether the platform is developing in the way you originally envisioned, what surprised you in terms of how the platform ended up being used in the wild, and what were the biggest technical and non technical problems that came from the rapid growth after the Reddit migration. And finally, how would you like the platform to evolve going forward, and what your long term vision is.
I mostly imagined the slow but steady growth we'd been having, and def didn't anticipate that reddit would mess up so badly that a massive chunk of users would migrate from a multi-million dollar enterprise software, to a hobby project developed by a couple of marxist-leninists 🤣 . But so it goes, with all these late-capitalist social media companies alienating their users, monetizing them in any way possible in search of declining surplus.
The biggest non-tech problem, is just the overwhelming amount of notifications. Companies have multiple layers between devs and users, to separate, order, and create a more controlled explosion. That doesn't exist here, so we get hundreds of notifications every day, with everyone treating us as their personal issue tracker.... and I basically would get nothing done if all I did was respond to them. Luckily things are calming down a bit now.
The biggest tech-problem was the performance and security issues of so many users joining the network all at once, and luckily we had so many wonderful community contributions to help stabilize that.
And finally, how would you like the platform to evolve going forward, and what your long term vision is.
We should be ambitious, and wantthe fediverse as a whole, on the long term, to replace big-tech. Every user we draw away from them, is one less person exploited for their data and treated as a commodity.
Technically, I'd just like us to continue making the software better, maintaining the code, and adding features.
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.
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.
I'm gonna ask some tough questions, but I am hopeful to get a response. Thank you for all that you do.
Thanks!
All
tab will be full of potentially illegal content if you federate with NSFW instances. We want to focus on dev, and not on legal issues, so for that reason we won't federate with NSFW ones.