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

help-circle


  • Currently kinda controversial, but currently it’s still Fedora, the xfce4 version.

    I had Debian for some time before, but had my apt packages messed up a couple of times to the point I had to entirely re-install. In stable, I was missing sufficiently recent versions, in testing I had other problems.

    With Fedora dnf I had less problems recovering, usually more recent versions.

    Xfce4 is just more suitable for my needs than Gnome.












  • They are trained to give answers which sound convincing on a first glance, for simple questions in most fields that strongly correlates with the correct answer. So, asking something simple on a topic I have no clue has a high likelihood to yield the answer I’m looking for.

    The problem is, if I have no clue, the only way to know if I exceeded the “really simple” ralm is by trying the answer and failing, because chatgpt has no concept of verifying it’s own answers or identifying its own limitations, or even to “learn” from it’s mistakes, as such.

    I do know some very similar humans, though: Very assertive, selling guesses and opinions as facts, overestimating themselves, never backing down. ChatGPT might replace tech-CEOs or politicians 😁





  • By which component is the password truncated on account-creation? Imo, the web UI shouldn’t do that without at least warning the user. Such long passwords might be a corner-case, but if the UI changes the password in any way before submitting it to the server, I think the user should see a big fat red notification. What if an account was created using a different client? The user wouldn’t be able to log in using the web-ui because the web-ui refuses to send the unmodified password?

    If the password is truncated server-side during account creation, the server should do the same during login, the UI or client wouldn’t even have to know about it.