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.

  • plantteacherOP
    link
    fedilink
    arrow-up
    3
    ·
    1 month ago

    One problem with all Lemmy instances running later version than 0.19.3 is the front-ends are broken with Ungoogled Chromium. Lemmy instances running 0.19.5 essentially force me to use Tor Browser (firefox). This is unrelated to the onion problem but one of my other workarounds is to use a non-stock front-end with ungoogled chromium. So for example slrpnk.net has alexandrite.slrpnk.net, which is an alternative FE. The landing page of slrpnk.net lists a few other alternative front ends as well.

    I don’t know if there is a way for users to run alexandrite and then specify another backend of choice. But if not, it could be useful to make other front-ends available on the onion.

      • plantteacherOP
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        The create post form is dysfunctional. After entering a title I tab to the next field and the title is erased upon shifting the focus to another field. The form is unfillable.

        The timeline has 4 possible timeline views: subscribed, local, all, moderator view. That selector is broken in Ungoogled Chromium. In UC, I click “moderator view” and the button highlights as I click it, the page refreshes, but the selector does not stick. It is trapped in the “local” view and only shows the local timeline.

        I did not test Mander specifically on these, but it seems to be the same problem for all stock front ends newer than 0.19.3.