this post was submitted on 15 Sep 2024
4 points (83.3% liked)

Mander

432 readers
1 users here now

founded 2 years ago
MODERATORS
 

I just got burnt. Wrote up a relatively high-effort post in:

http://mandermybrewn3sll4kptj2ubeyuiujz6felbaanzj3ympcrlykfs2id.onion/c/water

clicked sumbit, and it simply ate my msg. Redrew a blank form.. no way to recover the info loss. This is my 1st use of the onion, so I did not think to enable 1st party j/s (which is strangely off be default in noScript on Tor Browser despite clearnet sites having 1st party js enabled by default). It’s unclear if it’s a JS problem or if it’s because the onion version uses a quite old/classic reddit-like theme. In any case, it sucks.. it’s a defect for sure.

top 2 comments
sorted by: hot top controversial new old
[–] Sal@mander.xyz 1 points 14 hours ago

Thanks for pointing this out... I am very sorry that this happened. I have not tested the .onion front-end much.

Sorry for missing this post, I was traveling during holidays last month.

The server that is serving the .onion front-end is running only that service, and so I doubt it is ever under heavy load. I am not sure if this was a problem with the onion network itself, with the front-end, or the instance. When I looked into options I could not find examples of Lemmy instances using .onion front-ends and I picked the one I did because it does not require JavaScript.

I will make an effort to use the .onion site myself more often and I will look for other options.

[–] plantteacher@mander.xyz 1 points 1 month ago* (last edited 1 month ago)

As a test, I enabled js on the onion site and tried again to post from the onion connection. Again my message was simply blackholed. So noscript’s default disabling of JS is not the issue.

(edit) then I posted from the clearnet site mader.xyz.. no issue. This problem is onion-specific.