The S&P500 is almost always at an ATH, for the record. Buy as soon as you have the money and buy often. The market is irrational, and doesn't always reflect reality. Efficient market hypothesis says that all this "scary risk" is already "priced-in" instantly. If there's money to be made off this uncertainty, it's been made. Anything else is just gambling.

This sort of stuff is scariest when you're just getting started, but remember that you're probably looking at a multi-decade timespan. It doesn't matter what happens next week in the grand scheme of things.

Kind of surprising to take away the control of DXVK/VKD3D/NVAPI like that. Keeping NVAPI enabled has caused me trouble on certain games before. Now to disable them we need to type in Proton's environment variables I guess? I hope they at least put in UI toggles for Proton's configurations instead.

He’s probably overly defensive and paranoid and interprets some forms of criticism as attacks.

I think this was also a result of his “miscommunication” in the past

there might also be parties involved who are ACTUALLY interested in attacking GrapheneOS and weakening its popularity, for their own gains.

when your successful and also high-quality project is under regular attacks from various angles

Rossman’s over-dramatic nature and high reach

then communication spirals out of control into various escalations

You should actually look at any of the copious amounts of evidence that involve this conversation instead of just imagining what it might look like. There's really not much else to talk about until you do. Daniel has given us zero evidence to support his side, while in contrast there's a mountain of evidence against him.

I know this is a Louis Rossman thread but calling Daniel Micay "a bit socially awkward" is minimizing the issue to an extreme. Louis Rossman made his comments after he watched Techlore's in-depth video documenting Daniel's behavior, but keep in mind that even that hour-long video is just scratching the surface. To this day, Daniel continues to act the same way if not worse, and has a giant list of "enemies" that he says are attacking, harassing, bullying, and gangstalking the "grapheneOS project" (aka him). This might be partially caused by him bashing other open source projects and making new enemies any chance he gets. I'm not sure when the "all open source projects get together to personally target Daniel Micay" meetings occur, but maybe the only common thread is Daniel himself. There are tons and tons of receipts out there on the web if you search for "Daniel Micay list of enemies", especially on a site that I don't feel comfortable promoting but which does a very good job of keeping track of this stuff - especially because Daniel always deletes everything incriminating afterwards. If you're going to catch him in the act you need to take screenshots and make archive.org snapshots.

Daniel's behavior is a very important issue to be aware of if you're considering using grapheneOS, and personally it crosses the line of what I feel comfortable with in regards to running his operating system on the most personal device I have. Louis Rossman was even more justified in his decision to do the same, since Daniel is (to this day) specifically targeting him.

This is probably the intended point of the comic but I do appreciate that they are depicted as completely equal in the last panel, instead of any pretense that there's still an imbalance between them. The whole "that person is better than me" anxiety can be hard to break through.

Do you have more info on how you tested Rimworld's simulation speed, or maybe a source that has tested this? I always used the native linux Rimworld version when I was playing because I assumed it would be better for simulation lag.

Solid video, and it comes from a pretty grounded viewpoint. It's not very techy or pros/cons-focused; it's more about the "spirituality" of what we're even doing with the technology in our lives. They're obviously not a tech expert, but their mindset and "breaking point" are a lot more relatable for most casual people. This is the sort of realization that people are going to continue having as big tech encroaches further and further on their lives. E.g. their example of "it's not one big problem, it's many small problems that add up" with why it's so frustrating to use Windows, but then why people continue to use it.

It will take a "breaking point" and self-motivated change to critically evaluate the power that you're giving to corporations and decide that you're going to accept some discomfort in order to fix it. There will never be a perfect time to effortlessly switch your entire workflow across operating systems. I daresay that if there ever was a point at which switching to Linux was effortless, big tech would flash something new and shiny and make that no longer the case. They prey on keeping people in the path of least resistance, and understanding their strategy is the first step to doing something about it.

Wish people would have realized this a couple decades ago, but it really does feel like Linux is re-entering public discourse as people are getting more and more jaded about their relationship with big tech companies.

Their prices lately have been very unimpressive.

