• 2 Posts
  • 947 Comments
Joined 2 years ago
cake
Cake day: September 2nd, 2023

help-circle


  • It’s pronounced the same as a regular u. It is the same letter.

    They are weird rules, but in Spanish we have these rule:

    If a word has a “Q”, the next letter must always be a silent u. That is, you write a “U” but don’t pronounce it. And after that “U”, always comes a vowel.

    Similarly, if after a “G” comes a “E” or “I”, it is pronounced differently depending on if there is a silent “U” after the “G”.

    However, sometimes we want a non silent U after a Q or a G. In that case, we write “ü”.

    So u and ü are literally the same letter in spanish. We call the 2 dots “diéresis”, maybe it’s similar in German.


  • Dictionary attacks usually contain a dictionary of common passwords. To use a dictionary for this, you’d have to use a word dictionary instead of a password one. And then you’re back to combinatorics.

    4 words, where each word is in the dictionary: N^4. However the N here is way bigger than the amount of ASCII characters. Especially if each of the words may be of a different language. If N is larger than 16384, then it has more combinations than a random 8 ASCII character password. 16384 = sqrt(sqrt(128^8)). Quick Google search says English has more than 1 million words.

    Therefore even if you know that the user generated their password using this method and used a dictionary attack tailored for this method, it would still be harder to break than a random 8character password.



  • RAE about ñ:

    1. Decimoquinta letra del abecedario español. Su nombre es femenino: la eñe (pl. eñes). Representa el fonema consonántico nasal palatal /ñ/.

    2. Esta letra nació de la necesidad de representar un nuevo fonema, inexistente en latín. En cada una de las lenguas romances se fue fijando una grafía distinta para representarlo, como gn en italiano y francés, ny en catalán o nh en portugués. El castellano medieval escogió el dígrafo nn, que se solía representar abreviadamente mediante una sola n con una rayita más o menos ondulada encima; así surgió la ñ, adoptada también por el gallego y el vasco. Esa rayita ondulada se llama tilde, nombre dado también al acento gráfico (→ tilde1)

    EDIT: it is true that Spanish is not the only language so it shouldn’t be the one to decide if it is a letter or not. Since I only know 2 languages that used it, I checked the other one: basque.

    According to euskaltzaindia:

    ñ letra (eñe) ñ letra (eñe)

    Zenbait jendek uste du [ñ] hots bustia <in> bikotearen ondorio dela beti, eta ñ letrarik ez dela euskaraz. Ez da hala. Erreparatu adibide hauei: ñabardura, ñaka, ñañan egin, ñaño, ñimiño… hitzei; -ño atzizkiaz eraturikoei: andereño, haurño, xoriño, gazteño, maiteño…; mailegatuei: piñoi, txanpiñoi, erresiñol, giñol…; zenbait herri-izeni: Abadiño (abadiñar), Oñati (oñatiar), Armiñon (armiñondar), Iruñea, Urdiñarbe (urdiñarbetar)…; zenbait ponte-izeni: Eñaut, Beñat, Iñaki, Garbiñe, Eguzkiñe, Zuriñe… [EH; 17. araua] (→ letra; → kontsonante busti-palatalen grafia eta ahoskera)



  • Same thing with git.

    There is no shortage of git beginners that refuse to use a GUI.

    They ask for help for something, I haven’t used git CLI in years, so I tell them “go to this place and click those button”, then they open the vscode terminal and ask “but can I do it from CLI?” Okay then I go to search the command. Meanwhile I tell them to checkout a branch or something as basic as that and watch them struggle for way longer than it took me to find the command I was looking for.

    I get that thousands of elitists have convinced you that using git from a GUI is a sin. But it’s fine, I won’t tell no one. I use a GUI myself.









  • The C example is the wonderful happy path scenario that only manifests in dreams.

    Most projects don’t have a dependency list you can just install in a single apt command. Some of those dependencies might not be even available on your distro. Or there is only a non-compatible version available. Or you have to cast some incantation to make that dependency available.

    Then you have to set some random environment variables. And do a bunch of things that the maintainers see as obvious since they do it every day, so it’s barely documented.

    And once you have it installed, you go to run it but discover that the fantastic CLI arguments you found online that would do what you installed this program to do, are not available in your version since it’s too new and the entire CLI was reworked. And they removed the functionality you need since it was “bad practice and a messy way to do things”.

    All of this assuming the installation process is documented at all and it’s not a “just compile it, duh, you should know how to do it”.



  • Is there anything in the LLMs code preventing it from emitting copyrighted code? Nobody outside LLM companies know, but I’m willing to bet there isn’t.

    Therefore, LLMs DO emit copyrighted code. Due to them being trained on copyrighted code and the statistical nature of LLMs.

    Does the LLM tell its users that the code it outputted has copyright? I’m not aware of any instance of that happening. In fact, LLMs are probably programmed to not put a copyright header at the start of files, even if the code it “learnt” from had them. So in the literal sense, it is stripping the code of copyright notices.

    Does the justice system prosecute LLMs for outputting copyrighted code? No it doesn’t.

    I don’t know what definition you use for “strip X of copyright” but I’d say if you can copy something openly and nobody does anything against it, you are stripping it’s copyright.