just on moderation - I'm one guy unaffiliated with bluesky. I can do nothing with other reports. I understand the 'do something' urge to tick every box, I do, but it would mean a lot to my sanity to not be pulled to the worst things on the site, esp. since I can't do anything them.

I didn't get a chance this week (sorry) but this coming weekend will be the end of the 'new account' label.

ok. got some hard-ish decisions upcoming. The network is now large enough that labelling new accounts is becoming untenable, even when I only label on post the labeller falls behind. I get a lot of feedback that 'new account' is a major anti-scam tool, and I'm worried about taking that away.

so far these have stayed ahead of the influx, but I label *new accounts on first post* so doing a lot of numbers right now and we may be back to lag city

thank you by the way, to those that have been really patient with this - it sucks to have the wrong label just hanging around

some of these are in - the incomplete label, and I've compressed out a lot of redundant events (down by about 75%) labeller is about 2 weeks behind by my reckoning, with substantially lower label 'density' now so it shouldn't be too many more days before it catches up

ok I need to push a set of updates to the profile labeller in the next few days to make the number of labels something more sustainable - I've been putting this off bc life but unfortunately some things need to shift: (1/5)

(I don’t really have a good sense of how long this will take but will try estimate a time in the next day or so - I didn’t think to set up a log report for ‘what if I label too much’)

There are still a lot of labels out there that have yet to attach/remove - at this point all the labels have been *applied* so we're just waiting for the AppView to read all the labels off my label service (i.e. this is an app limit).

👀 I have about 1.5m to go, and have put out 8,494,814 label events since the start of my labeller - gonna hit 10m by the end of the week probably that's a bit

I suppose I didn't account for how many redundant entries there were when I saw millions of accounts all at once - 1,777,956 to go. That's... 2 days. And since I don't have time to work on it before the weekend anyway, suppose I'm doing things the slow way.

I still have a week to go before all the labels for the Brazilian invasion have been emitted 👀 I will send a carton of Real Australian Beer to the Bluesky team member that uncaps my ozone firehose

Meus feeds e rotulador passaram pelo maior pico (até agora), mas estarão um pouco atrasados por um tempo enquanto processam - por favor, tenha paciência, é como dois meses de atividade em dois dias. (muitas menções do Brasil, por favor, perdoe a tradução automática)

my feeds and labeller have gotten past the biggest (so far) spike, but will be running a bit behind for a while while they process - please bear with it, it's like 2 months of activity in two days

due to a bug with profile resolution earlier, some people are going to have a 'no display name' label for a little while - it'll clear up when the labels all catch up in the next few hours

This is around 500 'give something a label' events every minute, with ~1.6 labels per event what I'm saying is that I'm making a run at the busiest labeller leaderboard

I think this may be user logons or similar - we're almost there, but will have to restart the labeller in about 12 hours when the rate resets.

My choice to place a shield in the upper right corner of labeler avatars has blinded one eye of the polar bear. Sorry @profile-labels.bossett.social

normal sinus rhythm has resumed

something weird with my profile lookups the last ~2 hours - falling a bit behind while that gets sorted out

I wonder if anyone wants this

hey why are my mentions blowing up

One FAQ: Why are there accounts with both 'Elder' (from @labeler.mountainherder.xyz) and 'New Account' tags? I count 'New Account' from time of earliest *post/reply* in order to get a bead on 'when this person started using the account', the Elder label is based on account creation date.

Ok after a couple of days of playing chicken with the rate limiter I have something working. Will be refining both the timing (updated every 15m right now) and the combinations, so feedback welcome.

I've rolled out out lists that combine some of the labels, so you can choose to block certain label combinations.

ok ticking down - gonna be a bit before totally back up because I need to clear some of the old records at a rate of 3000 per w=3600

ACAB includes 'ratelimit-policy': '5000;w=3600'

(sneaky new label for nostr users)

(sneaky new label for bridgy users)

Two label updates: 1. NEW: 'Only Replies' - where a user only has replies in their history and no 'top level' posts. 2. 'New Handle' is now 'Changed Handle' to better reflect that the user isn't new. Didn't realise that 'handle' was synonymous with 'account' in other places.

ok I am a) alive and b) almost caught up to realtime - as with all software the issue is fixed permanently and forever so once this is done it should be all good

bit of a perfect storm - my labeller fell over about 24h ago (it's just got a few hours delay) while I was really busy so only just got around to fixing it; should be catching up now

The labeller is almost entirely automated, so if (e.g.) you add a profile image, it will remove the label by itself. May take a few minutes since I don't want to be *too* aggressive loading profiles. If you think you have a removal bug, ping here or @bossett.social or wait for me to check appeals.

I've changed 'High Volume' to be a periodic measure - I'm trying to flag bot accounts that post to a very set interval, not to identify people who post a lot.

New labels! No avatar/display name labels have gone in, and the new account/new handle logic is now more robust. The new labels default to *off*. They're hide/block labels and I don't want to default block brand new users until onboarding is better - but they're definitely gonna be useful to some.

Had a bug dropping 3p labels on web. Refresh should fix it. Will post about this on @bsky.app once all looks good

oh no broken while I work through this bug