What more info does that snitch?
Privacy is a million things, of which most people know about 3.
To add at least 1 more thing to that privacy implication list...
Q: Do we have an updated privacy table of what free news servers do
with respect to nntp posting host/account obfuscation practices?
(aioe) (albasani) (bbs.nz) (bofh) (chmurka) (csiph) (dizum)
(endoftheline) (eternalsept) (freedyne) (gmane.org) (hispagatos)
(mixmin) (mozilla.org) (neodome) (netfront) (news4all) (novabbs)
(pugleaf) (samolyk) (solani) (sunsite) (tcpreset) (usenet.ovh) (xsusenet)
I ask only because once every decade (or two) I revisit the privacy
status of nntp posting hosts and account obfuscation (or lack thereof).
Below is the nucleation particle that caused me to re-think about it,
as I likely haven't updated this table in well over a decade myself.
This is an old table so it is NOT accurate, nor is it inclusive!
--- < begin old table > ---
The worst servers reveal your NNTP posting host/acct in cleartext.
Most servers obfuscate, but they never change their obfuscation.
The best servers (wrt privacy) switch up the obfuscation.
However, the obfuscation method may or may not be sophisticated.
aioe = obfuscates the NNTP Posting Host & never changes it
esept = obfuscates account information & never changes it
mixmin = first obfuscated NNTP posting host on a monthly hash, but
then reverted to static due to it being a PITA to maintain
albasani = obfuscates NNTP posting host & account for each post
solani = obfuscates NNTP posting host & account differently for each post
netfront = for decades it reveals NNTP posting host in cleartext
but I think it now displays a permanent obfuscation
sunsite = reveals NNTP posting host in cleartext
mozilla = used to post in the clear but I'm no longer sure what it does
Op 12-9-2026 om 19:57 schreef Maria Sophia:
Privacy is a million things, of which most people know about 3.
To add at least 1 more thing to that privacy implication list...
Q: Do we have an updated privacy table of what free news servers do
with respect to nntp posting host/account obfuscation practices?
(aioe) (albasani) (bbs.nz) (bofh) (chmurka) (csiph) (dizum)
(endoftheline) (eternalsept) (freedyne) (gmane.org) (hispagatos)
(mixmin) (mozilla.org) (neodome) (netfront) (news4all) (novabbs)
(pugleaf) (samolyk) (solani) (sunsite) (tcpreset) (usenet.ovh) (xsusenet)
I ask only because once every decade (or two) I revisit the privacy
status of nntp posting hosts and account obfuscation (or lack thereof).
Below is the nucleation particle that caused me to re-think about it,
as I likely haven't updated this table in well over a decade myself.
This is an old table so it is NOT accurate, nor is it inclusive!
--- < begin old table > ---
The worst servers reveal your NNTP posting host/acct in cleartext.
Most servers obfuscate, but they never change their obfuscation.
The best servers (wrt privacy) switch up the obfuscation.
However, the obfuscation method may or may not be sophisticated.
aioe = obfuscates the NNTP Posting Host & never changes it
esept = obfuscates account information & never changes it
mixmin = first obfuscated NNTP posting host on a monthly hash, but
then reverted to static due to it being a PITA to maintain
albasani = obfuscates NNTP posting host & account for each post
solani = obfuscates NNTP posting host & account differently for each post >> netfront = for decades it reveals NNTP posting host in cleartext
but I think it now displays a permanent obfuscation
sunsite = reveals NNTP posting host in cleartext
mozilla = used to post in the clear but I'm no longer sure what it does
Hello Maria Sophia,
Probably telling no news to you:
The following newsservers do not exist anymore:
- aioe
- albasani
- mozilla
- novabbs
Not sure about (did they stop?):
- dizum
- mixmin
No posting allowed (as far as I know):
- bbs.nz
- neodome (except neodome.* hierarchy)
- netfront
And:
- gmane.org is now news.gmane.io
(this is a newsserver which does not peer and has own newsgroups)
also via: news.gwene.org
Rink
PS.
I do not post in alt.privacy.anon-server
and I think it has nothing to do with peering.
Also your "answer to" adress is invalid.
Usenet
lawrencium.club.cc.cmu.edu 480 posting not allowed
news.dizum.net 480 posting not allowed
news.neodome.net 480 posting not allowed
news.uni-stuttgart.de 480 posting not allowed
paganini.bofh.team posting allowed
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 56:04:48 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,718 |