argulane

That's some mad dedication to go from kicad schematics to running Quake. Very impressive!

If it's arm based mikrotik then you could run containers with fancier protocol wrappers

I think you can even use standard haproxy acl rules and tables to extract few bytes from the request and route them correctly. No need for Go.

If xfwl4 plans to implement something like sway output max_render_time, then input to pixel output latency should be same or even lower than x11

For me the torrent file currently is coming down at 26MB/s

Using /usr/bin instead of /bin comes down to that is much easier to mount one /usr instead of doing bunch of bind mounts for /bin /sbin /lib /lib32 /lib64,

Also some more background info https://systemd.io/THE_CASE_FOR_THE_USR_MERGE/

Proxmox has had cloud-init support for a while and we have been using it for several years in production.

I have used TimescaleDB in my last work place. We needed a easy way to store and visualize 500hz sensor data for few 10s of devices. We used it and Grafana to build a internal R&D tool and it worked way better than I imagined. Before I left I think the DB was using ~200GB on a compressed btrfs volume in DigitalOcean droplet and still performed fine for interactive Grafana usage.

I own a 2024 Toyota Corolla Hybrid (similar drive train to Prius) and it defrost the window way faster than my previous Volkswagen Passat. Ice and snow handling has been pretty similar here in North Europe compared to my previous car, studded winter tires are the key. Visibility is also quite comprareble.

Unfortunally they didn't exist when we started with kannel

We use it to send OTP messages through few telco providers who don't have HTTP API.

It's cool to see that they are still going. To any one looking to using this for SMPP connections should skip the releases and build it straight from SVN trunk to get the latest bugfixes.

I'm using lieer and mujmap to sync my Gmail and Fastmail accounts to a local notmuch mail storage on top of ZFS pool. That ZFS pool is in turn replicated off site.

I use neomutt to access my archive over SSH. And notmuch is very fast at searching all of my emails.

* https://github.com/gauteh/lieer

* https://github.com/elizagamedev/mujmap

* https://notmuchmail.org/

You can also `git fetch` and `git reset --hard origin/force-pushed-branch` to get your local branch up to speed with remote one assuming you don't have any local changes.

It's bit hidden but once you enable `git rerere`, it will remember your fixed up rebase conflicts.

https://git-scm.com/book/en/v2/Git-Tools-Rerere

It's mostly about performance. If you can store all the required info about the user inside the cookie then you can avoid a DB query roundtrip before sending a response.

Now that your cookie looks like this (probably also base64 encoded):

  {"id": 42, "display_name": "John", "is_admin": false, "session_end_at":1726819411}

You don't have to hit the DB to display "Hi John" to the user and hide the jucy "Admin" panel. Without HMAC, an attacker could flip the "is_admin" boolean in the cookie.

You could also create a cookie that is just random bytes

  F2x8V0hExbWNMhYMCUqtMrdpSNQb9dwiSiUBId6T3jg

and then store it in a DB table with similar info but now you would have to query that table for each request. For small sites it doesn't matter much and if it becomes a problem you can quite easily move that info into a faster key-value store like Redis. And when Redis also becomes too slow you are forced to move to JSON Web Tokens (JWT) witch is just a more standardized base64 encoded json wrapped with HMAC to avoid querying a database for each request.

But even if you are using random bytes as your session identifier, you should still wrap it in a HMAC so that you can drop invalid sessions early. Just for making it harder for someone to DDOS your DB.

That's only a problem when using GitHub. GitLab and Gerrit correctly version such force push PR updates and provide a nice view of what has changed.

Gitea API is pretty close to GitHub

https://docs.gitea.com/

Have you turned on the new render engine in the microsoft terminal settings? It is marked beta but should be much faster.

ATHOM plugs are very nice, you can order one with ESPHome or Tasomata firmware preinstalled and they can ship from Germany https://www.athom.tech/

It does not work because they intentionally disable pipewire support. You can binary patch the slack executable to enable wayland screen sharing https://askubuntu.com/a/1492207

Yeah they removed it sometime ago https://firefox-source-docs.mozilla.org/devtools-user/3d_vie...

Plain urllib3 staring from v2 is also pretty nice to use.

Best bet is probably to find a local hackerspace.

As one data point, Last week I bought a 2024 Toyota Corolla with 29k€. It has midrange options and a premium color finish.

This is the reason why a large part of the Linux kernel is actually developed in GitHub/GitLab. Just search for `github` in the maintainers file to see who many https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

Better tooling in Linux kernel case is moving everything to https://lore.kernel.org/ and https://b4.docs.kernel.org/en/latest/ witch mostly side steps the E-Mail part of the flow.

The amount of people who have the free time to massage `.muttrc` for patch based flow is pretty small. And https://sr.ht/ does not work for the volume that Linux kernel sees.

E-mail based workflow for Linux is starting to break down as the amount of patches is too huge.

* https://lwn.net/Articles/860607/

* https://lwn.net/Articles/952034/

* https://lwn.net/Articles/952146/

* https://lwn.net/Articles/950567/

* https://lwn.net/Articles/959069/

* https://lwn.net/Articles/815332/

grml is great! It has pretty much everything you need. grml config file is also quite readable and you can learn quite a lot from just reading it.

This!

Also doing PR code review is soo much nicer if each commit is logically self contained with a nice commit message.