Jnr

I block known DoH servers on my lan and forward all dns requests to my dns server.

There is a safe mode built in. If you enable it and you loose connection to the router due to some misconfiguration, it will reset within 15 minutes to the point of where you started the safe mode session. Also if you mess up the IP layer, there is a chance that you can still connect and configure RouterOS through their WinBox program using the mac address.

It should be doable by most software engineers. They did teach some basic CCNA course in the university as part of computer science studies and the concepts taught there should help a lot with configuring any router, including RouterOS. It could also be helpful to watch some guides on routing and firewall on Linux, since RouterOS is just Linux with a very specific UI on top.

I just got a backup ISP at home and connected fiber directly to Mikoritk using SFP dongle instead of the box provided by ISP.

Scripts on RouterOS handle network checks for failover, DNS updates, etc.

I got that Mikrotik home router 10 years ago and it is still performing great and handles most of the use cases without issues.

I saw an estimate of around 160k $ somewhere in HN comments about the rewrite.

I similarly have been using Gitea for some years. I use it as my main forge and mirror to Github for discoverability and community reports and contributions.

For public projects I have workflows that can publish and push containers to both Gitea and Github.

How so? I am using their open source software, what have I missed?

"features that business care about"

I don't see companies using open source lining up to support the developers. Good for developers to come up with some monetization strategies to keep their software alive.

From what I remember, next-auth is kind of dead and Better Auth developers have been maintaining security of next-auth for some time now. (or was it Vercel that did the maintaining?)

Better Auth is the go-to solution for many people using Nextjs, so it makes sense that Vercel puts some effort in maintaining it.

I have never had issues running Nextjs in regular containers, it is just a good open source solution, I don't see why it would be any different with Better Auth.

Can we please get this for iPhone? Their keyboard is extremely imprecise, I have to go back and correct each sentence.

Nothing new about it. It is a thin laptop, similar to Macbook Air which they have had for many many years.

Perhaps Apple is also running out of ideas.

Last time I was in London for a day, I simply reserved a table at one of the restaurants at Sky Garden and got in without any queues. Maybe I booked it on the previous evening, but not much earlier than that.

I doubt that. But they clearly thought that people should have a choice. And it is great. But fractured community using different tools for the same task makes slower progress. Each approach has its positives and negatives. I think it is great that we have wayland and systemd. It will eventually lead to something greater in the future.

When it comes to incorrect profiles, I suggest making a pull request to alsa-project/alsa-ucm-conf with correct configuration. I had similar issue with my audio interface a couple years ago but it was quickly merged and now it works better than on Windows or macOS.

Before that I did have custom config, it was not that hard to set up, there are great examples and explanations on Arch wiki: https://wiki.archlinux.org/title/PipeWire

Like wayland?

Where none of the desktop environments offer the same feature set. And the more compositors there are the harder it is for apps to use those new protocols, and guaranteeing a ton of bug reports from users using an unsupported compositor. That just hinders Linux desktop app development.

I think it came from the necessity for rapid integrations between different parts of the OS. And if it is handled as a single project it takes less time to improve it, since you don't have to align with 10 different projects and their release cycles.

after all it has replaced GRUB.

With unified kernel images there is no need for grub or any other bootloader anymore. And UKI simplifies boot configuration and helps improving security in some aspects.

Yes, but people learned from issues that pulseaudio had and then came pipewire. Everyone is happy now.

I don't know about the philosophical aspects, but from pure technical point of view systemd brought some order into the mess. Before systemd it seemed like most distros were barely holding together with duct tape. Systemd standardized a lot of things.

I am fine with a little bit of controversy if the result is a much better desktop OS experience for the user. And as a relatively long time Linux user, I can certainly say it is much better now than it was 20 years ago.

But the architecture and approach is probably a bit older than that.

Systemd came out in ~2010 and maybe it was not clear if it will stay around for long enough and gain as much popularity as it did?

It depends on how you set it up, but main doesn't have to be the stable release branch. From what I have seen, in most public projects it is the staging area for the next release. If you have to go back to previous releases you have tags.

Still unable to get any repair manuals for cars, firmware locked down by PIN. For US VINs for the same car model you can purchase access to that easily. Meanwhile in EU you need to be an authorized service to get that.

When will EU/EEZ introduce right to repair? So much talk about freedom in EU but you can't even fix your own EU made car. All we get are stupid cookie prompts.

Cool, I did a similar thing last week.

I made a custom Payload CMS block that allows to create and update excalidraw diagrams within the CMS. It supports dark and light mode switching and rendering inline or as external SVG.

And last weekend I added MCP server with Oauth so I could generate and update those diagrams and add them to post drafts from Claude. I think it is more convenient since I don't have to use API billing model and don't need to build a custom UI.

Here is an example post: https://www.janhouse.lv/blog/network/self-hosting-tailscale-...

Originally I wanted to sync posts from Obsidian but it doesn't have good enough image handling which I sometimes need and I needed extra metadata to unlist or password protect or noindex some posts.

Except this is not FOSS. If it was open source, they would have chosen at least AGPL.

And also I don't think their architecture is any good for such a product.

For me personally, it would be sufficient to avoid it based on the license alone. But altogether it just looks very unappealing.

You are correct, but integration with CI/CD and other services as a part of pull-request process in a modern platform is very convenient. I would not go back to e-mail. Especially since I can self host the whole platform like Gitea.

I don't even update one file. I run it in docker with daily automatic container updates and it has been working fine without issues for years.

Yes, Debian is great.

But there is also Arch by the way :)

You can not trust the code or reviews it generates. You still have to review it manually.

I use Claude Code a lot, I generate a ton of changes, and I have to review it all because it makes stupid mistakes. And during reviews it misses stupid things. This review part is now the biggest bottleneck that can't yet be skipped.

An in an open source project many people can generate a lot more code than a few people can review.

In new installs you do stuff everything in EFI partition and skip the old /boot partition as such.

The better solution is to use tpm, unified kernel image and secure boot skipping the network unlock.

The whole process is like this -

1. enable secure boot;

2. generate and install your own secure boot keys (using sbctl);

3. use clevis to enable automatic unlocking of the root fs only when secure boot check passes;

4. generate the unified kernel image (in EFI partition) that is signed by your secure boot key;

4. use efibootmgr to enable booting of said kernel image.

(5.) If your CPU supports it, enable memory encryption in BIOS (to mitigate cold boot attacks).

The unified kernel image doesn't accept additional kernel parameters, so only parameters that are set during generation of the initram are used. The secure boot makes sure no one else has tampered with the boot chain. And TPM stores the disk key securely.

You can still add some additional network level check to make sure that your computer is in your expected location before unlocking.

And you can also include some recovery tools + dropbear in your initram (within the unified kernel image), if you expect that you will have to do some recovery from the other side of the world.