@nolan I think this is an important point. People may not be aware how often their TVs and speakers are sending data to companies.

My top blocked domain on my pi-hole right now is to Sonos. How would I know that if I wasn't a) savvy enough to set up a pi-hole and b) privacy conscious enough to bother.

Whereas anyone running an ad blocker in their browser can see how much stuff is getting blocked.

i have been forcibly reminded the voyager plates basically constitute a mixtape, unsolicited nudes, and directions to where we live

I'm curious. Does anyone else read scientific papers for pleasure? (Boosts wanted.)

love how we're inching closer and closer to antivax psychos being bio terrorists

TIL the Windows XP wallpaper is literally on fire and it's a perfect metaphor for the tech industry right now and also very disconcerting

You couldn't make Toy Story in the future, because nobody will remember playing with generic astronaut or generic cowboy toys. blank slates that you could make original characters out of. Every cowboy toy at the store now is a Woody, every spaceman is a Buzz Lightyear. Even Mr. Potato Head has been re-branded as a Toy Story toy. The world depicted in the movie is unrealistic because it doesn't have Disney branding all over everything, ironically. Disney devoured that world and replaced it.

we don't need a "please don't use this for evil" code license. we need a diverse professional organization with a code of ethics that reviews free+open software so we can properly collectively own that software, advise its dev/use, and apply consequential pressure upon misuse.

I see this same kind of stuff in the LineageOS/Android ROM community, and it bums me out. It's like we're given a choice between 1) trust Google/Comcast/$BIGCORP with all your private date, or 2) trust some Macedonian teenager who compiled a binary somewhere. And of course, this choice is not even available to the non-technically-inclined (who frankly are better off going with Apple).

Dear @gitlab, after reading this, I am ashamed to be using your product:

gitlab.com/gitlab-com/www-gitl

We will stop using it as soon as we can manage to and I will stop recommending you to others. Unlike you, we don’t associate with folks incompatible with our values.

Shame on you.

#gitlab

take me down to parallel city where the lines are straight and stretch to infinity

A colleague showed this Untitled Goose Game-inspired poem to us (made by his wife)

Please do not let your web app hijack the control-F/command-f shortcut in a browser window. I need it more than you do.

Genie: You have ONE WISH.

Me: Alright, I have one, but it's very detailed.
Genie: As long as it is only one wish, you're allowed to spend as much time as you want detailing it.

Me: Alright, here we go. *Grabs notebook and takes a deep breath* The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in [RFC2119].

Genie: Wait, is that...?

Me: *Flips notebook* Chapter 1. Preamble.

@cwebber Do all endpoints need to know about attenuated ocaps and their restrictions, or should there be some sort of attenuation service that forwards requests after checking whilte-listed operations?

Or would we need to pass round chunks of signed metadata that describe the caveats put on a capability?

So I've been reading up on stuff hoping to base a new experimental system on them at work after seeing @cwebber toot about it here but there's something I don't quite understand about how they work /in practice/ in a distributed system.

How does one actually *do* capability attenuation?

Show more
Mastodon

My home on the Fediverse.