Show newer

In general, I think there's a lot of places where software assumes a certainty that just isn't justified. I'd love to see more software handle uncertainty in a robust way.

Show thread

seeing a show from a streaming service that’s got like four seasons and still going is, like, how did you survive, little guy? did they not notice you?

“Their response? A masterclass in liberal evasion.
Rather than engage the substance of my critique, SMA’s leadership sent back a polished, polite note thanking me for the “tone” of my letter while ignoring every single argument.They claimed “capacity constraints” as the reason they couldn’t continue the conversation.This, despite launching a book, fundraising, hiring teams, and expanding globally.
In other words:they had the capacity for power,but not for accountability.” counterpunch.org/2025/05/18/ho

Vor ein paar Tagen gab es ja diesen Vorfall mit dem Containerschiff, was im Garten eines Norwegers eingeparkt wurde.
Jemand auf Bluesky postete den Link zu dem Livestream, in dem nix passierte und das ganze mehr ein entspanntes Stillleben war.
Daraufhin haben sich alle so sehr in diesem Thema hochgeschaukelt, dass ich gestern allen ernstes ein Fanart zu dem lustigen Boot gemalt habe.

Es ist random, ja, aber für solche Momente liebe ich das Internet. ❤️

#Fanart #Mastoart #Ship #BigBoatStuck

@joepie91 Komo isn’t a brand, but a standard. So, to forward the complaints to the correct manufacturer the body taking care of the standard came up with this system.

@joepie91 nl.wikipedia.org/wiki/KOMO

They're made by several manufacturers, that are certified to use the brand name. When a manufacturer screws up, they can lose the accreditation.

Just learned that there's a trashbag brand in NL that has a whole dedicated 'complaints' website, with an extensive list of possible manufacturing errors: klachtenadreskomoafvalzakken.n

Can't tell whether they really care about quality, or they just have so many manufacturing issues that they needed to automate the complaint handling process this extensively

mozilla, AI, questions, complaining, wei are so tired 

@joepie91 ¿Wtf is 'smart search'? Doesn't FF just blob out their searching to google or duckduckgo or something?

The only good thing they mentioned in this is vertical tabs. A shame that tree style tabs are a few parsecs ahead in terms of features and usability.

Wei never used these removed features, and yet wei feel upset they are being removed [especially] for more effort into garbage llm [etc] stuff. It's amazing the culture of disposability in tech. Everything is only here for a few years, maintaining trusted apps, programs, etc not as cool as just pivoting to new slop. :blobcat_tableflip:

It's particularly odd because it's the comments where I explain some government procedure that get removed, and not the more irritated superficial comments.

Show thread

Hmm. Lately I've noticed some of my comments on YouTube disappearing from view, especially those that mention government in some way; both in Dutch and in English.

In all cases, it's unlikely that they were removed by the channel owner, given the content of the comment, who operates the channel, and the rest of the comments around it.

Wonder what's up with that.

(This has been true for at least 7 years by this point, probably longer)

Show thread

Since I realized that probably not a lot of people know this: Google does network-level (ie. TCP/IP-level) fingerprinting to detect automated requests, in addition to HTTP fingerprinting and more 'traditional' methods such as cookies and IP tracking.

I only know with *certainty* that this is used for scraping prevention on the search engine, but I would not be surprised if this were used for user tracking as well, given Google's history.

If I'm going to spin up a new Fedi instance, I think I'm going to establish this rule:

Do not use the term NSFW in content warnings. When describing the subject matter of a post in a content warning, you must be specific (e.g. "explicit sex" or "nudity").

NSFW is a bad term to use for three reasons:

It's vague. It doesn't describe anything in the post to the viewer. They don't know what they're getting into when they open that CW. Adding "NSFW" is either cruft that could have been dispensed with entirely, or a catch-all that the poster uses to escape responsibility for adding more specific terms.
It's poorly defined. While there are some subjects that are pretty universally acknowledged as likely to get someone fired, policies vary from one employer to another. Using the term is therefore of little value to the viewer for the specific reason it's intended.
It's based on the value judgments of (generally) capitalist, hierarchical entities whose value judgments have been shown time and again to be detrimental to our society as a whole. Maintaining the kind of kink-friendly space that I want to have is antithetical to allowing such entities to define what is acceptable to express and communicate.

#browsers #Firefox #EU
The EU should start a Foundation that is funded to fork and then continually develop Firefox for the good of its people and all humanity.

They have the wealth, the ability and everything needed. Just do this.

Het was vandaag goed weer om zagen te slijpen en we hebben ook weer scherpe zagen nodig als we verder willen zagen.

We zetten de zagen voordat we ze slijpen. De machines die we erbij gebruiken zijn heel precies, maar het instellen ervan is nog steeds veel handwerk.

advice on developing libraries/frameworks (3) 

There's a lot of common advice about things like API stability and upgrade paths and whatnot, but that sort of advice tends to be very "draw the rest of the fucking owl" - the recommendations above are how you actually *get to* those kinds of design properties without burning yourself out.

Show thread

advice on developing libraries/frameworks (2) 

(You can go further and have a fully-decoupled 'constellation' of unopinionated libraries, or take a standards-first approach to every component, but those sorts of approaches require a lot more upfront work and practice than the things described above - I definitely recommend working toward them, but start with the above or you'll never get anything out the door!)

Show thread

advice on developing libraries/frameworks 

How to make a framework or library that doesn't end up producing applications that are miserable to maintain or extend:

1. Make every component optional to use and easy to bypass.

2. But make sure that the lower-level mechanisms that those components use are also directly addressable/usable.

3. Leave deliberate gaps in your API design for bespoke application-specific things to go.

4. Do not make assumptions or structural demands of user code unless you're also willing to design abstractions that ensure them on behalf of the user.

5. Decouple the parts of the framework as much as possible, and treat them as mostly-separate libraries that just happen to work well together, preferring standardized data representations between parts where possible.

That's really all you need to allow users of your framework/library to do their own thing and swap out the bits that don't work for them, but so so few projects actually do these things...

no sorry i dont really use instagram, i can contact you via ouija board, spirit box, fluctuations in temperature, flickering lights, and certain rituals. i am also on mastodon.

20 years ago we were suing teenagers for millions of dollars because they were torrenting a single Metallica album and now billionaires are demanding the free right to every work in history, so that they can re-sell it.

The law only ever serves capitalism.

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.