Bug

You probably have a browser extension farming monero in the background because you used duckduckgo to download utorrent. Disable all your extensions and then run a virus scan and try again

Essentially the only people I'm seeing that have issues with the forum also seem to have a lot of real life issues

App tries to submit post again when it doesn't receive the success signal the first time due to your internet connection issue

Root cause: internet connection issue

Though it can probably also happen due to load issues on Ragarok's end

You should actually go to the discourse website and make a bug thread for this I think it would be really funny

1 Like

Have you tried using the namafia mobile app?

It's an issue for me on mobile. It started happening when I connected to 5G. This will be an issue for everyone because 5G works by constantly shifting you between different micro-cells. You're essentially changing networks very often, so posting during a change becomes an issue

Post it on the discourse website and see what they say

You could also contact your mobile carrier to see what they can do about the error message

1 Like

It's not an error. It's how the network is designed to function. Web services need to be able to handle it

People have posted about the intermittent connection issue before. Atwood is just a dumbass that doesn't accept any of his design choices could be poor, so the response is always "use recommended settings for limiting time between posts," which is dumb. It's the same thing with very long threads breaking: he'll never fix it because he'll never admit it's a problem that needs to be fixed

1 Like

How do you expect anyone here to be able to fix your issue?

Epok already declined my refactor request

Just go to blog thread 2. My problems went away.

Still think this is true.

The max value for a signed integer is +-32767 in a 16 bit program. I think my problems are from that.

1 Like

Well, I think Dan did fix the double posting issue by moving the timer from 0 seconds between posts to 0.5 seconds. The posts were being posted nearly simultaneously, so the fix works without hindering usability. I know there's no point in asking in the discourse forums because it won't get fixed there, so a workaround here (putting a small limiter on time between posts or using a plugin that doesn't let the exact same post in the exact same place go through twice) was the only way to get it fixed.

Why would forum posts be able to be negative?

Yes atwood is a dumbass and so are you. I think it would be funny to see you interact. You both are convinced you could never be wrong about anything and get really personally offended (and retaliatory) when someone suggests you might be

And the other benefit is that you might get an education about how these things work and why something would be designed that way (to resend a request when it doesn't receive a success signal on the first one) so you can stop posting here about how it's all very very dumb that you turn off your wifi and get weird network issues (and then ruin the blog thread because of it)

It's definitely implemented as unsigned

Ever heard of the Civilization Gandhi bug?
Google it.

Yes. Ghandi had a very low violence level and anything causing his level to decrease set it to the max possible

I think it would be really, really funny to ask them about this on the discourse website and find out there was actually an issue like this

You are experiencing issues with the blog thread. I am not. There is no configuration specific error that could possibly occur because of a rollover of a signed integer value on one machine but not another