this post was submitted on 21 Jun 2023
54 points (100.0% liked)

Technology

39528 readers
340 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago
MODERATORS
 

This next version is quite important as it brings important fixes.

Bugs: https://enterprise.lemmy.ml/c/actualbugs018

cross-posted from: https://sh.itjust.works/post/300197

Enterprise: enterprise.lemmy.ml - Thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] Lionir@beehaw.org 12 points 2 years ago* (last edited 2 years ago) (9 children)

I notice a few UI-related things:

  • Keep getting "Deleted by creator" in the bottom left which I assume an unregistered user shouldn't see
  • Community names in the Communities list or on any page it seems are not center aligned like you might notice here (https://beehaw.org/communities)
  • Modlog only appears after a refresh on the page
  • Modlog filters are no longer side-by-side
  • It finally says that the Username is taken
  • It still lets you make a password longer than 60 characters (bad)
  • Posts no longer seem to be switched

(Still need to test pinned messages being moved when sorted by new) (I should post this in there, actually, I guess)

[–] dudeami0@lemmy.dudeami.win 10 points 2 years ago (7 children)

Is there a reason you consider passwords longer than 60 characters an issue, or does the backend reject such passwords? In my experience, there should be no upper bound on password length except maybe in the order of request size being too large (say a password that is a several kilobytes).

[–] livingcoder@lemmy.austinwadeheller.com 6 points 2 years ago (1 children)

Passwords "should" be hashed anyway, so I don't understand why there's a limit. Are they actually being stored as plaintext in a VARCHAR(60) column in the database? Please tell me that's not happening.

[–] rs5th@lemmy.scottlabs.io 6 points 2 years ago

Just checked my own Lemmy postgres database, it's a 12 round Bcrypt 2b hash.

load more comments (5 replies)
load more comments (6 replies)