Bossett

I think it's very useful to split centralisation from 'centralisation you can't escape' - like I *want* centralisation a lot of the time, but I also want a credible exit (e.g. we see this in big OSS projects where central effort is good and forking is your credible exit)

if we look at verifiers, etc. and consider inverting that relationship - "I am a member of this community, here is my token, my root is <x>" and then let features hang off that (discoverability, etc.) that would also help move the control 'out' so it's less about 'trust me first, then...'

not sure if that solves the problem wholistically - but it helps make community more durable (like a subreddit can survive the exit of a chunk of the mod team)

whenever I have discussions around what would work, the conversation tends toward co-owned repositories (that would survive a user leaving/losing interest/etc.) and ways to express degrees of trust (so I can express "I want to use this labeller but only to label never block")

one of the clearest gaps in the ecosystem - working against the lofty decentralisation goals - is how power concentrates in tools: lists/feeds/labellers

the implicit decision by bsky rn is "don't let these things become powerful", which also means "don't let these things become *too* useful"

but they are automated - idk that there's a better word that means "no human at the controls"

but I suppose it matters what people think the label is for - like is it for filtering, spam reduction, avoiding arguing with those AI auto-repliers, etc. etc.

why why?

just makes it lag a bit

the sun’s out and I’m riding my bike, so it is a good day

yea it should sort itself out after a little bit - it’ll see the migration as a change and then should clear on the next post; but will have a look when I get home

A push notification from copilot: A Poetic Start to Your Week See your name transformed into a poem by M365 Copilot.

my corporate dystopia now gets copilot-induced whimsy

Had to Reinvent the Sailing Block (To Replace Them All) YouTube video by Reversing Entropy

I don't know anything about sailing but I love a good information-wants-to-be-free story

I'm kind of assuming but the random power brick I was using was very very warm

does the rpi use vmlinuz-6.8.0-101-generic? no

so TIL I was separately remoted into the wrong machine

well TIL why the RPi people get particular about USB power

well they do it on a computer I suppose

my feeds broke so I added a watcher and now I need a watcher watcher and well, that's something they claim is a real job

we call this site reliability engineering

ok I think we're recovering

so the LAST time things broke I added a monitor and restart job and now I need to add a monitor and restart job monitor and restart job

Panic! at the vmlinuz-6.8.0-101-generic

yeah something is broken

some people might be seeing newer stuff, there's a cache so it might be flipping between broken (not refreshing) and not broken

oh stuff is broken I think cf went down and now things aren't coming back 👀

hmm let me check

it's a challenge 👀

amendment to the RFC: Records MUST match the vibe of site.standard.document.

a male and female gang-gang cockatoo on a dead branch, they are looking at the camera

fierce lil guy

The maximum current through the power cord is 16A, and the maximum power used by the power strip is 3500W (can't be used for a long time).

idk much about electrical safety but I'm pretty sure this power board is all about insurance fraud

I think any model that has some kind of either consensus or verification can work - ultimately you just need to indicate "do not trust this source", and the ecosystem needs some alternatives to go to in that case

or at least from the new plc foundation - there are probably a bunch of workable scenarios, but they can't work without initial cooperation

there are systems that could work - like CRL lists, and could introduce an external validation to the resolution (i.e. ‘these 3 directories agree…’)

but in terms of ‘take this record with me’, no I think you’re right

it should be possible with an “I’m over there” entry, but in the adversarial case they may just not publish that - so you also need a PDS attestation or smth, and means to re-point records which is where it gets complex because you have to care for *every* record (client caches, etc - very messy)