kyrofa

To be clear, I'm not trying to argue or disagree with you. I agree that PPAs are a fine option. I'm not trying to disparage them, I'm trying to explain the reasoning behind my suggestion: PPAs enforce a number of requirements that exist for a reason, but that can be a challenge to meet depending on the project. The biggest example is that of source packages. I don't mean "your source needs to be open" (which of course this project is), but rather "your software needs to be built on Launchpad infrastructure." If you take a look at the existing CI the maintainer has in place to build the binary deb, you'll see what I mean: https://github.com/sinelaw/fresh/blob/master/.github/workflo... . The maintainer already has this, and it would need to be completely re-done to make it work in Launchpad, and the amount of work might be quite significant. A standalone Debian repo can just have binary debs, i.e. the work that has already been done can continue being used.

Thus my recommendation for aptly/reprepro: it's a more natural extension of what the project already has in place rather than a "you should do this instead."

Yeah, the one thing you're missing is getting into the users' `apt update`/`apt upgrade` flow, right? This will get you there without needing to change the Debian package you already create (although you can ship different ones this way if e.g. older Ubuntu/Debian distros require it and you want to support them).

Of course. Needing to ship a source package (as PPAs require) may actually complicate things, though.

Oof, yeah that's painful. I'm impressed you've gone to these lengths, most maintainers don't do that. They generally rely on the folks who want to use the software packaging it for their distros. Obviously there's a bit of a chicken and egg problem there, though, if you care about getting your software in front of users.

For the Debian situation specifically:

> It would've been nice if there was a quick serverless solution where you could just say a URL to look for newer versions of a single package, and both apt and dnf would remember that and update a package.

Have you considered just hosting your own Debian repo? It's basically what you're looking for here. You don't need more infrastructure, either, you can host them straight in github pages with aptly or reprepro or something, and drop new releases in there from CI.

My wife is a professional photographer and Darktable is a critical part of her editing workflow. It's a truly outstanding piece of software.

I don't even have a smart phone, I assume there is some sort of fallback behavior?

Yeah that's all it says ANYWHERE right now (https://status.canonical.com/, X, etc.), but so much of their infrastructure is down. Hoping for an update before too long.

It appears that 313 Team is claiming credit for this.

https://www.pcmag.com/news/pro-iran-hackers-hit-ubuntus-cano...

https://www.reddit.com/r/cybersecurity/comments/1t0jf3p/313_...

> TL;DR my motivation and experience for moving my blog from Cloudflare to bunny.net

In my experience the TLDR generally gives the motivation/experience in brief. This feels more like a subtitle.

Heh, server time as opposed to client time at least.

> The cards observe it is Friday. They have not forgotten the Great Friday Deploy of 2021. They have not forgiven it either.

It's... it's Thursday.

That's not actually true: cell phone rx/tx power is quite low. We can get away with that because all they need to do is get to the nearest tower, which has a ton of power, sensitive antennas, and is very tall. Amateur radios have far more power available to them, but any "p2p" (i.e. simplex in amateur radio) runs into normal RF issues, like obstacles and interference. If you used the existing radios in cell phones to communicate directly with other cell phones, you wouldn't get very far. Even amateur radios, with all their power, use repeaters to the same effect as cell towers.

Thanks Ben, I wasn't aware of that.

There are a number of companies/products that operate under this principle (mullvad and signal come to mind). Are you saying all of those are futile and misleading? Or are you saying that you expect they all have significant money and legal teams to defend against a crooked cop's thirst for vengeance for not responding the way they wanted during an investigation?

Why? That's kind of the whole point of this: they can cooperate entirely and give them everything they have. You think they'll get into legal trouble because they aren't gathering data?

Self-hosted gitlab here. Love it, and gitlab CI is excellent as well. Almost all product development revolves around some crappy AI integration that we don't use, and it worries me to see so much focus there instead of the core product, but the core product is still excellent.

> [It] runs a heavily stripped-down version of Linux that lacks systemd and apt. And these are just a few of the issues.

You mean it's not Debian-based? How is this an issue?

Loved this as a kid. But as a parent, even putting it in the garage is just too much noise for my household, haha!

Pretty sure Immich is on github, so I assume they have a workflow for it, but in case you're interested in this concept in general, gitlab has first-class support for this which I've been using for years: https://docs.gitlab.com/ci/review_apps/ . Very cool and handy stuff.

Wow, my worlds are colliding right now-- although seeing Benn on HN in retrospect shouldn't be that surprising. Go check out his music, The Flashbulb, he's one of my favorite artists.

Heh, I suppose you've heard of one now. Fair enough, I could be in the minority here.

> When a drive fails, one of the key factors in data security is how fast an array can be rebuilt into a healthy status. Of course, Amazon is just one vendor, but they have the distribution to do same-day and early morning overnight parts to a large portion of the US. Even overnighting a drive that arrives by noon from another vendor would be slower to arrive than two of the four other options at Amazon.

In a way this is a valid point, but it also feels a bit silly. Do people really make use of devices like this and then try to overnight a drive when something fails? You're building an array-- you're designing for failure-- but then you don't plan on it? You should have spare drives on hand. Replenishing those spares is rarely an emergency situation.

Yes, I didn't mean to imply that Linux was doing anything wrong, just that some hardware seems to work better with other approaches, for the reasons you state.

The Linux kernel supports rebooting using a number of different strategies[1]. Some PCs need a different one than the default in order to make sure everything is properly reset.

[1]: https://github.com/torvalds/linux/blob/9b2ffa6148b1e4468d08f...

> First if all, it wants to do everything and does none well (or better than specialized apps)

Yep. And any extra apps beyond the default just make upgrades go sideways. I've given up on it. Using syncthing instead (just for file syncing) and haven't looked back. It's not my favorite either, but just because it's a pain to configure. Once configured, it's been rock solid.

Related: https://simonwillison.net/2024/Sep/15/how-to-succeed-in-mrbe...

Haha, you just made my day. How have I not seen this?! Thank you.

v1.0 before 100 commits, wow.

> the likelihood that they'll even receive the complaint is next to nothing.

They don't need you to complain: they got an automated notification as soon as you saw the error page.

First of all, the 500 error page is often included as part of the toolkit being used to make the site, as a generic response to most exceptions. The developer isn't generally going to explain every possible exception in detail to the end user; the most important thing is that they automatically get logs or error notifications with the ACTUAL exception, and can take action to fix it.