If you want to get straight to the fun, I might recommend: https://cosmos-cloud.io/

It will handle all of the uninteresting stuff like docker, reverse proxies, ssl certificates, etc. You can get straight to adding apps either by pasting in a docker-compose, or getting them straight from the cosmos marketplace.

Also, it works with standard tools, so other than the reverse proxy, it’s easy to migrate away from if you want. I think the reverse proxy is just caddy, but I don’t know where the caddy config file goes or how to pull it out of the funky cosmos config format.

Or: maybe we can just keep paid influencer scams off the fediverse entirely? IMHO we don’t need or want paid content creators here. As soon as someone can make a buck from it, the entire network will be flooded with clickbait, AI generated posts, and worse.

Thanks, the Backwards compatibility is huge for us! We have a bunch of users who depend on mlem or thunder, so I was assuming I’d have to wait until updated versions of both of those apps was released to upgrade rblind.

Bonus third fix: If you notice that your pict-rs is using a lot of CPU or doing an unreasonable amount of IO, convert from using SLED (the default image repo) to using postgresql. The documentation for doing this is provided in the pict-rs crate.

The connection to the SMTP server is timing out. Are you sure the port and SSL config is correct?

These are the way. They usually come with a cable that splits from one USB A to four or more USB C. So you have a spot to charge them normally, but you can also give them a quick charge when you’re out and about with any random cable you have if you can’t find the splitter. And they charge much quicker than using a battery charger.

Same. Although sometimes I set up a public instance, because I’m setting one up for myself anyway, right? And then I have regrets LOL

If Lemmy got as big as Reddit, this would be an even larger problem. As a server admin, I’d like not to store several hundred gigs of text per day because someone subscribes to an active community. Unlike Reddit, Lemmy servers are not run by a company that can endlessly lose venture capitalists money.

Not OP, but I use miniflux on desktop, synced with Lire on IOS.

Born blind. I dream entirely in sound. People who went blind later in life, however, may still see in dreams.

For some reason I had Singapore in my head as being way larger like Japan or Korea.

How is this different from cosmos-cloud.io? The feature list looks identical.

Unfortunately, though, we don’t have the population of Singapore. While I would love this to work, I just don’t see merchants implementing yet another payment provider.

Right, but Canada is small enough that none of the large merchants are going to implement this, are they? Interac already has a payments API, and I’ve only ever encountered it used in the wild once.

How is this better than what already exist?

Sarcasm: Yup. The black people who were lynched should have just participated in local communities and confronted the KKK! That’ll fix everything!

Anyway, online isn’t the place to take up space and confront people. You do that in person. Online is where you come to get support, encouragement, and resources for the in-person fight. And that doesn’t work if your online profile is also local. For many people, there online participation cannot, and should not, be geographically local. Remember the “good old days” of the local BBS that you had to dial into? Isn’t it interesting that every single documentary full of sepia toned reminiscences about how wonderful those local communities were is entirely created by and featuring old middle-class white dudes? No women, no homosexuals or transsexuals, no people with disabilities, and no ethnic minorities? I wonder why!

Again, speaking from personal experience: blind people had NFBNet, but it wasn’t local. And the local BBS’s had so much ASCII art and other accessibility issues that we couldn’t participate.

And now, on local Reddits and Facebook groups, nobody uses alt text. I guess that’s my fault for not participating in a space that is completely inaccessible to me. I’m the problem with democracy!

If we look at how toxic and racist the local city groups are on Reddit or Facebook, I’m not sure this is a good model. If I’m a black trans woman living in a small town in Mississippi, my local instance might not even be a safe place, for me.

Similarly, I would encourage blind folks to join us at rblind.com rather than a local instance, because a local instance might not take our needs into account: many have captchas, some use inaccessible themes, etc. At rblind.com you can be sure that we won’t deploy an update or configuration change that will break accessibility, because the server admins and moderators are all blind ourselves. But the beauty of federation means that you can talk to everyone else on other instances, so being part of a particular identity group doesn’t limit you to just talking to other members of that group.

If your response to discussion is curses and insults, please also consider shutting down your instance while your at it.

This is exactly my point, though. Yes, all of these changes are easy and possible. But you have to know about them, first. This is not a drop-in “protect everything without side effects” tool like your initial post seems to say. For every app you put behind it, you need to take time to think over exactly what access is required by whom, when, and how. Does it use Oauth, RSS, .well-known, xmlrpc/pingbacks, RDF/sparql endpoints, etc? Do some robots need to be allowed (for federation, discoverability, automated healthchecks, etc)? Are there consumers of API’s provided by the app? Will file downloads occur from downloaders that resume downloads/chunking for multiple connections at once? What is the profile of the humans you expect to be accessing the service: are they using terminal browsers like lynx, do they disable JavaScript and/or cookies for privacy, are they on a VPN, are they using low profile devices like raspberry pi’s or low-end android tablets, etc? What bots are you intending to block and how do they behave: they may just be running headless chrome and pass all your checks, they may be on zombie consumer machines part of a botnet, etc. As with anything in life, there are no magical shortcuts, and no way to say “block all the bad people I don’t like and allow the good people in” without first defining who the good people are and what you don’t like.

In your case, all you’ve effectively done is said “good people run JavaScript and allow cookies, bad people do not”. Without really thinking through the implications of that. I suspect what you really mean is “I don’t need or want anyone but me accessing my personal lemmy instance”. So why not block lemmy-ui from every country but your own, or even restrict it to subnets belonging to the ISPs you use? That would seem to be a lot easier in the case of a personal instance. In the case of a public instance like mine, though, the problem is much harder.

Good to know. But most RSS readers already pretend to be browsers, because otherwise many publications with misconfigured reverse proxies will block them from accessing the RSS feed. cbc.ca is a good example of this. Because deploying a web firewall is neither easy or trivial, unless you know exactly who needs to access what, when, and why. Most people, in my experience, do not.