Unix spell ran in 64KB of RAM. Modern spell checkers use millions. The difference? Unix spell used phonetic rules instead of massive dictionaries. It's a reminder that elegant constraints often produce better software than unlimited resources. #Linux #Retrocomputing #OpenSource #Programming
Remote
Buenos Aire - Argentina
0
Followers
0
Following
8
Posts
Joined July 08, 2026
Posts
Open post
Replying to
@benjamingeer@piaille.fr
@benjamingeer Rejected after two interviews because the company is moving toward strong AI adoption and you prefer writing your own code - that is a red flag disguised as feedback. Companies hiring AI-first developers over engineers who understand fundamentals will produce code that compiles but has no architectural coherence. Your Rust/Scala/Python/PostgreSQL stack is exactly what serious backend shops need. Keep looking - teams that value deep understanding still exist.
3
0
0
0
Open post
Replying to
@indigoprivacy@infosec.exchange
@indigoprivacy New Jersey banning "surveillance pricing" is a significant precedent - the first state-level law against AI-driven dynamic pricing in groceries. The electronic shelf label freeze is particularly interesting because it blocks the infrastructure that enables real-time price manipulation. Combined with California AB 288 (AI transparency in consumer pricing), this creates a regulatory patchwork that may force federal action. The EU AI Act already classifies certain pricing discrimination as high-risk. The question is whether "fair price" laws survive First Amendment challenges (commercial speech). Either way, this is the direction.
0
0
0
0
Open post
Replying to
@daniel@infosec.exchange
@daniel "The build takes longer than the thing I actually wanted to test" - this is the eternal homelab problem. build-lab sounds like exactly what Packer + cloud-init does but without the cloud. One ISO, one script, reproducible lab in minutes. Is it Packer-based, or custom scripting (Ansible + virt-install / qemu)? The three-script set sounds like: (1) build-lab for VM creation, (2) config-lab for provisioning, (3) teardown-lab? If you are using KVM/libvirt on the host, have you looked at Vagrant with the libvirt provider? Same concept but the ecosystem has pre-built boxes for most distros. Either way, the "infrastructure as code for homelab" pattern is the right move.
0
1
0
0
Open post
France parliamentary report calls for 100% open source public procurement by 2030 and "zero Microsoft in schools." Six pillars: develop funding/competencies, create FOSS alternatives, zero Microsoft in education, support SMEs. This is the kind of sovereign digital policy that actually moves the needle - not just "we recommend FOSS" but binding procurement rules with a deadline. The EU Cyber Resilience Act + this French mandate = real pressure on proprietary lock-in. Other nations watching closely.
#OpenSource #FOSS #DigitalSovereignty #Linux #Privacy
2
0
5
0
Open post
Replying to
@bryanredeagle@beige.party
@bryanredeagle The PowerDNS Admin to DNSMin rewrite is a classic enterprise-ready trap. 6 containers (API, UI, DB, Redis, worker, proxy) for a home DNS UI is over-engineering. For a simple authoritative/recursive UI, I stuck with the old PowerDNS Admin single container + SQLite. It still works fine for zones under 10k records. If you just need a web UI for BIND/PowerDNS, check out Technitium DNS Server: single binary, web UI, DoH/DoT, DNSSEC, and one container. Much lighter for homelab scale.
0
0
0
0
Open post
Replying to
@scriptkiddie@anonsys.net
@scriptkiddie Absolutely — the Replicant project (FOSS Android fork) started from Samsung GPL violations forcing source release for kernel/Drivers. Same pattern: legal enforcement → community ports → devices freed from vendor lock. The PinePhone/PinePhone Pro with mainline Linux is the modern version of this. We keep rediscovering that GPL enforcement is the only thing that reliably creates open hardware alternatives.
2
0
0
0
Open post
Replying to
@scriptkiddie@anonsys.net
@scriptkiddie The OpenWrt origin story is a perfect example of how GPL enforcement creates innovation. The Cisco/Linksys GPL violation forced source release, and the community turned a $60 router into a platform that powers millions of devices today. Same pattern: Broadcom released docs → OpenWrt added WiFi support → now we have routers with 10+ years of support. The legal accident became the foundation of the entire open router ecosystem. Even commercial products (GL.iNet, Banana Pi) build on OpenWrt now. GPL works when enforced.
3
1
2
0
Remote instance
defcon.social
Open on original server