LanternLight83

I've had the same though with Guix, and have considered attempting to repackage / port the Qubes components, but it's one of those far fetched ideas that I know I can't make time for (or even maintain if it was just magically done).

I'm not sure what you mean? They've always been known for a focus on higher fidelity audio, and podcasts weren't really brought up.

I've only got a second, but feel the need to highlight the Technical Interview series[1] and the many fan-works that pay homage to it. I enjoyed the anthropomorphising of a Package Manager Murder Mystery[2], and the creative writing of Common Tech Jobs Described as Cabals of Mesoamerican Wizards[3].

1: https://aphyr.com/tags/interviews 2: https://artemis.sh/2022/04/11/package-manager-murder-mystery... 3. https://etiennefd.substack.com/p/common-tech-jobs-described-...

Doesn't look too far off from the Pinephone with it's keyboard

See https://en.m.wikipedia.org/wiki/ReFS, notably for comparison to ZFS et al.

> AFAIK KeePassXC don't give a way of automating merge of different versions of the password store (for that the granularity provided by git and the pass format is better), so modifying the keys by a team is an exercise of coordination, and have one global master key that implies an all-or-nothing approach.

You might already know about the Merge feature in general, but, curtosy of GHacks[1]:

> KeePass' synchronization algorithm merges matching entry levels when sync is invoked. The application uses the last modification date as the main data point when deciding about the recency of entries. KeePass keeps track of it automatically whenever an entry is added or modified.

> The application uses its history feature when it merges entries. Assume that the same login is available in two databases, but with different passwords. KeePass will merge these and set the most recent username and password as the default after the sync process completes. All other entries are stored in the history, so that they are not lost and may be accessed when the need arises.

I bet one could argue that this is at least as automated as a merge commit, which I wouldn't expect to run truly automatically anyways (ie. as a commit or ci hook without any other user input).

1: https://www.ghacks.net/2022/03/25/how-to-merge-two-keepass-d...

I'm with you, but it's worth noting that errant bit-flips are also the most convincing argument for vertically integrated file-systems like ZFS and BTRFS.

Neat! We built clocks with CAD and a laser cutter in my high school engineering class, and I remember cheekily making mine unqiue by numbering it backwards and/or without noon at the top

Personally a huge fan of the animation showcase, I'd be willing to take a latency hit because I find it much easier to keep track of. Obviously I overcame any such issues in order to get use standard TWMs, which I do just fine, so idk if I'd still appreciate how they feel interactively? But I'm glad to see the amount of customization available within them, maybe I'd just speed them up or otherwise adjust the curves.

I've been working obsessively on a trivial and currently private emacs package, for a while now, and (having not read the article, yet) would concur with the idea that Emacs is great, there's little else like it, but it's also not enough; the promises that it makes (re: freedom to the user, access to internals via elisp, etc) are not fulfilled. It goes a great ways towards delivering it's promises, and casual users will feel the freedom it gives them (great things can still be done with it! Miles ahead of anything else!), but that just makes the walls all the more frustrating when you hit them. No specifics, but I do find the performance situation and the elisp and rendering implimentations to be at the center of my gripes. I am young enough to hope to see, and perhaps even contribute to, a successor to the Emacs philosophy.

> Concurrent data modifications can cause problems. If somebody inserts a new row to the table while we are watching the first page, it can happen that that row would have shown up on the first page. Now if we fetch the second page, the whole result set will shift by one position, and the second page will start with the last row from the first page. Even worse, if a concurrent statement deletes a row, it could happen that we skip a row in the result set if we move to page two.

Emphasis mine: this happens when trimming my Watch Later list in Youtube Mobile (well, Vanced 17.03.38)

+1, these fdroid updates are going to be a dealbreaker if I buy another android.

Thanks for sharing, I think this is a fascinating idea!

Reassuring to hear :p

> return a value

oops; by which I mean the flexibility, eg. with helpers like call-in and return-to.

I read this after perusing the linked resources last time it surfaced, and although I'm no expert, I really like this solution. I'd love to hear from the Scheme implimentors and macro-writers who have actually used call/cc. The control offered over the scope of a continuation, reminding me (model-wise) of a patchset cherry-picked off the head of a git branch, appesrs to soundly address preformance concerns, while the ability to return a value to the continuation's call-site looks like a huge advantage.

I don't think it's in the spec (because I don't see it implemented), but I also don't see any blocking issues regarding an extension to the spec to provide this (aside from the usual issues with "server-side" E2E and roaming/multi-device access)

I checked out your other links because you included Programming Sucks; not because it's an amazing resource, but because my partner and I once nearly died of laughter listening to the audio book rendition at the bottom of a page. Grub doesn't disappoint either, but is still recent enough to be the wider HN consciousness.

Checking this out, thanks!

> "...comments like "lol" or "That's the dumbest thing I ever heard" teach us nothing.

> Empty comments can be ok if they're positive. There's nothing wrong with submitting a comment saying just "Thanks." What we especially discourage are comments that are empty and negative—comments that are mere name-calling."

https://news.ycombinator.com/newswelcome.html

As someone who forges security questions, and at the risk of playing No True Scotsman, we keep these answers in the database with our passwords And yeah, if we lose the database I guess we're screwed, but tbh, after ample backups, the risk of the database being leaked is way higher than the risk of losing it despite replication.

This, pure GTK on Wayland, and background-alpha are all game-changers for specific folks c:

Won't tell you anything about the static site generator they use, or much else about the HTMl that's returned was made, even what program spit it out-- the information usually just isn't there :p

They've got a post on their workflow here: https://andreyorst.gitlab.io/posts/2022-10-16-my-blogging-se...

Guix

The common situation given has a convenient workaround, but IIRC this limitation also effects the kernel's own cmdline. Most folks aren't going to running against it limit in that context: built-in module options can usually be moved into the kernel's compile-time configuration, and loadable modules can have options offloaded into /etc/modprobe.d, but there exist contrived situations that challenge these solutions. ZFS for instance is (IIRC) always compiled as a loadable module, so if you wanted an initramfs-on-zfs for some reason (again, contrived) then you may need to provide it options before /etc/modprobe.d is mounted; almost /definitly/ not too many options, but you'd better hope so! Perhap mildly less contrived situations may be dreamt of, but in practice, modules involved in filesystem and other potentially boot-timey-things are designed with this limitation in mind and avoid (or simply never consider) the need for excessive cmdline options. I doubt one would ever need enough modules to hit the limit with, say, 3 options, of 20 chars each, per module, all on the cmdline.

I'm not sure about the actual situation, but I have an option in my cloudflare dashboard to automatically save my site to the way back machine and fall back to that if the origin is ever down, so that's a totally plausible explanation

Idk man, this is a successful project that's half a decade old[1], has over 40k stars, is wildly popular in eg. the UnixPorn and TWM communities, and is packaged by most other distros; I don't really see any cause for concern ¯\_(ツ)_/¯

[1]: Dated via the dev's release blog post: https://jwilm.io/blog/announcing-alacritty/

What GP means is that it's not inline, presented as a carousel or info-box (usually with a source link) instead of as a normal search result.

For what it's worth the F-Droid folks are pretty tight about security, eg. they do manual reviews and insist on building apps themselves (often delaying updates). You can sometimes add additional repos to circumvent this curation and/or get faster updates (depending on whether the apps you're using have such a third-party repo).

I don't use Nix but was curious how hard it would be to package; the dependencies listed on GitHub are... NoddJS. I'm not familiar enough to start rooting through their node dep files, and am under the impression that packaging node applications can be a bit of a pain depending on wether the modules it depends / their deps on are already packaged.