us concentration camps Show more
U.S. border authorities hold migrant families in a pen under an El Paso bridge https://www.latimes.com/world/mexico-americas/la-na-asylum-migrants-el-paso-camp-20190329-htmlstory.html
I strongly encourage looking at the pictures; it's important for people to know what this situation looks like.
In the most recent episode of our podcast, @cwebber and @emacsen take a walk down memory lane about 8 bit computers, DOS and Unix command lines and the way that the imagery and mystique of the terminal may be holding us back.
Almost sixteen years ago I met this goofy guy who creeped me out just a bit. Then we became friends. Almost fifteen years ago I had a migraine and my mom told me to have Chris sleep in my dorm room since I was on new meds ... He never left. Ten years ago we got married. We live a magical life together and I love him more every day! Happy anniversary @cwebber
This game engine built on top of Jay McCarthy's excellent DOS (Delimited Operating-system Simulator) package: https://docs.racket-lang.org/dos/
Want a hint on what I made Morgan for our anniversary? I'll give you a hint: it involved me building an ocap game engine layer (no, not spritely, but it is a spritely warmup) named DOS/Hurd https://gitlab.com/dustyweb/dos-hurd
Can you find the present? Bonus points if you can run it!
It's the 10th anniversary of @mlemweb and I's wedding! I made something cool as a present, I will post about it soon.
Horray for @npd in pointing out that something that we should see the "don't scrape me plz" proposal as a robots.txt kind of equivalent https://github.com/w3c/activitypub/issues/339#issuecomment-496353172
That brings a lot of clarity to what it is, how we might expect services to respect *and* ignore it (both happens to robots.txt!), and avoids the unnecessary tracking problem.
The alternate proposal of a sharedInbox type thing where you supply in the header all intended recipients would at least have preserved the actor model and intentional delivery.
Receive-side filtering for federation results in lots of dangerous behaviors... and in that sense, the occasional comment that activitypub is only "advisory" on privacy, I think, stems not just from the E2E stuff but from this last-minute mistake. Explicit/intentional delivery is much safer.
I never should have allowed sharedInbox to be changed to filter-on-server-receive in ActivityPub. Probably the biggest mistake in my programming career. https://github.com/w3c/activitypub/issues/339#issuecomment-496349339
Speaking of Mark S. Miller's writings, here's "The Tragedy of the Common Lisp: Why Large Languages Explode" https://medium.com/@erights/the-tragedy-of-the-common-lisp-why-large-languages-explode-4e83096239b9
I really ought to write a blogpost about the E programming language, and why it's *THE MOST* important programming language you probably haven't studied if you're interested in secure distributed/decentralized systems.
Time and time again, I run into some challenge and it turns out that the answer is already written out somewhere on http://erights.org/ two decades ago.
Writing out (what I hope will be) a comprehensive overview of techniques that ActivityPub node operators can use to prevent spam.
While I've yet to encounter spam on the Fediverse, it seems inevitable that this will happen without intervention.
If we can create some good techniques to address spam before it happens, maybe we can stop spam from ever being a problem on the Fediverse.
Thanks @cwebber for helping co-author, as well as originating many of the ideas! Really excited to work on it!