@sydneyfalk i have failed orz

@vahnj

it okay

you can do it again, fren

<3

just get that AWOO out there for the awooin' public and their heckin' AWOO needs

@bea err, that's odd

i can see "this may never get worked on because we have too high priority on other things" cuz it's kind of a nice-to-have but

it'd be nice to at least acknowledge that such a thing would be useful

@vahnj i suspect there are some things that might make it tricky but i guess you know the blocking code better than i do!

@bea to be frank it's not that hard

1. create an additional field in the blocklist table to indicate "user_default"
2. the instance-level blocking mechanism selects from the list where "user_default" is false
3. every time a new user is created on the local instance, copy the list of "user_default" blocks into the UserDomainBlock model for their account

voila!

there's gonna be some more complications in there but that's the gist of it

@vahnj hmmm that rustles my jimmies but i can't put my finger on why

@bea what part does?

@vahnj i guess shifting it to be all account based from instance level

i feel like you can only do this for silences rather than suspends i guess?

@bea for instance: a rake task should be integrated to support migrating a domain-level block to/from users, there's a UI component that needs to be managed, some work needs to be done to avoid overriding if someone's managed the domain block themselves, etc