all 7 comments

sorted by: hot top controversial new old
[–] 3 points 3 months ago (1 child)

A miserable pile of secrets.

  • source
  • hideshow 1 child comment
  • [–] [M] 1 point 3 months ago (4 children)

    Not sure why the proper title failed to fetch. Sorry about that.

  • source
  • hideshow 4 child comments
  • [–] 1 point 3 months ago (3 children)
  • 10 comments in c/div0@lemmy.dbzer0.com view that post
    [–] [S, M] 8 points 3 months ago* (9 children)

    All done. Unfortunately it seems tesseract doesn't like this version. I'll see if there's a workaround

  • source
  • hideshow 9 child comments
  • [–] 5 points 3 months ago (8 children)
  • [–] [S] 7 points 3 months ago (3 children)

    Holy shit. I thought it was just an API version mismatch! The turbolib dev literally hardcoded our instance into a blacklist! Guess we have to decommission that frontend now.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 3 months ago (1 child)

    Well technically it was a downgrade from having our own special warning to a simple block, but yeah. I remembered reading that newer versions of Tesseract had flexible version support, so I was really surprised to see that message, had to check what was happening. I'm bummed tho, now I have to get used to a new UI :(

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 3 months ago (3 children)
  • [–] 2 points 3 months ago (2 children)

    Interesting. I'm curious to know what their reasoning for that is

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 months ago (1 child)

    The commit I linked added dbzer0 to the same blacklist, removing a custom warning that said

    "This instance and its admin staff encourages identity politics, groupthink, mob mentality, and extremist solutions to societal problems. Users who advocate violence are not moderated so long as the admins agree with the target. Caution and critical thinking are advised when interacting with this instance or its users."

    So probably something along those lines.

  • source
  • parent
  • hideshow 1 child comment
  • 1 comment in c/tecnologia@lemmy.eco.br view that post
    [–] 4 points 3 months ago

    Maravilha. O uso de recursos do Lemmy sempre foi apontado como um problema. Parece que finalmente acharam uma solução eficaz. Só falta conseguimos um bom alocador para programas que usam Tokio que suporte todas as arquiteturas.

  • source