Show more

Beyond update (version 2.0) officially launches tomorrow, but there's a rumor it'll be available to download tonight, in about 1.5 hours from now.

(I can't wait to explore other planets in VR. How cool will that be?)

Since I know the news that #Facebook planned to backdoor #WhatsApp got a fair bit of traction on Fedi (I think I shared some related links), it's worth pointing out this retraction from Bruce Schneier:

Of course, level-headed retractions never get as many boosts as prejudice-reinforcing security panics... but for those of you who care, there it is.

A recent commit in darktable's git repo removed the block on using Neo OpenCL, meaning: development snapshots of now support GPU acceleration for modern (within the past several years) Intel GPUs for a noticeably big performance boost, provided you have Intel Neo OpenCL suppport installed and compile darktable yourself.

Summary: Quicker photo editing in darktable for Intel laptops (without NVidia or AMD)!

This should land in a release by the end of the year in most Linux distros.

We should just call static websites 'micro pages', the industry would be all over that immediately.

One of my favorite subtle changes that Firefox and Chrome made recently, and which I really appreciate, is making it so the backspace button doesn't go back anymore.

Can't tell you how many times I've been editing a piece of text, lost focus, pressed the backspace button, then the browser navigated back and I lost my work. Alt+left exists; I don't need the backspace for this.

IT DOESN’T NEED AMP. It’s entirely static, is as fast as or faster than AMP sites, and is served from a fast global CDN with aggressive caching.

I’m INCREDIBLY tired of Google abusing their position as the global search monopoly to push their tech on sites or fear being demoted.

I launched a new blog this week. It's stupidly fast, uses zero external JS or CSS resources, is responsive, and supports modern features many sites don’t like dark style support. But Google just emailed me saying they might deprioritize it on Google because it doesn’t use AMP.

heyo, code people friends! Just thought I'd let you know about this helpful testing resource I ran into a few years ago:

it's a long long list in various formats of bits of text that are liable to cause Problems when you use them as user input, from control characters to fancy unicode to things that look like rude words to simple script injections

utopian future in the 1980s: flying cars
utopian future in the 2020s: no cars

Person A: "What is speleology"
Person B: "The study of caves. Here's a wikipedia link if you want to learn more."
Person C: "Wikipedia isn't a reliable source@!@!!!!"

Me: I wish people would stop mistaking "don't use this as an academic source for citations in a paper" with "this is not a reliable source for getting an overview of what something is." For non-controversial topics, Wikipedia is rarely inaccurate, and controversial topics are typically flagged.

One thing I find confusing about accessibility and compliance is that the WCAG publishes three different levels: AAA, AA, and A.

Under the law today, can websites get sued for not meeting A? AA? AAA? Or is it a self-policing kind of thing? As in, do legal departments just set their own targets based on their appetite for risk?

BTW I definitely see performance as an issue of access. If the CEO, the investors, and the developers are all using beefy desktops on fast connections, then they'll never notice what their less fortunate customers are experiencing on a hand-me-down Android phone or a busted laptop with a HDD. It's easy to miss performance problems if you're not paying attention to users with less money than you.

Show more

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!