That sounds great and all on paper but that also requires a ton of moderation overhead as now every small instance has to have enough mods to deal with everything being posted, since moderation would be local only. So all the spam and CSAM would have to be taken down by each individual instance. Would also somehow have to find a way for instances to pull the hashtags out of every federated instance too. The way it works on Mastodon is someone follows an account and that causes the data to get pulled in. On Lemmy you don’t follow users, you need a way to pull the data in.

The end result would be a mess of instances not even agreeing on vote counts with vastly different comments too, and even the posts.

Lemmy doesn’t aim to be an uncensorable platform. I join communities for the content, the users, and for better or for worse, the mods too.

The individual problems of having to deal with the duplicate communities will get worked on eventually.

Does Lemmy even have print CSS or is it more like the site’s style is so basic it just works? I looked quickly and apart from hiding a few elements, it doesn’t look like it really tries to be printer friendly at all.

Lemmy updates are a little touchy and buggy, can’t blame them for taking their time. It’s only been out for like a week. They have to load a backup on another server and test it out to see if there’s any issues with the upgrade and how long it’ll take. They have to plan downtime and set aside enough time to do it, handle any issues and a potential rollback.

As a general rule it’s the admins that have to deal with legal and technical problems, so the features for admins are a much higher priority for development. Protecting whole instances is more important than user focused features because if instances get taken down that’s a whole bunch of users that need to find a new home.

In the meantime many of the third-party apps can take care of some of those features.

Gotta remember we’re at version 0.19.3. That’s still very much an early access platform with the quirks not quite figured out yet.

It’s just a shortened version of my name. Mine comes from elementary school. One of my classes had 3 Max in them as the name was really popular for my generation. So we just started using Max-X where X is the initial of the last name.

It has stuck since.

If the server’s going to enforce this then I feel like the default should be total up and down, as all the others can be calculated from those two numbers by the clients. Other methods I would foresee be used by instances that somewhat wants to hide or fuzz the numbers, so that’d be an opt-in thing that defaults to maximum transparency.

That’s hard to enforce with federation, how do you specify the limit of single user instances vs big instances like lemmy.world? You receive all of it through the same server, and you may have hours of activity backlog queued up if your server had federation issues or was offline. They’ll come pouring in as fast as the remote instance is willing to send them.

If you apply the limit on specific instances, you may end up with instances where the admin runs bots that may bust the limits and it may be high or off as a result. Or the admin’s just like “eh, I don’t like limits”.

Doing security in the wide open is hard. It’s trivial to observe things like shadowbans with Lemmy.

Even with ratelimits, that also wouldn’t deal with the issue with old abandoned Mastodon instances like we had with the japanese discord spam a couple weeks ago where the made accounts across the fediverse.

I don’t think it supports WebPush at the moment, no. But it would be the technically correct way to implement this. It’s an open standard that’s not tied to any particular company and ecosystem.

Ideally it would support WebPush which would allow your app to register with any push notification service that supports WebPush.

WebSockets would drain battery and also add a lot of load on the servers to handle all those connections. Implementing specific notification services directly on Lemmy isn’t quite where it belongs. Plus you don’t want all Lemmy admins to have to register to Apple Push and Google’s FCM and potentially others. With WebPush you can have your own server as a relay and then dispatch to expo/APN/FCM as needed.

I wrote a proxy specifically for that: https://github.com/maxpoulin64/lemmy-api-compat

@iso@lemy.lol If that’s the main problem you have with it, this will make third party apps work.

Boost for Lemmy doesn’t appear to be, last update was in September.

I’ve been using a custom proxy to rewrite auth for Boost to work since my accidental 0.19 update. It’s been working great considering how quick and dirty it is.

My partner also reports the Mlem chokes completely on 0.19’s JSON response. I suspect fields were added and it’s not coded to ignore extra fields when deserializing. I haven’t confirmed it’s still present on rc4, I’ll update my instance and report back. Edit: confirm Mlem still doesn’t work even with the proxy hack. Without the hack it can’t authenticate at all. Latest git main branch might, this is based on the 1.1 current release which is about a month old.

I wish I did that, at this point my TypeScript template errors are as long as C++'s ._.

The default Lemmy UI is pretty lightweight. Do you have extensions, especially Lemmy home instance redirection extensions?

I’ve definitely used one of those that made browsing lemmy incredibly slow as it was busy rewriting all the links.

Lemmy loads basically instantly on Firefox on my desktop, and same on my phone with Chrome.

API keys is what identifies the client/application. So basically, Reddit sees it as me using a personal custom app or script, and it’s therefore not blocked.

They didn’t shut down the API, they just made it prohibitively expensive to use. For most people, that falls into the free tier.

Also helps to clear the cache of the Play Store app and force stop it and open it up back again to see the change.

Changing the icon doesn’t remove the old one in either version, it just makes a new one

Custom API keys

Check sticky, you can enroll in the testing group and get it.

That’s probably something Rubén needs to handle. I didn’t realize it would come out this huge lol. That’s why we’re bug testing this!

You can replace the API keys with your own with ReVanced.