I tried to comment in this thread:
https://fedia.io/m/news@lemmy.world/t/339242/Ex-Americans-are-suing-America-to-get-back-some-of-the
Wrote out a msg, clicked “Add comment”. The button faded and changed to “Sending…“ then simply reverted back to “Add comment”. My comment does not get posted.
#Lemmy is plagued with this behavior where you take the time to fill out a form & submit, and it simply does nothing and gives no reason for the refusal. It’s extremely frustrating because my effort is thrown away and I don’t even get to know why. If a form won’t be accepted, then don’t present it to me in the first place.
Now #Kbin is doing it.
Lemmy devs say the lemmy server is solid and that it’s the Lemmy web client that’s buggy and flimsy – which seems likely (the client is javascript after all). But in this case at hand I’m using a kbin client to post to a lemmy community.
Is the kbin client talking directly to the lemmy server, or does the fedia kbin server proxy the msg? I suspect the former because I’m on tor and #LemmyWorld is #Cloudflare configured in a tor-hostile way.
So #fuckCloudflare. If this is a CF problem then the Kbin client should be smartened to make CF threads read-only so people don’t waste their time trying to generate content.
OTOH I have some doubt about the Cloudflare-blockade theory because I am able to vote in that thread. Why would my votes stick but my comments be refused?
If you retry it doesn’t let you? From kbin I saw an error trying to reply to a post, but then I retried and it worked.
I’ve retried several times, even with a long delay. I also tried re-entering the thread (which is often the fix for kbin-specific failures) and that did not work either.
(edit)
Note that to send this reply to you here in this pure kbin mag I had to submit twice. But in that #LemmyWorld even many retries makes no difference. I would love to have a text-based client about now.
