Today @dansup mentioned spam again. I think we all see it and I already spoke about stopping it in a federated way.
Here is a mockup of what I think is possible.
1. setup a blocklist on two levels. One for the name and one for the servers. This can be done by using dns, done it in the past.
2. make it federated so every server is able to use it. Be aware, able is not something that should be mandated.
3. have a whitelist available so you can assure your users are able to enjoy your services.
4. people should be able to whitelist.
This is simply a base set of requirements that should be available. It more or less works like service spamhaus and others offer. I can think of a lot of other features but this set is something that will allow you to run a server and be able to not fight spam in a time consuming way.
The advantage is that if owner foo blocks user xyz then owner bar will not be bothered with the spammer. Therefor reducing the workload on negative things.
I am reaching out to some of the bigger players I know. Please invite others that do play an important role to discuss this if you feel the need.
@mike
@🎓 Dr. Freemo :jpf: 🇳🇱
@Mark Nowiasz
@dansup
Are you guys/girls willing to work together in assembling a blocklist under the conditions mentioned in this posting? If not, can you state why?
I am willing to make an effort, I am not sure you would.
Here is a mockup of what I think is possible.
1. setup a blocklist on two levels. One for the name and one for the servers. This can be done by using dns, done it in the past.
2. make it federated so every server is able to use it. Be aware, able is not something that should be mandated.
3. have a whitelist available so you can assure your users are able to enjoy your services.
4. people should be able to whitelist.
This is simply a base set of requirements that should be available. It more or less works like service spamhaus and others offer. I can think of a lot of other features but this set is something that will allow you to run a server and be able to not fight spam in a time consuming way.
The advantage is that if owner foo blocks user xyz then owner bar will not be bothered with the spammer. Therefor reducing the workload on negative things.
I am reaching out to some of the bigger players I know. Please invite others that do play an important role to discuss this if you feel the need.
@mike
@🎓 Dr. Freemo :jpf: 🇳🇱
@Mark Nowiasz
@dansup
Are you guys/girls willing to work together in assembling a blocklist under the conditions mentioned in this posting? If not, can you state why?
I am willing to make an effort, I am not sure you would.
@🎓 Dr. Freemo :jpf: 🇳🇱 Thanks, it is solvable indeed. Both using the whitelist and giving a note when someone is posting it ( think of the non delivery notice e-mail uses). They should be able to delist from it to a certain degree.
Follow
🇳🇱
@hanswolters I think if block lists are to federate then it needs to be a bit more to it than that.. I federate with many servers where it would be more work to white list or opt-out on a case by case basis than the amount of spam I get. There is probably a better way to indicate whose additions to the block list i will trust by default and whose I would not. It would also be key that the specific posts which triggered the block be attached to the block list rather than a note (which I wouldnt trust as much).