Maybe HDR on linux? I'm fairly clueless about how it all works under the hood, but I'm currently on debian 12 and I'm hoping that by the time 13 comes around it will just work without me needing to do any manual system tweaks. As I understand it, it's currently semi-working or fully-working in KDE6, but I'm still on KDE5 until debian 13 comes out.

Rutracker is pretty solid for a public tracker. They've notably got a ton of music rips mirrored from what.cd and RED, and they seem to have a good handle on gaming releases as well. Their uploaders seem to focus at least a little on making releases well-annotated and a custom/high quality experience rather than just mindless scene content dumping. Use an adblocker and page translator and you should be good to go.

I don't think 'cattle not pets' is all that corporate, especially w/r/t death of the author. For me, it's more about making sure that failure modes have (rehearsed) plans of action, and being cognizant of any manual/unreplicable "hand-feeding" that you're doing. Random and unexpected hardware death should be part of your system's lifecycle, and not something to spend time worrying about. This is also basically how ZFS was designed from a core level, with its immense distrust for hardware allowing you to connect whatever junky parts you want and letting ZFS catch drives that are lying/dying. In the original example, uptime seems to be an emphasized tenet, but I don't think it's the most important part.

RE replacements on scheduled time, that might be true for RAIDZ1, but IMO a big selling point of RAIDZ2 is that you're not in a huge rush to get resilvering done. I keep a cold drive around anyway.

"Cattle not pets" in this instance means you have a specific plan for the random death of a HDD (which RAIDZ2 basically already handles), and because of that you can work your HDDs until they are completely dead. If your NAS is a "pet" then your strategy is more along the lines of taking extra-good care of your system (e.g. rotating HDDs out when you think they're getting too old, not putting too much stress on them) and praying that nothing unexpected happens. I'd argue it's not really "okay" to have pets just because you're in a homelab, as you don't really have to put too much effort into changing your setup to be more cynical instead of optimistic, and it can even save you money since you don't need to worry about keeping things fresh and new.

"In the old way of doing things, we treat our servers like pets, for example Bob the mail server. If Bob goes down, it’s all hands on deck. The CEO can’t get his email and it’s the end of the world. In the new way, servers are numbered, like cattle in a herd. For example, www001 to www100. When one server goes down, it’s taken out back, shot, and replaced on the line."

~from https://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle/

Oh wow, that is horrible. I know people that talk exactly like that w/r/t wanting to "further their career" etc, but I guess the "announcement" part at the end doesn't make as much sense in that context.

I think it's hard to dig yourself out of this hole unless you've got early retirement on the horizon. The more you work, the less of an outside life you have, and the less you feel compelled to focus on anything but work, rinse and repeat. Your friend probably doesn't have anything to look forward to IRL, so might as well make more money.

Can't believe it's someone's job to make this list and this is what they came up with. A 14-year-old with internet access could name way more major players.

That's a new fear unlocked. I've been dragging my feet on getting into VR and this might have shifted my timeline by another year.

Maybe tangential but this reminded me of how much I hate setting up systemd timers/services. I refuse to accept that creating two files in two different directories and searching online for the default timer and service templates is an okay workflow over simply throwing a cron expression next to the command you want to run and being done with it. Is there really no way we can have a crontab-equivalent that virtually converts into a systemd backend when you don't need the extra power? I feel like an old person that can't accept change but it's been a decade and I'm still angry.

You might be able to read Arches faster.

I think it is dependent on it. The only option for connecting to mollysocket is now QR code, and QR code requires VAPID.

I just did this, and these were my rough steps:

1. Backup from Molly-UP
2. Write down the code
3. Install normal Molly from FDroid (you don't need to remove Molly-UP yet)
4. Open normal Molly and import the backup, log in to your account etc
5. In your mollysocket instance, run mollysocket vapid gen and use the key as MOLLY_VAPID_PRIVKEY environment variable in docker compose, or however you're running mollysocket.
6. Go to notifications and change the notification type to UnifiedPush, and scan the QR code from your mollysocket instance. (I was having trouble scanning the QR code when it's printed out via CLI, maybe because it was white on black, but the QR code from the web server page (port 8020) worked)
7. Uninstall regular Molly-UP when you're ready

No real trapdoors or anything; I spent the most time trying to get the QR code to scan before finally getting it to work via the web server page.