Keep in mind that user-level instance blocks are not the same as instance-level defederations. AFAIK, it only blocks the communities. You'll still see comments and posts from that instance in other communities and that instance will still influence your feed with their votes.
It is better to go to an instance that defederates or to convince your current admin to defederate.
Punycode is not solving the same problem. Punycode solves Unicode in domain names. Percent encoding is for Unicode in URL paths. Lemmy only needs to worry about the paths, Punycode should be "supported" out of the box without any special handling
Yes, storage costs matters. I think it's honestly crazy that Lemmy caches images as much as it does. It would be great to be able to just disable it completely, but alas you can't do that without disabling uploads for your own users either (at least I don't know how).
Yes, but honestly unless you're very big, federation queries are the bulk of the processing and stuff from your own instance doesn't matter that much. I mean think about it, do you think the 100 active users on your own instance is what costs or the 10000 users posting all over the fediverse is what matters? Obviously the latter. So again, local user count is not that impactful.
ActivityPub users need to be identified by some identifier in the URL, and Lemmy chose the user name to be that identifier. As a result, non-Latin usernames become… complicated.
Sorry but this is just false. URIs can easily encode UTF-8 characters and it's perfectly standard to do so via percent-encoding. Example: https://en.wikipedia.org/wiki/😂. Your browser will even automatically convert that 😂 into the appropriate percent-encoding and will even display the emoji in the address bar, even if that is not the "true" URI.
This is, if you ask me, an unnecessary limitation in Lemmy.
No thanks, I’ll be staying with datastruct.nextState() rather than const nextState = prevState.nextState()
You can easily do the first option in Rust, you just use the mut keyword. That's it, nothing more than that. And you'll find that you quite rarely have to do that, and when you do it, it's actually quite a useful signal to be aware of, since mutability sometimes means a bit more surprising data changes.
I wouldn't even call that a functional feature, that's just the language being based on expressions and bool having a then method. It's more object-oriented in that sense if anything tbh
I really think you should give Rust a chance. It is not a functional language, like Haskell. Haskell is a hardcore purely functional language. Rust is not a purely functional language - instead it just borrows a few features and ideas from functional langauges. It also borrows ideas from object-oriented languages and it is inspired by C++ in some aspects (or has at least learned from C++, I guess you could say).
Could you maybe elaborate what it is about the functional ideas in Rust you don't like? I really only see them as benefits - Rust is like the best of both worlds. The good stuff from functional and the good stuff from object-oriented.
Sorry but immutable by default just makes sense. When you start coding Rust you'll see how rarely you actually need to use the mut keyword. It's quite rare actually.
The number of users is not really what drives costs honestly. Or at least, it's not like a linear relationship. I think actually having many popular communities might be a bigger issue.
I mean, I can't really take credit - the users on Feddit.dk are the ones that deserve the praise. I've been very surprised at the willingness to donate. We have almost 18 months of runway and that runway has mostly only gone up as time went by. Feddit.dk is not going anywhere anytime soon :)
About 62 USD per month. I post monthly finance updates. All the costs are covered by user donations so far :)
It might be possible to do it cheaper, but I feel I got a good deal for some very high end hardware so this setup should be scalable going forward for a long time.
I was kinda baffled by this too. I like the general idea that they present (you need to pay your own long-tenured engineers higher than market rate cause they actually know more about your own system), but this idea of a formula? What, are you gonna start counting git commits? A formula sounds like a super weird way to solve that problem.
Just look at the engineers that add value in your company and pay them a fair market rate. When someone leaves, find out what salary they get in the new job and ensure all your remaining engineers get at least that amount and adjust as you go along. Something like that perhaps.
Yea so the point is that your followers don't automatically see your upvotes but your followers will see what you boost (repost)? I guess that makes sense.
Could the same thing happen on the Fediverse? I mean could a community get overrun by bot posters without any actual humans posting? I'm not sure what the endgame of doing that would be.
Yea that could in theory be possible - the big problem is that it requires people to hold their own private key and manage that, both securely and conveniently. And well... tbh I just don't see that happening. If you need to keep your own private key and also keep your own password, I really don't see any non-techie people ever using the fediverse.
There's also the issue that if that private key is leaked, there is no going back. Your identity is stolen and you can do nothing to take it back. This is different from if your password gets leaked - in that case, an admin could in principle step in and reset your password and you could regain control of your account. This happens all the time when people's Facebook accounts get "hacked". They report it to Facebook and get their account back. This is impossible if it relies on a user-held private key.
It's a neat technical solution that unfortunately forgets the human, as is often the case.
SorteKanin @ SorteKanin @feddit.dk Posts 15Comments 1,655Joined 2 yr. ago
Keep in mind that user-level instance blocks are not the same as instance-level defederations. AFAIK, it only blocks the communities. You'll still see comments and posts from that instance in other communities and that instance will still influence your feed with their votes.
It is better to go to an instance that defederates or to convince your current admin to defederate.