![](https://feddit.dk/pictrs/image/7c6b6582-40a1-412b-99be-35694d7af85a.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Does it though? You can still put up a fork somewhere else as long as you uphold the license right? Unless I guess in the case where the license explicitly disallows forks, but I don’t think that’s very common (can you even do that?).
Does it though? You can still put up a fork somewhere else as long as you uphold the license right? Unless I guess in the case where the license explicitly disallows forks, but I don’t think that’s very common (can you even do that?).
Because CPU registers are all powers of 2, i.e. exponential in this fashion. And it’s also just the same reason - 64 is high enough, why go to 96 or 80 or something?
I’ll probably update within a week as well :)
I’m quite sure such on the fly price changes are illegal. At least here in Denmark.
Even reddit is still niche when it comes to social media and has always been. It’s become a little more mainstream the last few years, but for most people social media still equals Facebook, Instagram, Twitter, Snapchat and such.
Very nice even :D
But maybe Rust isn’t that niche, but the Fediverse apps and projects are niche themselves.
Lemmy is niche even within the fediverse, where microblogging still dominates and the threadiverse style apps are smaller. It’s just not a very large space.
I haven’t had big problems honestly. Still have less than 100GB of storage, which is like 0 dollars on object storage.
I found it very easy to start with the ansible setup and later changed to self managed docker. I even moved servers once and it worked fine.
Overall I haven’t had any issues, but I’m also a software engineer so maybe I know more than others. There are some missing features for sure, but I don’t think it’s so bad so far at least.
Agreed, I would definitely not refer to the first one as self hosting without qualifying further.
I’d say yes but it also really depends where you go. I used to host Feddit.dk at DigitalOcean, it was expensive af for like no hardware at all. Now I use Hetzner instead and it feels reasonable, especially their server auction.
It attracts a different audience, so in aggregate it seems like your community is suddenly bigger because 1+1=2 right? What you don’t realize is that you’ve divided your community into two separate groups with possibly different wants, needs and cultures.
Unless that “one place” is an open, federated standard that allows anyone to participate with their own self-hosted server - i.e. “one place” = the fediverse, then it’s fine!
Nice avatar lol
Crossposts are broken in 0.19.4?
It is only for admins and mods. Tbh I think it should just be allowed for anyone to see.
Also the post complains about the amount of storage used by caching images but that was also fixed/improved in v0.19.4
You don’t need 0.19.4 to avoid large storage costs. You can adjust your nginx setup to set a limit on the size of images allowed. For example, Feddit.dk only allows images up to 5MB. Anything larger than that will be linked to rather than stored locally.
I already reported this a while ago and it has been fixed in a newer version. https://github.com/LemmyNet/lemmy-ui/issues/2441
I never understood the idea behind these kind of automatic slur filters.
First of all, why even allow the comment at all? Why not just remove the whole thing? Censoring just the slur doesn’t help that much and can just be confusing.
Secondly, by filtering the slur like this, it’s less likely that the person posting the slur would be reported and thus no moderator sees the fact that someone posted slurs (unless slur-filtered comments are auto-reported; are they? I don’t know). That’s the opposite of what you want! If you have slurs that should be disallowed, get people to report those that post them and tell people not to do it or ban them if they keep doing it.
When it’s filtered like this and nobody reports the comment, the user posting the slur will probably just continue doing it.
And of course in addition to all the above, there’s the problem that it doesn’t take into account the context at all, which is what leads to the image of this post.
I think it is solvable. Your instance keeps track of the instances it is connected with. It could just do the search and find the post on your own instance if the domain is among the connected other instances.
EDIT: Right, it doesn’t fix the problem of stumbling upon a link to a fediverse instance somewhere else. Not sure how you could deal with that one
Just hijacking the top comment to say that it has been suggested, just not implemented yet https://github.com/LemmyNet/lemmy/issues/818