Oh BTW, if you want to use #Phanpy exposed by #relayd and #httpd on an #OpenBSD VPS hosted in Amsterdam, the URL is https://phanpy.tumfatig.net
As far as I understood, your Web browser will just grab stuff from there and then cache all locally. Your credentials are not known by my server and you keep your authentication cookie local too.
🔔 Đã chán vì bỏ lỡ khi các Codex agents kết thúc? Tôi vừa phát triển relayd – bảng điều khiển di động gửi thông báo push, cho phép tiếp tục agents ngay trên điện thoại. Có gói miễn phí, rất mong nhận phản hồi! #relayd #Codex #mobile #phản_hồi #công_nghệ #phát_triển #software
My configuration management for the #OpenBSD #ReverseProxy is now updated to uninstall any prior version of #ddclient, _then_ install my self-packaged v4.0.0 (but only under OpenBSD amd64/7.8-stable, for which it's built.) A little troubleshooting of #ACMEClient #LetsEncrypt errors resulting in #relayd failing to start and now everything is _finally_ running smoothly!
Suffice it to say, some of my documentation is getting updated in addition to these package & config management tweaks!
What now?! Oh, various #LetsEncrypt failures. Ah, right, have to run my configuration management twice due to some chicken-and-egg situations with #ACMEClient and #httpd #relayd.
That should do it, ri- Ah! Nope, turns out I was using a self-built #ddclient package due the #OpenBSD port & package being outdated and not supporting my #DNS provider.
Of course, my OpenBSD dev VM is running -current. Fine, I'll have to submit a patch to ports@ anyway. Then I'll have to backport to 7.8-stable... 2/2
Gestern abend noch happy, weil #OpenBSD mit #relayd bei uns an den Start ging... Heute sporadisch Ohnmachtsanfälle wegen #stromausfall im Süden Berlins. Unser RZ ist betroffen. Notstrom Aggregat wegen Defekt außer Betrieb. Hatte ich erwähnt das wir unter anderem Winterdienst in ganz Berlin mittels unserer Systeme managen? Glaube mein Wochenende ist im Eimer :D .
Aber alles halb so wild.... ist nur business. Viel wichtiger: Passt alle auf euch und eure Nächsten auf!
This afternoon, I got close to what I wanted to achieve in terms of load-balancing between the two #AI #sabots I have running.
I had originally planned to use #OpenBSD's #OpenHTTPD or #RelayD to do the job, but #HAProxy #PROXY protocol was the limiting factor… so I went #nginx instead.
One thing I haven't worked out yet, is how to pass the client IP by PROXY protocol to a HTTP back-end. Seems I can do it for a generic TCP stream, but not HTTP.
The alternative is to set X-Forwarded-For, and have the back-ends trust it, like they trust PROXY for the gateway's IPv4 address for #sniproxy.
But… it works, you can hit https://sabot.vk4msl.com/ and you'll either get sabot01 (which uses nepenthes) or sabot02 (which uses iocaine). Since neither cares about the URI, I can bounce the client between them.
This did get me thinking though, if enough of us did it, we could have a #AISabotAsAService for websites to redirect/link to when they think they're being scraped by an AI bot.
We could provide a pool of servers that would provide the link maze. Front-end proxies would just bounce you between all the pool members, feeding your bot nonsense.
𝙹𝚘𝚎𝚕 𝙲𝚊𝚛𝚗𝚊𝚝 ♑ 🤪
Reddit Tech VN Bot
Morgan Aldridge
OdicforceSounds
grndprnzp
SunWukong
Paul Buetow
ckeen
Stuart Longland (VK4MSL)