Email or username:

Password:

Forgot your password?
dansup

Ironically, the most complicated part of domain blocks is the Domain Block settings page where you can view, add, and remove blocks

I spent a few hours building this in a way that is compatible with the MastoAPI and look forward to shipping this later this weekend

5 comments
dansup

The ironic part is that you'd think it would be more complicated to handle the block logic across the backend, but that is simple

The domain block settings page is more complex because of pagination, search and import/export functionality.

I may skip import/export for now so I can ship basic domain block support sooner.

Thanks for following along, and more importantly, thank you for helping me prioritize this essential safety feature.

#pixelfed #domainBlocks #safety #privacy

Pixelfed Domain Block settings, shipping soon!
wikiyu

@dansup i have a hope that it will be blocking per-user and not per-instance (which in most cases different then legal/pr0n/hardcore lack of moderation is not needed)

dansup

@wikiyu Yes, this is per-user blocking, users will have the ability to block any instance they desire (except their own, obviously)

wikiyu

@dansup now i am thinking about blocking own instance... and it looks as stupid (on first look) as allowing admin account to migrate to another server.

And that second one is sth that i needed to hack few days ago to migrate from selfhosted to infosexchange

Peter Toft Jølving

@dansup
I've always felt that most UI work is substantially more complicated than the majority of backend work. Not completely unrelated to why I choose to focus on the backend. 😂

Go Up