• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • Just tried on some browsers in private/incognito mode and all worked when not logged in.

    But then I logged in, and the problem appears again. After some testing, I found that the problem seems to be on the default comment sort.

    When set to old (which was my default one) I have the error, but when using any of the other options (new, top, hot), the comments display correctly.

    EDIT:

    The same happens when using mlmym.org to visit the lemmy.world instance. When set the comment sort do old, I got the error. Changing to new, it works.

    But using mlmym.org on others instances I tried, it always works even when using the old as default.





  • le__el@lemmy.worldtoBrasil - Geral@lemmy.pt"Min ajudar, Lussiano"
    link
    fedilink
    Português
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Se você procurar apenas pelo termo, ele só vai pesquisar nas comunidades que a sua instância já federou.

    Exemplo, você tá na instância do lemmy.world e pesquisa algo, ele só vai mostrar resultados de subs que algum usuário do lemmy.world já tenha acessado anteriormente.

    Mesmo que seja de instância remota ele vai achar, mas com um adendo, apenas os posts após a federação inicial serão mostrados (posts feitos antes do lemmy.world ter federado com a instância remota não deve aparecer).

    E pra conectar com uma comunidade remota pela primeira vez, caso ainda não esteja federando com a sua instância, você precisa colocar o endereço completo da comunidade na busca, exemplo https://lemmy.ml/c/algumacoisa.

    Aqui tem um índice com links de comunidades, mas não sei quão atualizado ele se mantém: https://browse.feddit.de/

    EDIT:

    Mais um adendo, esse índice do feddit só lista comunidades do lemmy, então se for uma comunidade hospedada no kbin, aparentemente não vai aparecer lá




  • If you try to make another non nested comment (or reply directly to your original post) and it show up on beehaw, we can be sure that the federation is running and the comments (and nested comments) that involves the defederated instances are all completely banned from there.

    EDIT: Catch42’s comment also didn’t show up there yet, so the federation seems to be is a big laggy.

    EDIT2: And now Catch42’s commented showed up there, so the federation synced up and the comment thread that involved any user from defederated instances didn’t show up.





  • I also had the same issue on my first login (the email was verified, btw). The login button just went spinning and nothing happens. Trying the login on Jerboa gave me invalid credentials (it wasn’t a mistype, because I used a password manager).

    The workaround I did was to do a password reset and use a simpler one (was 50+ chars with special chars on, then changed to 32 chars and no special chars).

    Not sure if what fixed was the reset itself, or the new password.

    After this, the login went smooth on both the website and the app.

    EDIT: And when posting this, the post submit button also kept spinning (the more than 200+ chars issue). But trying in a new tab, the message was actually sent.

    And some minute later, on the old tab the message was sent, but the OP post changed from the “improvements and issues” to “The inability to post multiple pictures is holding Lemmy back.”, but the comments below mine where for the “improvements and issues”, while the comment above where to the other thread.