Tuned in to On-site Discussion!

>>3369
I think figamin didn't make a proper auto schedular tor kill and restart script. I don't know how figamin setup the tor configuration. Though the default vanilla tor setup has to be run through superuser privilege.

>>3370
It's supposed to restart automatically, but i realized i wasn't running tor in the background so it wasn't working right. Hopefully it should be good now.

>>3371
It works now.

However, I noticed a bug of sorts. If you follow a link to the last bump from the main page, it leads to the .org version instead of the .onion. All the other links seem correct.

>>3371
It died again.
And .org has been very slow lately, too.

>>3383
It was complaining about a compression bomb for some reason.
Anyways I haven't worked much on the site lately (busy irl) but this weekend I will try and figure out a fix for this, it's up for now

>>3384
>about a compression bomb
Not long ago 8chan.moe faced a similar problem. At least, compression bomb was mentioned in the context of tor address dying.

https://8chan.moe/site/res/5423.html#q16390

Not sure if this will be of any use to you, but I figured I'll leave the link to the post anyway. As far as I can tell, they didn't fix it reliably, because their .onion is currently dead too.

>.onion address dead.
>Your IP address is listed in rbl.efnetrbl.org.
>The collected sources are as follows: Scanned TOR exit node proxies

Uh-huh… ಡ_ಡ