Communick News

About a week or two ago, I started noticing that I could no longer copy the clean links for search result hits on Google. I thought it was maybe some quirk of a browser I was using, but today when trying to copy a link to a Youtube video, I realized it was actually rolled out globally (it seems).

Basically instead of getting a
https://youtube/. com/watch?v=-ed6UeDp1ek link now through google, (spaced out link to avoid AutoMod) you will get
https://www.google.com/goto?url=CAES<rest-of-encrypted-blob-containing--versionByte-keyID-cipherText>

The article describes the change in technical detail, and mentions a fix, but the author has kept it private for now so Google doesn't patch it up (like they probably will or have for this workaround relying on the "Translate Page" feature with a different Browser Language selection [Twitter Link, Aug 27]).

Why it will probably be patched:

Surprised there's no post about it here already.
Only Hackernews article I could find (4 days ago):
https://news.ycombinator.com/item?id=49506338

Head tracking is a gamechanger for flying or driving games. I've used opentrack successfully with Star Citizen via lutris but have been struggling to get it working for steam games. LookPilot seems to work well and is fairly cheap but isn't FOSS. I know there are loads of other alternatives so I'm wondering what have you found that works well?

cross-posted from: https://piefed.world/c/tech/p/1379783/microsoft-collects-massive-amounts-of-info-from-k-12-students-without-parental-consent-c

I'll just provide my own example: my homelab consists of 6 Kubernetes nodes placed across the country. Some differ by ISP, some are placed in different cities, one is hosted on a cloud provider. Basically it's a very cheap variant of geo-replicating my workloads.

Two of these nodes are visible from the Internet and have a static IP address; one node also has an IPv6 address. Each node hosts an authoritative DNS server (CoreDNS) for my personal domain pootis.network; and the .network TLD has glue records which point to IPs of these two nodes. This is a classic "self-hosted DNS" scenario.

Here's an excerpt from my zonefile so you can understand the setup better:

$ORIGIN pootis.network.
$TTL 300

@       SOA     ns1.pootis.network. admin.pootis.network. (
  2026082001
  1200
  300
  1209600
  300
)

; Nameservers and glue records
@       NS      ns1.pootis.network.
@       NS      ns2.pootis.network.
ns1     A       178.44.116.85
ns2     A       91.219.150.30
ns2     AAAA    2a06:dd00:1:4::4189

This 5-record block (NS/A/AAAA) is mirrored into the .network zone by my domain registrar (plus DS for DNSSEC but that's another thing).

As such, my DNS becomes fully independent - and, in theory, if one of my externally-facing nodes breaks, let's say ns1, then DNS resolvers all over the world (forwarders, recursive, and such) will fall back to ns2, and everything will keep working. Kubernetes will also reorganize the pod placement so all my workloads are available again after a slight downtime.

That would have been great, if it worked as described, but apparently, after one nameserver in my zone fails, then the resolvers... just give up? Let's say ns1 failed but ns2 is working. The parent zone still points to both nameservers. My external resource records (websites and other stuff) at this point would have already been auto-reconfigured by a custom k8s controller to point to the IP addresses of the node that hosts ns2. Simplifying: the entire world basically sees this after ns1 fails and after TTL caches expire:

; all of this has very low TTL, 5 minutes or so

@       NS      ns1.pootis.network. ; from .network 
@       NS      ns2.pootis.network. ; from .network

ns1     A       178.44.116.85 ; broken. Either from .network glue or from my auth DNS
ns2     A       91.219.150.30 ; either from .network glue or from my auth DNS
ns2     AAAA    2a06:dd00:1:4::4189 ; same

; my-website     A       178.44.116.85 ; does not appear because ns1 is broken- my LB already removed it from the set
my-website     A       91.219.150.30 ; fronted by a pair of CNAMEs due to loadbalancing but still
my-website     AAAA    2a06:dd00:1:4::4189 ; same

But even if I query 1.1.1.1 directly for my-website's record, it just doesn't work most of the time because the resolver pins itself to ns1 which is currently failing, or it selects ns1 and does not even care to try ns2.

To be precise: some resolver implementations DO fall back to ns2 as expected, but most of them just pin themselves to ns1 and then outright refuse to resolve the records in my zone.

And there's actually no reasonable way out, as far as I can see:

• moving my DNS infra somewhere else (CloudFlare, for example) is unacceptable since I would like for my homelab to be as independent as practically possible;
• anycasting, or running a fully-fledged BGP AS is also impossible because that costs a lot of money and I'd like for my homelab to fit into a $10/month budget with room to spare;
• "live-patching" the NS and glue records in the parent zone (.network), to keep up with the set of my working nodes, is possible, but very unwieldy and somewhat hard to accomplish.

There's a lot of custom machinery that keeps my workloads running and accessible after a node failure, but all of this becomes completely moot when authoritative DNS is the bottleneck.

Has anyone been running a similar stack and encountered this problem? I'm aware that the answer is usually "host your DNS at CloudFlare" or "use the registrar's DNS infra" but still...

Hey all, I just happened upon a trove (~100gb) of MP3s from when I was a sweaty teenager with a DSL line and a 5-disc ripper. Anyone have recommendations on OSS toolsuites to begin indexing/sorting out the files? Everything apparently got flat dumped from a directory structure to a folder. There’s metadata in about 90% of the content - ~10k songs to sort through shouldn’t be too rough with hashing.

I’d be more than willing to seed once everything is in a happy place, there’s probably a few hundred studio cuts of songs that haven’t seen the light of day yet.

!hannover@piefed.social

News und Diskussionen rund um Hannover.

DayOtter is an open-source, self-hostable scheduling platform (a Calendly alternative) where you own the data. Booking pages, calendar sync (Google/Microsoft/any CalDAV), reminders, teams, payments, and a built-in assistant that can create and edit bookings from plain language or SMS.

v0.4.0 adds full team scheduling (book across chosen members with combined availability, internal team meetings, and an embeddable busy-vs-free team calendar), a smarter assistant (recurring/back-to-back meetings, editing existing bookings), and one-command deploys to Render/DigitalOcean/Fly/Heroku/Railway. The team feature started as a community contribution, which was great to see.

Runs on Docker Compose, free to self-host with every feature included (there's an optional hosted plan, but nothing is held back on self-host). Stack: Next.js, Postgres, Redis/BullMQ, Drizzle.

Release notes: https://github.com/Dayotter/dayotter/releases/tag/v0.4.0

cross-posted from: https://piefed.world/c/politics/p/1379777/americans-have-grown-more-skeptical-that-a-woman-will-be-president-in-their-lifetime

Lot of pressure to make this post today. Hope I can do it.

This post is for casual conversation if you don’t feel like making a post of your own.