Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TH
Posts
13
Comments
271
Joined
2 yr. ago

  • While Reolink hardware is perfect for Blue Iris and other self-hosted solutions, I try to warn everyone that Reolink's own Android app now captures your device's clipboard whenever accessed. The same may be true for their desktop or iOS apps, I don't know.

    I have several Reolink cameras and I've been happy with their overall image quality and capabilities, but I do not trust their software whatsoever and recommend keeping them isolated from the internet entirely.

  • Good to know it's possible! I'm going to play around with the remote configs and see if I can accomplish the same for any future user accounts.

    I use flatpaks for almost everything now, but I admit I haven't spent much time on their backend management aside from flatseal.

  • Thanks for the link. I'll play around with the remotes and add some feedback to the ticket.

    If I can set the user remotes on behalf of other users in advance, that should suffice for now. Otherwise, if each user has to know how to add their own remote in order for it to take priority, that's a real pain point.

  • You're very welcome. For Markor, I wasn't a fan of the default viewer theme, which is how I view most notes when on mobile, so I made some tweaks to improve its appearance...below is a screenshot:

    If you want something similar, add the following under Settings > View mode:

    • Open existing files in view mode: on (this may be default)
    • Link color: #71aaff

    And replace the <style>...</style> block under the inject -> head pop-up with the following CSS:

     `
        
    <style> 
    html, body { 
      font-family: sans-serif-condensed;
      font-size: 110%;
      background: #0d1117; 
      color: #c9d1d9;
      margin: 0;
      padding: 0.5em;
    }
    
    a {
      color: 58a6ff;
      text-decoration: none;
    }
    
    h1, h2, h3, h4 {
      padding-bottom: 0.25em;
      border-bottom: 2px solid #222934;
    }
    
    hr {
      border: 2px solid #222934;
    }
    
    pre, code {
      color: #b5a5ee;
    }
    </style>
    `
      
  • I write nearly everything in markdown. Like you, I don't want databases, or other barriers that will complicate portability.

    I just use my text editor of choice, usually VSCodium or vim on the desktop, and Syncthing to keep the notes synced across all of our devices.

    On Android, I've been happily using the Markor markdown editor for years. I've tried several others but always return to its simplicity.

    All of the above editors support opening folders in a tree view, so you can easily keep your notes sorted under a traditional folder structure and find what you when you need it.

    Edit: Forgot to mention that Markor does have a dedicated to-do feature too, which also uses markdown.

  • We use markdown notes extensively. Everything is synced to our desktops and mobile devices with Syncthing. Markor editor for Android, and VSCodium/vim on the desktop. Works great for tech notes, medical info, shopping lists, recipes, etc.

  • Honestly, any enterprise OEM will be similar, such as Dell or Lenovo. Yes, their mainboards are proprietary, but you can easily source them from legitimate parts vendors. That's why there are so many refurbished Optiplexes and ThinkCentres on Amazon. They're trivial to repair and most don't even require tools.

    You cannot easily upgrade to a dedicated GPU unless replacing an existing unit, which is standard for laptops as well.

  • The deal breaker for me is that it seems the low-level component that would interface with the shells (presumably managing credentials in some way) is closed source and off-repo. That's a big red flag for me, no matter how benign the intention.

  • I appreciate the writeup and that you've taken the time to post about it here, however I am 100% leery of managing remote access or credentials using closed source software. I'll definitely keep an eye on the project, but it's a hard pass for me until the app is fully open source.

  • Simple SMS, obtained from F-Droid, is probably the best universal option until the Fossify project adds the fork to their suite (assuming they do).

    If you have the ability to toggle network access for your apps (GrapheneOS, etc.), Google Messages is a very solid SMS app that receives regular updates. I would normally only recommend FOSS apps, but many of those options are limited and/or dangerously outdated for SMS.

  • I too like to review changes between images, but I'm just as content to run rpm-ostree status and/or rpm-ostree db diff to see what exactly has changed.

    You should be forced to reboot though? And if you don’t want to reboot, can’t you just do an --apply-live?

    I'm hoping to eliminate the extra reboot each day that is usually necessary to activate the latest image. I know that a lot of this will depend on exactly when the image drops from the repos (versus when I shutdown a host), which is why I was looking for some general feedback from others who might have done the same thing...I didn't know if it'd be worthwhile in the long run, but I guess there's only one way to find out. As for the --apply-live, I use it on occasion but I don't want to rely on it for system updates (if that's even possible).

  • Thanks, yeah I've found a few articles already on running scripts at shutdown...something like this should do it (using Tony Walker's update script), though I've not tested it yet:

     
        
    /etc/systemd/system/silverblue-update-at-shutdown.service:
    
    [Unit]
    Description=Fedora Silverblue Update at Shutdown 
    ConditionPathExists=/run/ostree-booted
    DefaultDependencies=no
    Before=shutdown.target
    
    [Service]
    Type=oneshot
    ExecStart=/usr/local/bin/silverblue-update
    TimeoutStartSec=0
    
    [Install]
    WantedBy=shutdown.target
    
      
  • I haven't had time to check out the forks from Tibor's apps, but I recall there were issues with the original Simple Calendar Pro which is why I had settled on Etar at the time. I'll definitely keep an eye on Naveen's repos though.

  • I was an rxvt/urxvt fan for nearly 20 years, then Alacritty for a while. Nowadays, I just use gnome-terminal and I've been happy with it. Looking forward to trying Prompt though.

    5 days later: Prompt is the bee's knees! Highly recommend for anyone wanting a snappy, feature-rich GTK4 terminal, especially if you work with containers.

  • My vote is Fedora. It offers fresh yet stable packaging, and a polished experience that you can rely on. You can then use flatpaks for even newer apps, or opt to run Arch in a container with distrobox/toolbox and play with as many cutting edge apps as you want, all as if they were installed on the host.

    Finally, if you like what you see in Fedora, consider trying Fedora Silverblue, Kinoite, or any of their other immutable distros.