Thank you, gentlemen raincoat and Rambler, for discussing this issue. Even though I am a random guy passing by, the concerns you raise do touch me. I feel that free speech issues should never be forgotten here. It would be of my great pleasure to try raising this topic from ashes and encourage other forum users having a look and thinking about it one more time.

Meanwhile, I will try to help in increasing the awareness, despite the smallness of my resource. Absolute freedom of speech must exist not only for the sake of conspiracy giggling.

i'm here rambling from the i2p network!! lol on my end ramble seems to work really well for me!

Ok, thanks for the explanation.

If you had an old login cookie in your browser cache, you'll probably still be able to post from the clearnet or .onion site for as long as that cookie persists and is valid, or until we proactively invalidate or otherwise neuter non-i2p cookies.

However, it shouldn't be possible to login or signup from anywhere other than ramble.i2p. This is by design to minimize abuse and the concomitant moderation workload, and to encourage I2P adoption.

But I'm posting from the clearnet site Ramble.pw right now. Is this not going to be the case in the future?

Clearnet posting wont' work, it's only available over I2P, or should be. All networks are read-only besides I2p.

I'll probably still post from the clearnet site only, but it's good to see that this site is not abandoned.

Fixed!

Based on what is happening with Reddit it's good idea :D

It really is. Hopefully this may encourage some new users to check out I2P. I guess a easy-to-follow newb's guide to connecting to I2P may be in order eventually.

A step in the right direction. I2P is a great network.

700 m4ny w0rd5 4r3 b4nn3d, 17 m4k35 7h3 5173 unu54bl3.

He hasn't posted in over a month. So maybe he has, or someone got him to abandon it.

As was said earlier, it's HTTPS issues. I'm experiencing similar problems on Firefox. Using HTTP over yggdrasil works fine for me. Clearnet connection with HTTP also works, but you won't have encryption.

I hope /u/Rambler hasn't abandoned the site :s

The certificate is outdated, so it cannot finish HTTPS handshake.

What software are we using here, is it on github? I really like these forums.

I'll see about having the message updated to more accurately reflect the issue.

Ah, so it's a feature not a bug. No problem.

Sorry for the inconvenience. This is done on purpose because of the amount of abuse, spam registrations and posts that happens through Tor.

In the meantime, please consider using I2P or Yggdrasil if you'd like to also post from an alternative network. Tor is on time-out until we can figure out a way to make it not just a ripe avenue of abuse and spam. =/

that's an impressive flex - thanks for doing good stuff with your powers

Wow, that's good to know.

I also own the ISP that hosts this site. Our policies aren't changing anytime soon.

Enjoy it while it last. If Ramble ever gets too big, they'll get bought out/threatened/servers pulled.

I have had same issue after I upgraded Firefox ESR to version 102 from 91. No addons. HTTPS-Only Mode is disabled.

Edit: Somehow this issue was dissolved. And redirect to IP address url 23 . 137 . 250 . 250 occasionally on Firefox ESR 91 and 102 after RAMBLE site updated.