• 0 Posts
  • 387 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle

  • Been using Nix for just over a year.

    Seconding to go with flakes. No idea wtf channels are or whatever the previous system was.

    Documentation can be confusing due to changes in paradigms. The bare “nix <scope>” seems to be the most modern oppose to “nix-<scope>” (e.g., nix store vs nix-store). That said, not every feature can be found in the newer variants.

    This can make following tutorials difficult if they aren’t using the same paradigm.

    Getting comfortable with the nix language will be helpful. Its a functional programming language, which is very different than languages like bash.

    Not everything has to be done the nix-way. My nvim files are in the same repo, but I just outOfStoreSymlink them instead of wrapping them in a derivation.

    Some useful packages I like not already shared.

    Disk partitioning: https://github.com/nix-community/disko

    Immutable: https://github.com/nix-community/impermanence - Pretty much resets the system to a new install every boot. Discourages manual tweaks via sudo as they get wiped out. You can still mark certain directories to be persistent (logs, personal documents, steam games, etc.).

    Nvfetcher: https://github.com/berberman/nvfetcher - Nix has a concept of overlays. You can pretty much override anything with .override (module args or inputs) and .overrideAttrs (module attribute set or outputs). Nvfetcher helps with checking different sources so you can override a packages src attribute. Why is this useful? So you can install any version you want and are not bound to nixpkgs. That doesn’t mean the install script in nixpkgs will always work on newer versions, but those can be overridden as well if needed.

    Note that disko, impermanence, and nvfetcher all have a flake.nix in the root of the repo. Those provide ready to go overlays so you don’t have to deal with writing your own which is really nice if you want to latest version without much work when available.



  • Toooo real. Its like companies have taken the worst of everything and just call it agile. List out every task and estimate them so we have timelines, but don’t actually architect anything as that’s waterfall. Fake waterfall, with fake dates, but fingers will be pointed like they were real commitments, and spend a month doing it for this executive power point instead of fucking off so devs can build the damn thing.









  • If half your employees aren’t acting the way they do in private, they’re putting on a mask and not being their true selves

    But you’re making this point in defense of someone aligning themselves with a group who targets trans, women, and whoever else they can bully not like them for being their true selves… Do you not see the hypocrisy of such a point given the context of the quote?


  • Major desktop environments are KDE as you mentioned and Gnome.

    Arch wiki is a good resource even if not running arch. You may want to look into their dotfiles page to back up your settings: https://wiki.archlinux.org/title/Dotfiles.

    NixOS ended up being my distro of choice for reproducible installs but it has a high learning curve and poor documentation so I wouldn’t recommend to start with. That said you can still use Nix on other distros with home manager to manage dotfiles and install non-system apps.

    Distros just pick the default things to install. You can always use the package manager to install something else like a better file manager.

    A lot of choices are simply subjective so its hard to recommend any one distro. Mint is close to windows, based on Ubuntu and uses Gnome. Ubuntu based on Debian I find to be user friendly. Not used a Fedora based distro in ages but there is also Silverblue I’ve heard mentioned positively.

    Distros like Arch and NixOS are more design your own system setups. Pick what you want. I used arch for a bit, but got annoyed at keeping all my systems in sync. Had a huge wiki of all the tweaks I made. Then scripts to automate some of it. I started looking at automation tooling like ansible when I found nix.





  • You probably don’t want the entire terminal rendered in your UI for the reason you gave that it is intended for monospace.

    Rather, you want the buffer which is markdown and contextual info like cursor position.

    You might hit some challenges like how to handle style elements. For example:

    <cursor>*bold*
    

    Moving the cursor to the right of the b will take two key presses in nvim but would typically be one key press in a WYSIWYG editor.

    There are probably many ways to handle this in nvim through the plugin system, but both paths of embedding vs emulating nvim has a good chunk of dev work to be completed.

    Emulating will likely be more rewarding at the start as you can get incremental improvements pretty quickly.

    Embedding is a cool idea, but likely a ton of upfront work to get your first tangible results.

    You might be interested in reviewing https://github.com/MeanderingProgrammer/render-markdown.nvim which attempts to render Markdown in the terminal. They have logic for rendering things like the bold example in bold while hiding the markup.

    I personally just use https://github.com/iamcco/markdown-preview.nvim to render in a different window when render-markdown.nvim isn’t enough.


  • Ultimately we don’t know the implementation. I’ve seen some bad sites like stealth truncating on the registration form but leaving the login form unbounded so the password you pasted in both times doesn’t work.

    Separate issue from truncating, I get suspicious when I see passwords capped to 16-20 chars for the reason you gave that they should be stored as fixed length hashes.



  • sloppy_diffuser@sh.itjust.workstoCybersecurity - Memes@lemmy.worldI hate passwords
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Also suggests the user may be reusing the same prefix if only the changed bits are getting truncated.

    Should use different random passwords every time. Completely random or a random string of words. While it doesn’t solve the cleartext password storage issue, a data breach won’t compromise all your other accounts to same degree.

    Doesn’t hurt to also randomize usernames, emails, and even security question answers.

    edit: or my new favorite passkeys, just make sure you trust whatever tool is managing your private keys.