SteveTech @ SteveTech @programming.dev

Posts

1

Comments

360

Joined

2 yr. ago

Cert pinning is pretty uncommon in the self hosting community though, especially when both Cloudflare and Let's Encrypt have a 90 day validity period and often renews after 60 days.

Uhh, this might be true for WebRTC, except not much uses WebRTC other than for realtime streaming/calling. Jellyfin for example is just an mp4 stream over http; and http(s) will only use the IP in the DNS record. I'd like to see a packet capture if you are certain something is switching IP.

I’m pretty sure QWERTY telegraph keyboards post-date typewriters.

Yeah they do! Actually a Japanese research paper (and this video) also theorises that they also grouped similar sounding letters in American Morse Code together (e.g. Z ∙ ∙ ∙  ∙ & SE ∙ ∙ ∙   ∙, or C ∙ ∙  ∙ & S ∙ ∙ ∙)

Yeah, YunoHost explains why http://localhost:8536/ wouldn't be working. If cloudflared and Lemmy are in separate containers you have to put an actual IP in, since localhost points to the container itself.

How are you accessing it without Cloudflare? How do you know that Lemmy is actually listening?

What's the URL you using to access it without Cloudflare?

Edit: Also that curl tells me it's not listening on that IP/port.

Can you access it without Cloudflare?

Does curl http://localhost:8536/ work?

You are using cloudflared right? Because normal (non-cloudflared) Cloudflare doesn't support port 8536.

With dynamic DNS? Yeah it always has, as long as you can host a http server.

With a dynamic IP? It should do, the certs are only valid for 6 days for that reason.

I know this seems pretty much solved, but I just wanted to point out:

Frigate doesn't need a TPU, OpenVINO is quite performant even on decade old Haswells, or if you've got a GTX 750 or higher you might be able to use that as well.

Oh okay, I had assumed compiling would be a bit more I/O bound, while gaming would be a bit more CPU bound, but I guess you're right about the benchmarks!

If it helps, I wrote a KDE widget to switch between the modes: https://github.com/Steve-Tech/KDE-AMD-X3D-Selector

My understanding is amd_x3d_mode basically prioritises what cores the scheduler will assign tasks to. I usually keep it on cache since I do a lot of code compilation, but I will usually switch it to frequency for gaming and stuff.

You can host a page with an iframe, but you can't directly change the DNS record to point to something that isn't GitHub.

I think they were trying to say that the cage in front with the AP behind, acts as a directional antenna. Similar to how Yagi antennas have metal elements that aren't connected in front of the actual antenna.

But I don't know enough antenna theory to know if that's correct.

It's not strictly Linux anymore, but I wrote a library (or userspace driver?) in Python that interacts with a ChromeOS Embedded Controller found in Framework Laptops and Chromebooks. The driver part of it interacts with the EC directly over the IO ports, which was originally written for Linux but later ported to FreeBSD and Windows since IO ports aren't at all OS specific. It can also talk to the cros_ec_dev driver on Linux if it's loaded.

https://github.com/Steve-Tech/CrOS_EC_Python

I wrote a GUI utility for Framework Laptops too, which also serves as the example for CrOS_EC_Python: https://github.com/Steve-Tech/YAFI

help now actually opens the help utility on Python 3.13!

Thanks TIL! Although I prefer this diagram that has all the wifi channels on it, instead of just the 3 common ones.

Source

Perhaps there was an easier lighter-weight way of doing this?

Yeah, SSH tunneling. What I would do (and have done in the past) is something like:

    
ssh -L 8080:192.168.0.1:80 myserver


  

That will forward port 8080 on your host to port 80 on 192.168.0.1, so you can access your router's web UI with http://localhost:8080/ in your own web browser.

You can also setup full tunneling with SSH, but that requires messing around with SOCKS and I usually can't be bothered.

My understanding is previously the kernel would crash on systems with more RAM than the address space, so there's now a patch to ignore the anything above the max address supported (e.g. 32bit without PAE, 36bit with PAE). More RAM was never supported, so I think the author of the article has misunderstood or oversimplified what's been done.

You can always install activate-linux, and it even works on Windows.

Epic!

You should be able to add options it87 force_id=0x8688 ignore_resource_conflict=1 to /etc/modprobe.d/it87.conf (or whatever filename) and it87 to /etc/modules. To get it to run at startup.