Your friendly neighbourhood sh.it.head
Gamer, book and photography nerd, francophile // Gamer, geek des livres et de la photographie, francophile
Some older consoles have very negligible size libraries in modern day terms, and who knows what sources of ROMs will be taken down by lawsuits in the next few decades. I feel like there is some sense in making a complete archive of a systems game library, but for my personal use I usually just download / dump / rip what I need specifically.
Whatever file format I use them in is also how I back them up, I backup my entire desktop's and laptop's data to an external hard drive and an online service provider. I'm sure a compressed format would be more space efficient but that would take much more time given my use case.
In the case of my laptop it runs Linux and the filesystem I use supports "transparent compression" (almost all contents of the drive are compressed with zstd), so I'm guessing any of the ROMs on there will have already been compressed as nuch as they can (but I'm not knowledgeable enough on the file format specs)
The foundation supports a bunch of other open source projects, after all there is a lot more to devices that run the Linux kernel then just the kernel.
Also, I found it a but funny that the foundation created the PDF using Adobe InDesign 19.4 (Windows), according to the metadata in file posted on their website. (original | archive of the PDF)
You and someone else have mentioned the deadman switch, does the other person need an account or can credentials be made for them? I haven't used bitwarden in a while (since I migrated to gopass and then to keepass), so I'm guessing this is a new feature.
That is a very fascinating feature and I think I'll look into it!
What exactly is the deadman setup? I did a quick search and found someone asking for a feature from last pass. Is this what you're referring to?
I've debated on using a bank safe but I'm still unsure about the regulations in my country regarding them. Notably what can law enforcement do without a warrant etc etc.
In terms of self hosting I think that'll likely be the route I go as well, where family can just "shut it down" upon my death. I'm sure my partner might want to keep a few things (e.g. my kodi setup) but the things they would want to keep aren't too difficult I feel.
I mostly play rogue likes with controller and would like a XBox/Playstation style controller
I'm assuming you dont need gyro or touchpad that you'll get with PlayStation / Nintendo compatible controllers, however if you do want those features the Switch Pro controller & the DualSense (PS5) play nicely on my Linux computer (with steam)
Out of the two I'd probably recommend the dual sense since you're used to Xbox / Western PS layout rather then Nintendo / Japanese PS layout.
I've heard good things about the 8bitdo controllers, but can't comment on their compatibility or quality. The contemporary xbox wireless controllers I don't personally like, the current ones have this extra grippy texture on the back and thumbsticks that doesn't sit well with me and the lack of rechargeability ootb is disappointing for the price.
I have a few shortlisted
My parent's 2010 Ram 1500, the interior is rather comfy but the reliability is just not there. At 100k km the engine blew up, apparently this is still an issue with the current ones as the 5.7L V8 still has the same flaw allowing for some components to drop into the cylinder. There's also been random electrical components that have died relatively fast, and whatever metal was used rusted exponentially even with rust proofing being applied twice a year. It had more rust than their 2011 Toyota Highlander that had greater than 300k km
I also just hated when I had to drive it downtown, but I can't exactly blame the vehicle for that.
2011 Toyota highlander, it went through 3 transmissions, 5 rear wiper motors, and it was about to go on to its 4th transmission when they sold it. The 3rd one didn't even last much more than a year.
2006 Rav 4 (V6), this car also went through 2 transmissions, and then had to have the entire steering column replaced by year 2
~2016 Ford Fusion, this was a rental car for when my Civic was being repaired after an accident and my god was it awful. It handled like a massive boat despite being a medium sized car and the transmission felt significantly less responsive than even the CVT in the honda. The seats also sucked but i think that was how the rental company cleaned them, they made this awful noise every time you sat in them and looked and felt like a "casting couch" with several generations of children dried up in them...
Honorary Mention: my friends Nissan Versa, seemingly unreliable and falling apart but it refuses to ever give up. That thing will survive nuclear winter, and will remind you with every pothole that its existence is torture.
The plugin that brings the "starter" / "welcome" screen when
nvimis called without a file ismini.starter, a lua module of theminiplugin. My primary use case for neovim is closer to a feature complete text editor rather than a full fledged IDE, although there definitely is some overlap in my setup.My set of plugins are roughly as follows
vim-plug, I will likely replace this one withpackerat some pointgoyo.vimandlimelight.vimfor distraction free viewing and editingnnn.nvimto integrate thennnfile manager into neovimmini.nvimaccording to the Github, "Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort. They all share same configuration approaches and general design principles."mini.surroundfeature rich surround actionsmini.statuslinea very simple no-frills statuslinemini.starteraformentioned start screenmini.pairsinserts the paired character, e.g typing(will automatically place)behind the cursorsmini.movemove selectionsmini.maphas a little map of the file similar to VScode among many other IDEs & text editors
barbar.nvimTabbar plugin- a whole bunch of LSP / autocomplete engines / snippets / git commit messages & signs
nvim-treesitterfor syntax highlighting
And the remaining things in my
init.luafile are just keybindings, setting up the plugins, and disabling the swapfile etc. when editing my password secrets ingopassamong other 'secret' filesIt definitely is rather reminiscent of older Windows versions with the seperate application launchers, fully expanded task bar entries that show the name of an app that are ungrouped (until necessary). And the widgets are very reminiscent of Rainmeter.
But I also bring some things from macOS that I enjoyed such as the global menu on the top (sadly Firefox flatpak does not support), virtual desktops with the pager widget on the bottom, and I use Krunner a lot (plasma's equivalent to macOS "Spotlight")
I hope your switch to Linux goes well if / when you switch!
I understand why they wouldn’t want to suddenly change the branding of existing projects though.
I'm not sure if I agree, I feel like the long term damage of keeping the names is greater than changing them now to Fedora Plasma Atomic (Formerly Kinoite) / Fedora Atomic Workstation (Formerly Silverblue). Leaving them as is, is just going to create more confusion in the future to new users who won't immediately understand why the naming convention is different for the other spins and will create more confusion for documentation / support threads online.
I feel that I am 50:50 on it, immutable at least conveyed more information about what it is while Atomic feels a lot more "buzz-word-y" and does not convey as well what it means. Regardless, I'd say the bigger issue is keeping the old Silverblue & Kinoite names, they really should change them even if it means having a ~2 year period of having "Formerly Silverblue / Kinoite".
Thank you for the very thorough reply! For god knows what reason I get this error:
error: app/org.mozilla.firefox/x86_64/stable not installedwhen running the xdg-open firefox-reader command, yet manually runningflatpak run --user org.mozilla.firefox about:reader?url=https://example.comworks just fine. I'll have to troubleshoot it when I have a bit more time ;pThanks again for your very thorough write up and the linked articles. Have a good day :)
Update: It seems like on my system, the
--userflag was the issue, removing it made the script function. I am using Fedora Kinoite (Immutable version of KDE Plasma), so perhaps it is just a difference in how flatpak is configured between distros? I'll have to read into it more later.I'll keep my answer focused on KDE Connect as I no longer use a TWM. You can most definitely use KDE Connect in non-Plasma environments. For non-Plasma (and non-Gnome * ) environments you can just install the
kdeconnectdpackage. Then, to start the KDE Connect daemon manually, execute /usr/lib/kdeconnectd. You can schedule this to autostart as a systemd unit, or in the config for your TWM (I know in sway/i3 you could start it, I'm assuming it is similar for many other options)If you use a firewall, you need to open UDP and TCP ports 1714 through 1764. If you use
firewalldspecifically, there's an option to enable KDE Connect rather than manually specifying it. This also let's you have it only work on private networks and not public if you so chose.See Arch wiki for more details
*For gnome I would recommend using gs-connect even if you have a tiling extension
£ KDE-Connect: does that work on TWMs? Is there a good implementation? Can I use GSConnect elsewhere too?
You have a few options on what you can do to limit your child's usage of a device.
NextDNS has some interesting features for parental controls, as well as some options to try and prevent bypassing it (i have yet to try it though). On iOS it can be installed as a device profile and you can prevent them from being uninstalled, I'm not sure how to go about this on android but I'm sure there's a way of limiting the child's access to changing the settings.
Otherwise the built in parental control features on Android and iOS seem to be very useful as well, since you can limit what your child can install, set screen time limits, etc. I am pretty sure you'd want a more recent version of Android however to get all of the features here which may not be possible depending on the budget.
If you just want the ability to call / text then perhaps a dumb phone is a good first step? But a smart phone may be more useful if they're older.