Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Notifications
Mark all as read
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post

I would like basic killfile functionality.

+7
−3

I would like, when I am logged in, the ability to specify that I do not want to see posts, or posts and answers, from a list of users. It would be preferable if this defaulted to the community that I am currently in, but had the option to add others or a universal that included future communities.

They should not be able to know that I am ignoring them except by the fact that I am unusually good at ignoring them.

I suspect other people will want this feature, too.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Avoid writing a duplicate answer? (2 comments)
Functional question (4 comments)

Comments on I would like basic killfile functionality.

Avoid writing a duplicate answer?
Grove‭ wrote about 1 year ago:

Another potential problem: If someone has asked a question that you know the answer to, but a user you're ignoring with this has written an answer. You won't know if what you're considering writing is just a duplicate of the already given answer, or if your potential answer contains something that might be of value to the asker (or someone else who comes across that question in the future.

Moshi‭ wrote about 1 year ago:

Grove‭ Perhaps if that situation occurs, a little notice telling you something like "this question has been answered by a user you have blocked" when starting to write your own answer. That way, it's out of the way until it's actually useful.