home.social

#nheko — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nheko, aggregated by home.social.

fetched live
  1. @element
    Kann man in Gruppen irgendwie einen #Bot einfügen der automatisiert um bestimmten Uhrzeiten an bestimmten Tagen Nachrichten versendet?
    Kann man überhaupt einen Bot einfügen?
    #matrixorg #MatrixMessenger #Element #ElementX #Cinny #Nheko #fluffyChat #schildichat

  2. My opinion on is slowly turning around. For years I promoted it as the best chat protocol that will eventually become the "glue that connects all communication platforms together".

    But the frustration with various issues within Matrix ecosystem keeps growing:

    - Still can't log into matrix.org account with on . Getting Cloudflare timeout (Error 524). Is my IP cursed?

    - Apparently I also timeout when trying to view rooms in some space in Element desktop.

    1/2

  3. My opinion on #matrix is slowly turning around. For years I promoted it as the best #FOSS chat protocol that will eventually become the "glue that connects all communication platforms together".

    But the frustration with various issues within Matrix ecosystem keeps growing:

    - Still can't log into matrix.org account with #Nheko on #Linux. Getting Cloudflare timeout (Error 524). Is my IP cursed?

    - Apparently I also timeout when trying to view rooms in some space in Element desktop.

    1/2

  4. My opinion on #matrix is slowly turning around. For years I promoted it as the best #FOSS chat protocol that will eventually become the "glue that connects all communication platforms together".

    But the frustration with various issues within Matrix ecosystem keeps growing:

    - Still can't log into matrix.org account with #Nheko on #Linux. Getting Cloudflare timeout (Error 524). Is my IP cursed?

    - Apparently I also timeout when trying to view rooms in some space in Element desktop.

    1/2

  5. My opinion on #matrix is slowly turning around. For years I promoted it as the best #FOSS chat protocol that will eventually become the "glue that connects all communication platforms together".

    But the frustration with various issues within Matrix ecosystem keeps growing:

    - Still can't log into matrix.org account with #Nheko on #Linux. Getting Cloudflare timeout (Error 524). Is my IP cursed?

    - Apparently I also timeout when trying to view rooms in some space in Element desktop.

    1/2

  6. My opinion on #matrix is slowly turning around. For years I promoted it as the best #FOSS chat protocol that will eventually become the "glue that connects all communication platforms together".

    But the frustration with various issues within Matrix ecosystem keeps growing:

    - Still can't log into matrix.org account with #Nheko on #Linux. Getting Cloudflare timeout (Error 524). Is my IP cursed?

    - Apparently I also timeout when trying to view rooms in some space in Element desktop.

    1/2

  7. Joder, cada vez le tengo más manía al puto Element (v. de escritorio para Linux). Desde que he cambiado de cuenta en Matrix me lo pone realmente difícil para conectarme, a lo cual me obliga todos los putos días. Y no me conserva ninguna de las preferencias entre sesión y sesión. Cada vez más tocapelotas el dichoso cliente. Estaba por pasarme a Cinny pero no permite mensajes de audio 😖 ¿Habrá que probar la beta de Nheko?

    #Matrix #Element #Cinny #Nheko

  8. Joder, cada vez le tengo más manía al puto Element (v. de escritorio para Linux). Desde que he cambiado de cuenta en Matrix me lo pone realmente difícil para conectarme, a lo cual me obliga todos los putos días. Y no me conserva ninguna de las preferencias entre sesión y sesión. Cada vez más tocapelotas el dichoso cliente. Estaba por pasarme a Cinny pero no permite mensajes de audio 😖 ¿Habrá que probar la beta de Nheko?

    #Matrix #Element #Cinny #Nheko

  9. Joder, cada vez le tengo más manía al puto Element (v. de escritorio para Linux). Desde que he cambiado de cuenta en Matrix me lo pone realmente difícil para conectarme, a lo cual me obliga todos los putos días. Y no me conserva ninguna de las preferencias entre sesión y sesión. Cada vez más tocapelotas el dichoso cliente. Estaba por pasarme a Cinny pero no permite mensajes de audio 😖 ¿Habrá que probar la beta de Nheko?

    #Matrix #Element #Cinny #Nheko

  10. Joder, cada vez le tengo más manía al puto Element (v. de escritorio para Linux). Desde que he cambiado de cuenta en Matrix me lo pone realmente difícil para conectarme, a lo cual me obliga todos los putos días. Y no me conserva ninguna de las preferencias entre sesión y sesión. Cada vez más tocapelotas el dichoso cliente. Estaba por pasarme a Cinny pero no permite mensajes de audio 😖 ¿Habrá que probar la beta de Nheko?

    #Matrix #Element #Cinny #Nheko

  11. Joder, cada vez le tengo más manía al puto Element (v. de escritorio para Linux). Desde que he cambiado de cuenta en Matrix me lo pone realmente difícil para conectarme, a lo cual me obliga todos los putos días. Y no me conserva ninguna de las preferencias entre sesión y sesión. Cada vez más tocapelotas el dichoso cliente. Estaba por pasarme a Cinny pero no permite mensajes de audio 😖 ¿Habrá que probar la beta de Nheko?

    #Matrix #Element #Cinny #Nheko

  12. So, wegen dieser ständigen Probleme und Fehler in #Element habe ich Element nun auf allen Geräten gelöscht. Auf dem #iPhone verwende ich ja eh schon #Fluffychat und auf dem #MacBook verwende ich nun #nheko. nheko-reborn.github.io/ #Martrix

  13. So, wegen dieser ständigen Probleme und Fehler in #Element habe ich Element nun auf allen Geräten gelöscht. Auf dem #iPhone verwende ich ja eh schon #Fluffychat und auf dem #MacBook verwende ich nun #nheko. nheko-reborn.github.io/ #Martrix

  14. So, wegen dieser ständigen Probleme und Fehler in #Element habe ich Element nun auf allen Geräten gelöscht. Auf dem #iPhone verwende ich ja eh schon #Fluffychat und auf dem #MacBook verwende ich nun #nheko. nheko-reborn.github.io/ #Martrix

  15. Other projects I use every day:
    #Matrix spec & clients like #FluffyChat and #nheko
    #Bitwarden & #Vaultwarden password manager
    #Neovim text editor
    #clangd LSP

    I'd love to encourage these projects to jump ship, and I celebrate those that do. I am much more likely to provide quality contributions if you host on your own forge, or a free one, and I am sure I'm not alone in this.

    GitHub is hostile to FOSS and, despite giving away lots of free-of-cost stuff I believe ultimately hurts us.

  16. Other projects I use every day:
    #Matrix spec & clients like #FluffyChat and #nheko
    #Bitwarden & #Vaultwarden password manager
    #Neovim text editor
    #clangd LSP

    I'd love to encourage these projects to jump ship, and I celebrate those that do. I am much more likely to provide quality contributions if you host on your own forge, or a free one, and I am sure I'm not alone in this.

    GitHub is hostile to FOSS and, despite giving away lots of free-of-cost stuff I believe ultimately hurts us.

  17. Other projects I use every day:
    #Matrix spec & clients like #FluffyChat and #nheko
    #Bitwarden & #Vaultwarden password manager
    #Neovim text editor
    #clangd LSP

    I'd love to encourage these projects to jump ship, and I celebrate those that do. I am much more likely to provide quality contributions if you host on your own forge, or a free one, and I am sure I'm not alone in this.

    GitHub is hostile to FOSS and, despite giving away lots of free-of-cost stuff I believe ultimately hurts us.

  18. Other projects I use every day:
    #Matrix spec & clients like #FluffyChat and #nheko
    #Bitwarden & #Vaultwarden password manager
    #Neovim text editor
    #clangd LSP

    I'd love to encourage these projects to jump ship, and I celebrate those that do. I am much more likely to provide quality contributions if you host on your own forge, or a free one, and I am sure I'm not alone in this.

    GitHub is hostile to FOSS and, despite giving away lots of free-of-cost stuff I believe ultimately hurts us.

  19. Other projects I use every day:
    #Matrix spec & clients like #FluffyChat and #nheko
    #Bitwarden & #Vaultwarden password manager
    #Neovim text editor
    #clangd LSP

    I'd love to encourage these projects to jump ship, and I celebrate those that do. I am much more likely to provide quality contributions if you host on your own forge, or a free one, and I am sure I'm not alone in this.

    GitHub is hostile to FOSS and, despite giving away lots of free-of-cost stuff I believe ultimately hurts us.

  20. Ok my #debian with not #flatpak didn't work. There are some apps I need ... like #fractal
    #nheko is a nice, but (personally) I really can't stand qt. Simply don't like.
    Mainly all #gnome circle apps work great....
    So having a stable #debian base with some "new" flatpaks might be a good plan for me.
    Because I forced myself not to distrohop for a year ... I still have 337 with debian to go ;)

  21. Ok my #debian with not #flatpak didn't work. There are some apps I need ... like #fractal
    #nheko is a nice, but (personally) I really can't stand qt. Simply don't like.
    Mainly all #gnome circle apps work great....
    So having a stable #debian base with some "new" flatpaks might be a good plan for me.
    Because I forced myself not to distrohop for a year ... I still have 337 with debian to go ;)

  22. Ok my #debian with not #flatpak didn't work. There are some apps I need ... like #fractal
    #nheko is a nice, but (personally) I really can't stand qt. Simply don't like.
    Mainly all #gnome circle apps work great....
    So having a stable #debian base with some "new" flatpaks might be a good plan for me.
    Because I forced myself not to distrohop for a year ... I still have 337 with debian to go ;)

  23. Ok my #debian with not #flatpak didn't work. There are some apps I need ... like #fractal
    #nheko is a nice, but (personally) I really can't stand qt. Simply don't like.
    Mainly all #gnome circle apps work great....
    So having a stable #debian base with some "new" flatpaks might be a good plan for me.
    Because I forced myself not to distrohop for a year ... I still have 337 with debian to go ;)

  24. Ok my #debian with not #flatpak didn't work. There are some apps I need ... like #fractal
    #nheko is a nice, but (personally) I really can't stand qt. Simply don't like.
    Mainly all #gnome circle apps work great....
    So having a stable #debian base with some "new" flatpaks might be a good plan for me.
    Because I forced myself not to distrohop for a year ... I still have 337 with debian to go ;)

  25. ahhhhh why does #nheko on #nixos now break for for me
    like dafuq

    it just says OLM fails to restore my session (all of them!) and fixing it is somehow super nontrivial....

  26. ahhhhh why does #nheko on #nixos now break for for me
    like dafuq

    it just says OLM fails to restore my session (all of them!) and fixing it is somehow super nontrivial....

  27. ahhhhh why does #nheko on #nixos now break for for me
    like dafuq

    it just says OLM fails to restore my session (all of them!) and fixing it is somehow super nontrivial....

  28. ahhhhh why does #nheko on #nixos now break for for me
    like dafuq

    it just says OLM fails to restore my session (all of them!) and fixing it is somehow super nontrivial....

  29. ahhhhh why does #nheko on #nixos now break for for me
    like dafuq

    it just says OLM fails to restore my session (all of them!) and fixing it is somehow super nontrivial....

  30. #matrix app options on #kde atm kinda sucks. #element is the best, but it's now among a number of apps that don't (properly) support kde wallet/#kwallet so that's a no for a while now, which is a shame cos it's worked fine before. #nheko has been recommended, and it's pretty nice despite some rough edges, but it is honestly not that hard to come across several bugs that make it unusable. kde's own matrix app (forgot the name #neochat) is pretty rough on the edges too, a bit basic looking, but def a lot less buggy than nheko - it has some bugs of its own tho like 'quote' messages not working properly, at least when the quoted/replied message has a photo (it shows a thumbnail of the correct image, but opening it up shows a totally diff pic - for instance). all in all, ur best option is element's web app, but for a chat app u wish to use daily for a lot, it's kinda jank to always be looking for ur browser window/tab. the element app on other platforms like #ios and #macos just works tho so dats a fallback, if u use those.

  31. #matrix app options on #kde atm kinda sucks. #element is the best, but it's now among a number of apps that don't (properly) support kde wallet/#kwallet so that's a no for a while now, which is a shame cos it's worked fine before. #nheko has been recommended, and it's pretty nice despite some rough edges, but it is honestly not that hard to come across several bugs that make it unusable. kde's own matrix app (forgot the name #neochat) is pretty rough on the edges too, a bit basic looking, but def a lot less buggy than nheko - it has some bugs of its own tho like 'quote' messages not working properly, at least when the quoted/replied message has a photo (it shows a thumbnail of the correct image, but opening it up shows a totally diff pic - for instance). all in all, ur best option is element's web app, but for a chat app u wish to use daily for a lot, it's kinda jank to always be looking for ur browser window/tab. the element app on other platforms like #ios and #macos just works tho so dats a fallback, if u use those.

  32. #matrix app options on #kde atm kinda sucks. #element is the best, but it's now among a number of apps that don't (properly) support kde wallet/#kwallet so that's a no for a while now, which is a shame cos it's worked fine before. #nheko has been recommended, and it's pretty nice despite some rough edges, but it is honestly not that hard to come across several bugs that make it unusable. kde's own matrix app (forgot the name #neochat) is pretty rough on the edges too, a bit basic looking, but def a lot less buggy than nheko - it has some bugs of its own tho like 'quote' messages not working properly, at least when the quoted/replied message has a photo (it shows a thumbnail of the correct image, but opening it up shows a totally diff pic - for instance). all in all, ur best option is element's web app, but for a chat app u wish to use daily for a lot, it's kinda jank to always be looking for ur browser window/tab. the element app on other platforms like #ios and #macos just works tho so dats a fallback, if u use those.

  33. #matrix app options on #kde atm kinda sucks. #element is the best, but it's now among a number of apps that don't (properly) support kde wallet/#kwallet so that's a no for a while now, which is a shame cos it's worked fine before. #nheko has been recommended, and it's pretty nice despite some rough edges, but it is honestly not that hard to come across several bugs that make it unusable. kde's own matrix app (forgot the name #neochat) is pretty rough on the edges too, a bit basic looking, but def a lot less buggy than nheko - it has some bugs of its own tho like 'quote' messages not working properly, at least when the quoted/replied message has a photo (it shows a thumbnail of the correct image, but opening it up shows a totally diff pic - for instance). all in all, ur best option is element's web app, but for a chat app u wish to use daily for a lot, it's kinda jank to always be looking for ur browser window/tab. the element app on other platforms like #ios and #macos just works tho so dats a fallback, if u use those.

  34. #matrix app options on #kde atm kinda sucks. #element is the best, but it's now among a number of apps that don't (properly) support kde wallet/#kwallet so that's a no for a while now, which is a shame cos it's worked fine before. #nheko has been recommended, and it's pretty nice despite some rough edges, but it is honestly not that hard to come across several bugs that make it unusable. kde's own matrix app (forgot the name #neochat) is pretty rough on the edges too, a bit basic looking, but def a lot less buggy than nheko - it has some bugs of its own tho like 'quote' messages not working properly, at least when the quoted/replied message has a photo (it shows a thumbnail of the correct image, but opening it up shows a totally diff pic - for instance). all in all, ur best option is element's web app, but for a chat app u wish to use daily for a lot, it's kinda jank to always be looking for ur browser window/tab. the element app on other platforms like #ios and #macos just works tho so dats a fallback, if u use those.

  35. We released version 0.12.1 of #nheko! This release includes a few security fixes around html escaping into the UI and properly attaching a mark of the web on Windows. I highly recommend you upgrade!

    This release also takes the first steps to room version 12 compatibility regarding the upcoming
    #matrix security release.

    You can find the release here:
    https://github.com/Nheko-Reborn/nheko/releases/tag/v0.12.1

    Enjoy! :)

  36. We released version 0.12.1 of #nheko! This release includes a few security fixes around html escaping into the UI and properly attaching a mark of the web on Windows. I highly recommend you upgrade!

    This release also takes the first steps to room version 12 compatibility regarding the upcoming
    #matrix security release.

    You can find the release here:
    https://github.com/Nheko-Reborn/nheko/releases/tag/v0.12.1

    Enjoy! :)

  37. We released version 0.12.1 of #nheko! This release includes a few security fixes around html escaping into the UI and properly attaching a mark of the web on Windows. I highly recommend you upgrade!

    This release also takes the first steps to room version 12 compatibility regarding the upcoming
    #matrix security release.

    You can find the release here:
    https://github.com/Nheko-Reborn/nheko/releases/tag/v0.12.1

    Enjoy! :)

  38. We released version 0.12.1 of #nheko! This release includes a few security fixes around html escaping into the UI and properly attaching a mark of the web on Windows. I highly recommend you upgrade!

    This release also takes the first steps to room version 12 compatibility regarding the upcoming
    #matrix security release.

    You can find the release here:
    https://github.com/Nheko-Reborn/nheko/releases/tag/v0.12.1

    Enjoy! :)

  39. We released version 0.12.1 of #nheko! This release includes a few security fixes around html escaping into the UI and properly attaching a mark of the web on Windows. I highly recommend you upgrade!

    This release also takes the first steps to room version 12 compatibility regarding the upcoming
    #matrix security release.

    You can find the release here:
    https://github.com/Nheko-Reborn/nheko/releases/tag/v0.12.1

    Enjoy! :)

  40. Don't open the #nheko room on #Matrix, someone is posting disturbing images.

  41. Don't open the #nheko room on #Matrix, someone is posting disturbing images.

  42. Don't open the #nheko room on #Matrix, someone is posting disturbing images.

  43. Don't open the #nheko room on #Matrix, someone is posting disturbing images.

  44. Don't open the #nheko room on #Matrix, someone is posting disturbing images.

  45. It is no secret I dislike #Matrix. I need to find a client that doesn’t eat all my resources (meaning not Element). I want to try the TUI written in Go but it uses Olm. Olm is deprecated in Nixpkgs so I asked a colleague. He recommended #Nheko. I went to give it a spin… but alas it too uses Olm for double ratchet encryption. Okay… so is there an upstream fix in Olm or Nheko I could patch in? So I go to check out the Olm project to see what it says <gitlab.matrix.org/matrix-org/o>…

    > It is not written in memory-safe languages (C and C++11), resulting in several CVEs

    Oh, no. The trigger phrase “memory-safety”… I know I am going to look into this a bit more & be sad or angry but do it anyways as another case of needless Rust propoganda… I see the MS GitHub issue about the situation for Nheko <github.com/Nheko-Reborn/nheko/> which points to this 3-year-old merge request to just f💀cking use OpenSSL/LibreSSL for crypto calls <gitlab.matrix.org/matrix-org/o>. That response is saying:

    > As we do not have much prior experience with OpenSSL, reviewing this code would require looking up the documentation for those functions to ensure that they are being called correctly, and that all the parameters are correct.

    So the folks building the chat encryption for Matrix protocol have no experience with OpenSSL? & instead of learning this ubiquitous, valuable cryptography tool to accept the MR (I still need to to be fair), they blame C/C++ & choose to ‘rewrite it in Rust’. This Rust ‘replacement’ is not a drop-in replacement & it seems the bindings are messed up or incomplete where the maker of Nheko is forking to fix the bindings. Am I missing something? WTF are these folks doing?

  46. It is no secret I dislike #Matrix. I need to find a client that doesn’t eat all my resources (meaning not Element). I want to try the TUI written in Go but it uses Olm. Olm is deprecated in Nixpkgs so I asked a colleague. He recommended #Nheko. I went to give it a spin… but alas it too uses Olm for double ratchet encryption. Okay… so is there an upstream fix in Olm or Nheko I could patch in? So I go to check out the Olm project to see what it says <gitlab.matrix.org/matrix-org/o>…

    > It is not written in memory-safe languages (C and C++11), resulting in several CVEs

    Oh, no. The trigger phrase “memory-safety”… I know I am going to look into this a bit more & be sad or angry but do it anyways as another case of needless Rust propoganda… I see the MS GitHub issue about the situation for Nheko <github.com/Nheko-Reborn/nheko/> which points to this 3-year-old merge request to just f💀cking use OpenSSL/LibreSSL for crypto calls <gitlab.matrix.org/matrix-org/o>. That response is saying:

    > As we do not have much prior experience with OpenSSL, reviewing this code would require looking up the documentation for those functions to ensure that they are being called correctly, and that all the parameters are correct.

    So the folks building the chat encryption for Matrix protocol have no experience with OpenSSL? & instead of learning this ubiquitous, valuable cryptography tool to accept the MR (I still need to to be fair), they blame C/C++ & choose to ‘rewrite it in Rust’. This Rust ‘replacement’ is not a drop-in replacement & it seems the bindings are messed up or incomplete where the maker of Nheko is forking to fix the bindings. Am I missing something? WTF are these folks doing?

  47. It is no secret I dislike #Matrix. I need to find a client that doesn’t eat all my resources (meaning not Element). I want to try the TUI written in Go but it uses Olm. Olm is deprecated in Nixpkgs so I asked a colleague. He recommended #Nheko. I went to give it a spin… but alas it too uses Olm for double ratchet encryption. Okay… so is there an upstream fix in Olm or Nheko I could patch in? So I go to check out the Olm project to see what it says <gitlab.matrix.org/matrix-org/o>…

    > It is not written in memory-safe languages (C and C++11), resulting in several CVEs

    Oh, no. The trigger phrase “memory-safety”… I know I am going to look into this a bit more & be sad or angry but do it anyways as another case of needless Rust propoganda… I see the MS GitHub issue about the situation for Nheko <github.com/Nheko-Reborn/nheko/> which points to this 3-year-old merge request to just f💀cking use OpenSSL/LibreSSL for crypto calls <gitlab.matrix.org/matrix-org/o>. That response is saying:

    > As we do not have much prior experience with OpenSSL, reviewing this code would require looking up the documentation for those functions to ensure that they are being called correctly, and that all the parameters are correct.

    So the folks building the chat encryption for Matrix protocol have no experience with OpenSSL? & instead of learning this ubiquitous, valuable cryptography tool to accept the MR (I still need to to be fair), they blame C/C++ & choose to ‘rewrite it in Rust’. This Rust ‘replacement’ is not a drop-in replacement & it seems the bindings are messed up or incomplete where the maker of Nheko is forking to fix the bindings. Am I missing something? WTF are these folks doing?

  48. It is no secret I dislike #Matrix. I need to find a client that doesn’t eat all my resources (meaning not Element). I want to try the TUI written in Go but it uses Olm. Olm is deprecated in Nixpkgs so I asked a colleague. He recommended #Nheko. I went to give it a spin… but alas it too uses Olm for double ratchet encryption. Okay… so is there an upstream fix in Olm or Nheko I could patch in? So I go to check out the Olm project to see what it says <gitlab.matrix.org/matrix-org/o>…

    > It is not written in memory-safe languages (C and C++11), resulting in several CVEs

    Oh, no. The trigger phrase “memory-safety”… I know I am going to look into this a bit more & be sad or angry but do it anyways as another case of needless Rust propoganda… I see the MS GitHub issue about the situation for Nheko <github.com/Nheko-Reborn/nheko/> which points to this 3-year-old merge request to just f💀cking use OpenSSL/LibreSSL for crypto calls <gitlab.matrix.org/matrix-org/o>. That response is saying:

    > As we do not have much prior experience with OpenSSL, reviewing this code would require looking up the documentation for those functions to ensure that they are being called correctly, and that all the parameters are correct.

    So the folks building the chat encryption for Matrix protocol have no experience with OpenSSL? & instead of learning this ubiquitous, valuable cryptography tool to accept the MR (I still need to to be fair), they blame C/C++ & choose to ‘rewrite it in Rust’. This Rust ‘replacement’ is not a drop-in replacement & it seems the bindings are messed up or incomplete where the maker of Nheko is forking to fix the bindings. Am I missing something? WTF are these folks doing?

  49. It is no secret I dislike #Matrix. I need to find a client that doesn’t eat all my resources (meaning not Element). I want to try the TUI written in Go but it uses Olm. Olm is deprecated in Nixpkgs so I asked a colleague. He recommended #Nheko. I went to give it a spin… but alas it too uses Olm for double ratchet encryption. Okay… so is there an upstream fix in Olm or Nheko I could patch in? So I go to check out the Olm project to see what it says <gitlab.matrix.org/matrix-org/o>…

    > It is not written in memory-safe languages (C and C++11), resulting in several CVEs

    Oh, no. The trigger phrase “memory-safety”… I know I am going to look into this a bit more & be sad or angry but do it anyways as another case of needless Rust propoganda… I see the MS GitHub issue about the situation for Nheko <github.com/Nheko-Reborn/nheko/> which points to this 3-year-old merge request to just f💀cking use OpenSSL/LibreSSL for crypto calls <gitlab.matrix.org/matrix-org/o>. That response is saying:

    > As we do not have much prior experience with OpenSSL, reviewing this code would require looking up the documentation for those functions to ensure that they are being called correctly, and that all the parameters are correct.

    So the folks building the chat encryption for Matrix protocol have no experience with OpenSSL? & instead of learning this ubiquitous, valuable cryptography tool to accept the MR (I still need to to be fair), they blame C/C++ & choose to ‘rewrite it in Rust’. This Rust ‘replacement’ is not a drop-in replacement & it seems the bindings are messed up or incomplete where the maker of Nheko is forking to fix the bindings. Am I missing something? WTF are these folks doing?

  50. To offset more negative emotions in my recent toots, I have to say that @kde @neochat (apps.kde.org/neochat/) has become a really excellent #Matrix client. It didn't have E2EE support the last time I tried it, but it works perfectly now, surpassing #Nheko, my previous favorite.

    I do like #FluffyChat as well, but the UI scaling just doesn't look quite right on my monitor. Oh, and of course, give me real menubars and scrollbars, brah. XD