she/they ⚧︎. https://dblsaiko.net/
Probably not, the costs were essentially just sticking ethernet ports on the walls next to the phone ports and rewiring the existing wires to those ports. And back when this was done (whenever we got DSL, around 2005 maybe?) fiber tech was probably prohibitively expensive. I haven’t looked up how much fiber modems cost but it would probably be more expensive even today.
The phone lines repurposed as ethernet in my parents’ house also only do 100 Mb/s. I concur, so painful. I want to put a storage server there but no matter where it’s limited by awful speeds. It also means getting faster internet would be useless because it would be limited by these wires.
Yeah! To add to this:
Hm, okay, that does sound like the real client IP will get lost and every connection will appear to come from the proxy then. It would be good if that were passed somehow. My current setup adds the X-Forwarded-For header for example.
Oh interesting, I’ll have to look into that. Is this with that “proxy protocol” I’ve seen mentioned? If not, does this preserve it pass through the client socket address?
Tbf, technically data is still decrypted at the reverse proxy and then re-encrypted. So if someone manages to reconfigure the proxy or read its memory somehow they could read traffic in plain text.
However then since they have to control the VPS, they could also get a new cert for that domain (at least the way I’ve configured it) even if it was passed as is to the real host via a tunnel and read the plaintext data that way, so I don’t think a tunnel protects against anything.
If someone manages to get root (!) access on this VPS it’s over either way.
Yes, you can just use a reverse proxy for IPv4 only and point it to the IPv6 upstream. That is what I do, with a separate DNS record which then combines the two. See the DNS records for id.knifepoint.net (CNAME), http.vineta.knifepoint.net (AAAA, A) and vineta.knifepoint.net (AAAA).
The reverse proxy config and certificate management is set up with NixOS, if it helps: https://git.dblsaiko.net/systems/tree/nixos/defaults/v4proxy.nix https://git.dblsaiko.net/systems/tree/nixos/modules/sys2x/v4proxy.nix
The experimental status is more about that not everything is implemented yet (not that everything can be implemented, for example due to HTML not being oriented around having multiple pages in a document), so you have to write a bit of raw HTML sometimes. This is an example of how raw HTML looks, it’s the shell for my webpage.
There’s experimental HTML support. I’m using Typst as a static site builder for my website.
Two different rDNS names, for stuff that uses it. For example if you want to run mail and an IRC bouncer under different domain names.
Lists with 100k items? Impressive. I can see how with a document like that it will run out of memory. Is it a stack overflow? You could try increasing the stack size in that case.
As a Typst enjoyer I have to say this isn’t it imo from a quick look at the readme. Typst’s mix of markup and code modes is excellently designed and a high bar for anything to beat, and this looks like it doesn’t come remotely close. (I do have to say, I also heavily dislike Markdown in general)
Yeah, that’s fair. When verified beforehand, and what it discovered is an actual issue, why not. It does overwhelmingly attract people who have no idea what they’re doing and then submit bogus reports because it looks good to them though.
Daniel Stenberg has banned AI-edited bug reports from cURL because they were exclusively nonsense and just wasted their time. Just because it gets a hit once doesn’t mean it’s good at this either.
Tbh I haven’t had too many problems with Postfix – however it is certainly a footgun and it would be nice to have fewer parts to connect together, and better defaults. I might try it out, it looks interesting.
From its web page it sounds like it is both a MTA and MDA, has a built-in spam filter, plus has calendar, contacts and file storage. Do you know how it compares to my current setup of Postfix, Dovecot, and rspamd (and Nextcloud for the others)?
I’m partially very sad but also kinda glad that I never got to use 10.4 or other previous versions (first one I used was Ventura). The more I hear about it, the more it sounds like I would have absolutely loved it and would be incredibly mad right now at the changes they made since.
I might give you Windows 7 on functionality, it has been forever since I used either. But definitely not design. 2000 has a UI that is consistent throughout, clear, and professional. It’s a masterclass in UI usability engineering. Plus it’s also heavily customizable if you want to do so. A lot of that was lost with Vista and some with XP.
AppImages are precompiled archives with extra steps. Meh. No, some of my problems with Flatpak are:
Some of that (and why it’s necessary in the first place) is due to Linux’s incredible fragmentation and lack of an extensive backwards-compatible system API (such as macOS’s Cocoa), which causes a lot of other problems everywhere – but a lot of it is also self-inflicted. In fact, the massive focus on Flatpak and looking like that is the direction the Linux desktop is going was partly what drove me to try out a Mac.
Mirror’s Edge Catalyst-ass computer (agree, it looks great!)