Notices by blaine (blaine@mastodon.social), page 2

@evan nothing new, looks like activity has dropped off, initial Rank 6 fires have dropped to Rank 2-3, community meeting this evening. The wildfire service is really incredible and feels well organized from the interactions we've had. ❤️

@evan we'd been considering the possibility of a Montreal trip this summer, but felt uneasy leaving in summer (also it's really nice here when it's not burning 😅). Soon, though!

(I gotta say I don't miss planes, either. I wish the trans-Canada train had a slightly more comfortable and affordable seating option, would 1000% do that. I'll have to get your long distance rail tips at some point)

@evan heh, thanks, 💯 preaching to the choir. We're very well set up and safe in a nearby town about an hour away, extremely fortunate in that respect. ❤️

@evan looking slightly further out, we all need to take decisive political action – both to fight climate change and the effects of climate change, but also to take immediate actions that will protect our communities, environment, and infrastructure when disasters strike (not if — ask not for whom the climate bell tolls). Our highly reactive emergency/rescue orientation in funding and action is amazing to see in action but saddening because so much more could be done in prevention.

@evan wait. Hope.

Evacuated. We're safe with our cats, we'll see how the next few days go for our home.

Apocalyptic scenes up here in south-central British Columbia. This photo was from when things were relatively calm.

@thisismissem @evan alternatively having a "DM-native" protocol handle DMs – whether that's Signal or another protocol, it would be *trivial* to point a webfinger profile (or mastodon profile, but it'd be nice if this worked across different AP implementations) at a Signal account and let that other system handle it. Also adding developer-parseable support for DMs to AP would be trivial (except for all the encryption, so not really trivial ;-) ). Remember: we made all this up. It can change!

@evan the next poll: "direct messages in Mastodon are bound to appear in public feeds [of non-addressed users]"

Dipped a toe into a standards discussion and I remain convinced that it's not a world for me.

I wish we lived in a world where standards work was done by a wide, diverse, and open community rather than exactly the sort of technologist who loves to bikeshed.

It's such important work, and uniquely creates opportunities for amazing large-scale cooperation to happen. Too often, though, it's a place for insecure people to build little fiefdoms. 😢

@evan @julian @nightpool in the Postel sense, though, it's too bad that a client implementor needs to maintain (at least) four discovery pathways, and may require four separate requests to validate the information. Similarly, an ap host doesn't know which spots a client will check, so needs to implement all four. I'm well out of the standards game, but I'd very much advocate for "pick one and stick with it" 😊

@evan @julian @nightpool lots of folks advocated to support any URI scheme in a webfinger lookup, and that's why we have the "acct" scheme at all - so that email-style addresses could be used alongside http etc URIs!

The <Link> approach definitely works, but feels a bit reinventing-webfinger/creating more complexity in lookups (on the client side).

Hope the context is helpful! 😊

@evan @julian @nightpool for what it's worth, webfinger should be (re: is) able to do this, even if the implementations in the wild don't. The intent at the time was for webfinger to be the "DNS records" for "social addresses", and the main reasons we didn't just use DNS was because (1) DNS doesn't support anything but bare domain names, (2) management of DNS records at scale is hard, and (3) it wasn't possible to query DNS via the web.

@dymaxion lol, fair. I'm not sure I'm ever going to be able to sustain 12 solid hours of foreplay though. 😂

The back-woods, working class, remote rural community near where I live, whose primary employers are a zinc/lead smelter and a pulp mill, just elected amazing queer hero, Birkley Valks, to the local school board of trustees. He soundly won the election against a hate-mongering anti-trans bully.

Love wins! 🎉🏳️🌈🏳️⚧️❤️

The real reason to write rust is that sex is good, but have you ever tried a successful build after fighting with the esp-idf+cargo toolchains for 12 hours?

@schoenswetter almost – I'm thinking specifically about newly created accounts, which, apparently Mastodon already supports!! https://mastodon.social/@mcc/112209005598142179

I'm clearly behind the times; awesome to see the fediverse blazing ahead of established monopoly networks.

One must imagine Sisyphus listening to "Happy"

On instagram, which I only use these days to follow friends who are on there, the most frequent "notification" is from obvious spam (presumably phishing) accounts. Meta has thus far been unable to stem the never-ending flow.

Except these accounts are all brand new. I don't know anyone who's not on instagram in 2024 that will decide to sign up and follow *me*

If Instagram had a flag that said "don't let new accounts follow me", it would stop the spam dead.

Fediverse apps should do this.

@ch0ccyra1n like https://github.com/sfomuseum/go-activitypub from @thisisaaronland - exciting times!

I expect (hope?) we'll see a lot of these. Like apache/nginx/etc and the many micro web frameworks in every language. 😁

I'm not sure if it's new or if I'm just really bad at paying attention, but I just learned about it and I'm so excited about #fedify: https://unstable.fedify.dev/

I think systems that are shaped like fedify are one of the key things needed to really open experimentation and exploration of the possibilities that the fediverse affords.