![](https://lemmy.ca/pictrs/image/f2e15bf5-d328-4049-bed2-ae7cd4ae92c8.jpeg)
![](https://startrek.website/pictrs/image/ccbc1d32-aa21-4d26-bb28-42e63bd83083.png)
That was my takeaway as well. I just wish I had data for the other seasons. It’d be interesting to see how that might change the percentages as they are.
As for GEOGIOU
, I’m reasonably sure that this refers to both versions of her.
Canadian software engineer living in Europe.
That was my takeaway as well. I just wish I had data for the other seasons. It’d be interesting to see how that might change the percentages as they are.
As for GEOGIOU
, I’m reasonably sure that this refers to both versions of her.
Honestly, it’s 'cause I forgot to include it! I’ll see if I can add it tonight. Check back in 24hrs :-)
I like it, and I’d bet dollars to doughnuts that you’re talking about Discovery. I’ve said in the past that the show should be called “Star Trek: Michael Burnham” as it would at least be more honest.
To be fair, I think every series has a lot of episodes that would fail this test, some of which were excellent, like DS9’s “In the Pale Moonlight”, and “Far Beyond the Stars” or TNG’s “The Inner Light”, but if used to assess a series, I think this could be a good metric.
Thanks for posting this! I have the same router.
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 ;-)
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.
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?
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.
Maybe I’m misunderstanding vulture. My impression was that it’s meant to be run in your CI, which would mean it’s only privy to code executed by your tests. If it actually attached to production sessions, then yeah that’s pretty handy.
If you ensure 100% test coverage, you don’t need this ;-)
deleted by creator