Пропустить навигацию
Hopefully this helps.
0:00 / 0:41

Hopefully this helps.

Shayan

@ImSh4yy66 тыс. подписчиков

Открыть в X
11 616 отметок «Нравится»СкачатьОригинальный пост

1 371 122 просмотра

Hopefully this helps.

38 комментариев

Комментарии из оригинального поста в X (Twitter)

  • Фото профиля Punished Harold

    @cananadad

    Sigh, obviously you make the password unique, and put a helpful error message saying that the password was already taken by "%username%".

    1 035 отметок «Нравится»

  • Фото профиля Khalid Warsame

    @KhalidWarsa

    Vibe coders:

    594 отметки «Нравится»

  • Фото профиля Peterino2

    @petey_fo_really

    whats so funny is if enough of this shitposting happens the chances of llms generating code like this goes up lmao

    273 отметки «Нравится»

  • Фото профиля Shayan

    @ImSh4yy

    Follow me for more database tips.

    244 отметки «Нравится»

  • Фото профиля Sassy Batman

    @samuelralak

    This is genius. Also storing passwords in plain text - major security improvement. Hackers expect encrypted+salted passwords so this will throw them off completely

    94 отметки «Нравится»

  • Фото профиля BestCodes

    @the_best_codes

    These are hashed in your real implementation, right 😳

    89 отметок «Нравится»

  • Фото профиля Un Programador

    @ProgramadorVzla

    I spend 2min of pure laughing. Thank you

    71 отметка «Нравится»

  • Фото профиля Shayan

    @ImSh4yy

    not sure what's funny here?

    20 отметок «Нравится»

  • Фото профиля Un Programador

    @ProgramadorVzla

    The pointer of course

    11 отметок «Нравится»

  • Фото профиля Russell Polo

    @RussellPolo

    You could save bandwidth by giving the user the id of their password: Instead of the password you provided, just use the ID '2'. Doing so will reduce bandwidth needs and save the environment.

    63 отметки «Нравится»

  • Фото профиля 🟣 Gato

    @GatoGodMode

    Using the same password in reference for multiple accounts and exploiting it yourself? Not at all. Even suggesting that one password could belong to multiple accounts is awful. 100gb to 3gb downsize is cool and all, but I can just steal data even faster now and furthermore, if any two or more users share the same password instinctively, chances are those same people don't change their passwords at all, which further subjects those people to more data risk. I'll take the bigger DB in this situation. Imagine the dictionary bruteforce efficiency on this. It would be devastating.

    61 отметка «Нравится»

  • Фото профиля INIYSA

    @lafaiel

    Thanks, it really helped me optimize the server running on my e-cig's cortex-m0 processor!

    55 отметок «Нравится»

  • Фото профиля Juan Henriquez

    @juanhenriqz

    Imagine @aarondfrancis using a Mickey Mouse pointer like for his db courses 😂

    37 отметок «Нравится»

  • Фото профиля Shayan

    @ImSh4yy

    @aarondfrancis he got a few things to learn from me.

    20 отметок «Нравится»

  • Фото профиля Njaū

    @godfrey_njau

    I thought the joke was the tiny hand until I saw some taking the advice seriously

    30 отметок «Нравится»

  • Фото профиля Giuseppe Gangi

    @ggangix

    that way the password can be a select and not a text input. Smart 🤓

    26 отметок «Нравится»

  • Фото профиля Elmo

    @aggressa

    You have separate users? Just log them all in to the same account. They won’t notice.

    19 отметок «Нравится»

  • Фото профиля Shaun Thomas

    @BonesMoses

    Don't forget to add a public REST API to interact with the tables for even better efficiency!

    14 отметок «Нравится»

  • Фото профиля lucid

    @lucid_bound

    like I said

    13 отметок «Нравится»

  • Фото профиля Simao Soares 🇪🇺🇵🇹🇳🇱

    @simao_msoares

    The small hand is too distracting, Explain like I'm 80 and worked at the circus for 72 years.

    12 отметок «Нравится»