Thanks for posting this! I have the same router.
Canadian software engineer living in Europe.
Thanks for posting this! I have the same router.
Awesome. Perhaps now there will be some renewed focus on screen reader support?
A lot of places don’t have buses and the roads aren’t safe for kids to cycle anymore. The assumption is that if you’re a parent, you just have to “make time” some-crazy-how.
Honestly, this is so much better than those cases when the codebase is an absolute fucking nightmare are the senior dev doesn’t see it. Instead they gaslight you into thinking that this is actually best practice.
Honestly, after having served on a Very Large Project with Mypy everywhere, I can categorically say that I hate it. Types are great, type checking is great, but applying it to a language designed without types in mind is a recipe for pain.
That’s an interesting thought. There’s a lot of cases you see where people have stripped a comic’s name from the bottom of the image, but that’s not really what this project was designed for. Aletheia will guarantee you that the person/company sharing the media is who they say they are, but critically it won’t prevent infringement.
The example I give in my talk is that InfoWars could take a BBC news story and say “we made this”, but it wouldn’t let them modify that story and claim that “the BBC made this”. The goal is to be able to re-connect what someone is saying with the reputation of the person saying it, with the hope that we can start delegating our trust to individuals and organisations again.
I wrote a version of this in Python a few years ago, but it depended on external tools like ffmpeg to work, limiting its portability. The Python requirement was also a major factor for adoption.
If it were ported to Rust, doing the (de)serialisation internally, I believe that it could have far-reaching implications on how we share and consume news:
https://danielquinn.github.io/aletheia/
If you’re interested, I presented the Python version at PyCon UK a while back.
Not throwing any shade, just some advice for the future: try to always consider the problem in the context of the OSI model. Specifically, “Layer 3” (network) is always a better strategy for routing/blocking than “Layer 5” (application) if you can do it.
Blocking traffic at the application layer means that the traffic has to be routed through (bandwidth consumption) assembled and processed (CPU cost) before a decision can be made. You should always try to limit the stuff that makes it to layer 5 if you’re sure you won’t want it.
The trouble with layer 3 routing of course is that you don’t have application data there. No host name, no HTTP headers, etc., just packets with a few bits of information:
syn
) etc.In your case though, you already knew what you didn’t want: traffic from a particular IP, and you have that at the network layer.
At that point, you know you can block at layer 3, so the next question is how far up the chain can you block it?
Most self-hosters will just have their machines on the open internet, so their personal firewall is all they’ve got to work with. It’s still better than letting the packets all the way through to your application, but you still have to suffer the cost of dropping each packet. Still, it’s good enough™ for most.
In your case though, you had setup the added benefit of Cloudflare standing between you and your server, so you could move that decision making step even further away from you, which is pretty great.
You might want to consider just Dockerising everything. That way, the underlying OS really doesn’t matter to the applications running.
I’ve got a few Raspberry Pi’s running Debian, and on top of that, they’re running a kubernetes cluster with K3s. I host a bunch of different services, all in their own containers (effectively their own OS) and I don’t have to care. If I want to change the underlying OS, the containers don’t know either. It’s pretty great.
What’s a PPA?
Watch the video. The selection of bike infrastructure is done so in a frame of lowest cost with highest benefit, and this is couched in the explanation that there’s no one thing to solve everything but rather a series of things that all must be done.
If you really want an app-like interface, you could make use of Epiphany’s “Install as Web App” feature. Just open Epiphany, go to your Lemmy instance, login, and then select “Install as Web App” from the main menu. Like magic, you get a “Lemmy App” that you can bring up like any other app.
This is my experience in GNOME. Presumably though, it’d work with any desktop environment that respects the XDG standards.
Why didn’t this become a thing? Surely in 2024, we should be able to build packages from source and sign releases with a private key.
What about blog spam though? Surely this would relinquish controls like moderation for your site?
Ooh! Thanks for this! I had no idea it existed.
I recommend writing everything in Bourne shell (/bin/sh
) for a few reasons:
Also two bits of advice.
As someone who has used and loved Docker since 2015, but never used Podman, can you explain the difference and why I might want to make the switch?