Subj : Synchronet issues
To   : Spectre
From : apam
Date : Thu Oct 27 2022 13:28:03

 > Me either... not in 30 odd years... but as I keep saying, it doesn't
 > mean it
 > didn't happen.  If you extract the tarball, do the do whatever the
 > hell that
 > was, its to far back to recall, and the result is you have a raft of
 > stuff
 > missing permissions.  Then? Shrug.

It also doesn't mean it's got anything to do with synchronet, given that
it's happened to no one else, given that the installation makefile just
does not do that, means you're either lying, did something you didn't
know, or something else happened (filesystem corruption).

If it's too far back to remember, and you have no interest in finding out
what really happened, then perhaps you should stop pissing on rob's
project all the time. Stop calling it synchromess and implying it's crap.
Rob has put a large chunk of his life into writing Synchronet, and he
doesn't deserve someone making rubbish claims about it all the time.

If you don't care about it, and want people to stop calling you out about
it, then JUST STOP CALLING IT SYNCHROMESS. It's not funny, it's offensive
and uncalled for.

Andrew


--- Talisman v0.44-dev (Windows/x64)
 * Origin: Smuggler's Cove - Private BBS (21:1/182)

.