Relevant.

Awesome. Perhaps now there will be some renewed focus on screen reader support?

Ah yeah, I remember a moment like that in DS9, where Sisko is lamenting the crew’s interest in a holosuite program set in the 50s because of how “our people” were treated back then. It always felt out of place for me, though DS9 is still my favourite Star Trek.

Can you give some examples of this? Admittedly I didn’t much care for Discovery and didn’t pay a lot of attention through it as a result, but I’m not picking up what you’re laying down ;-)

It’s a different kind of world. You need a different kind of software.

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.

We don’t use X, and we don’t use Facebook, and I’m not even close to feeling sorry."

Love it. Subscribed!

You may want to promote this in /c/solarpunk.

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.

This might be fun to write actually. Basically you need a central server you connect to via a websocket that would plot points out on a map (maybe with leaflet?) on receipt of notifications pushed via said socket.

The trouble of course is that with a central server, you tend to incur costs, so you’d have to pay, unless some sort of P2P mesh could be established between participating parties. That’d be a fun problem to solve for sure.

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.

Very cool trick. I’ve never been comfortable with how Python package installation is effectively arbitrary code execution. It’s also a nice reminder that installing packages into a Docker environment is generally safer than going bare back metal.

Very slick. It looks like a thin wrapper around some pretty powerful tools, and I’m impressed that they’re still useful on such a low-power device.

I wrote an assistant a while back before Whisper was a thing, but now that I see what you’ve done, I’m going to have to go back and refactor.

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.

Voyager: One Small Step

It’s one of my top ten favourites, but it’s also a very typical “one off” story.

They also support genocide.

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:

• source IP and port
• destination IP and port
• A few other firewall-specific bits of information like whether this packet is part of an established connection (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.

I rather like the FSFe for general Free software stuff, but you may find nicer-looking stuff if you visit merch store for specific projects, like GNOME, KDE, etc.

Revealjs is a pretty great replacement for PowerPoint, but it does require rudimentary HTML skills.