Don’t forget to add padding, so I’d just round it out to 18 months to be safe.
Thanks man. This is likely going to be too much for me, but I really appreciate you providing it. Taking a look :)
edit: Actually, I think I get it after looking at the nix.sh that’s the actual list of commands. Thanks! Seeing if I can tweak things so I can make my own version. Cheers!
This is great!
@tripflag@lemmy.world If you don’t mind, what tools did you use to create this html? Have a cheatsheet.txt that I often share with devs on my team and I’d love to format it into something like this with a TOC, display name for a command, and links down to each oneliner.
I’d recommend Fedora KDE. Keep it simple. Good community, support, stable.
Surprised I don’t see any Fedoras on here yet. Very happy on Fedora KDE.
Why did they say if like it was a bad thing? I want this to be a thing.
This was before my political consciousness, but I feel like 1992 has an argument, but maybe that was just because of Perot…
I really doubt this is the primary reason. I think it was multifaceted, but really the people in the business of designing phones were already using Bluetooth exclusively and felt that it was good enough. Some designs probably rushed it as a means to sell more premium headsets (Apple, Samsung), other saw it as removing an unnecessary redundant feature that was more prone to breakage and a waterproofing difficulty (Google). I think it really just came down to the personal preferences of the (affluent) people who were doing the designing, not necessarily a purposeful cash grab. It really was not great since wired headphones were way cheaper than their Bluetooth counterparts. Luckily Bluetooth has gotten much better and less expensive. I think there should be options for both.
Exactly. This is about protecting themselves from legal liability, not anything else. As the guy who hosts it is just a regular guy, not a corporation with limited liability/tons of startup dollarbucks, I don’t begrudge him/them at all.
I want a tool that can do the same thing for whole communities. Seems like there might be a day where communities would like to migrate for one reason or another. While you could simply stand up a new community on the new instance and then attempt to get everyone to move over, that’s bound to fail if the community is large enough. It would be cool if subscribership would also be able to be moved in the back-end.