CIRCLE WITH A DOT

@Daveography wait wait what, this is *that* Chad?

@Njord the lack of easily available disposable or reusable masks that didn't use ear loops meant that every mask I wore before then was super uncomfy for my sensitive ear cartilage

But I mostly wore n95s after the initial cloth mask craze until I got my flo mask.

@fasterthanlime oh and governance: almost(*) any implemented rfc should be either accepted and stabilized or removed altogether after a reasonable discussion period in order to eliminate the bifurcated world where compiler and stdlib developers get to use features that languish for years (now some of them coming on a decade) in bikeshedding hell.

I call this the "shit or get off the pot rule." If I feature is important enough to use, it is important enough to stabilize.

(*) a separate category of feature flag should be established for the few things that are deep compromises that should never be stabilized but are necessary for the compiler to use.

@fasterthanlime and not what you asked but I think function coloring is not only fine, but desirable. Where I think rust has gone wrong in async is in the main libraries trying way too hard to pretend that an async executor is some ambient global thing that you can pretend you don't know about, and it creates an expectation of magic that can't be met.

Async functions are ultimately just a shorthand for state machines. They have uses even in otherwise not "async" code. But you need to know when you're interacting with a state machine and when you're not.

@fasterthanlime types: first class non-moveable and non-droppable traits.

@fasterthanlime semantics: I would add a pipeline operator. I think it would simplify a lot of common expressions.

@fasterthanlime syntax: angle brackets doing double duty as a kind of bracket and binary operator is a thing no language should have ever borrowed from c++, and the resultant turbofish pride is silly.

@mcc "it was always burning, and we keep on feeding it" just doesn't have the same ring to it.

@dysfun isn't that what @mcc wants though? The original spec was "back up to it and throw it in a drawer". Not surveillance, but not terribly different requirements.

@RogerBW @ireneista

@dragonfrog we are *so far* behind on having viable street level commercial in medium density areas that I do actually think a radical solution is needed if it's gonna change.

@EllenInEdmonton @Chigaze @satchmo35

@EllenInEdmonton imo any new multiunit residential over 3 stories (so not just high rise) should be required to have podium commercial bays proportional to their resident capacity.

@dragonfrog @Chigaze @satchmo35

@dragonfrog @Chigaze @satchmo35 I believe that there are a couple of residential towers downtown that are connected to the pedway, and I think that counts.

@ratsnakegames @mcc it's probably only a matter of time though. And as with fedi/AP, where this already did happen, how the network reacts and deals with it will be a real test of its philosophy.

@mcc @whitequark reminds me of the good(*) old days when the Twitter firehose was open... Surely history would never repeat...

(*) in hindsight probably not actually.

@mcc @jrose I suspect their share goes up when there's a mass migration event and goes down otherwise, because in a mass migration event people want the easy answer and that's the easy answer the Mastodon website gives them. But otherwise there's probably a lot of accounts on m.s that don't stick around, while people on other instances might be more sticky (at least unless their instance shuts down).

It's been a while since one of those migrations came here so I think overall that's probably correct.

@mcc @jrose and I'm pretty sure m.s isn't even close to 51% anyways, whether in terms of total accounts or active accounts. I think it's more like 30%ish eyeballing fedidb.com's stats.

There are over 30k distinct activitypub servers out there, all with their own moderation policies, for better or worse.