[-] Quibblekrust@thelemmy.club 1 points 1 hour ago

Not me. I switched to using hydrogen decades ago.

[-] Quibblekrust@thelemmy.club 4 points 1 hour ago

This is all wrong! You can't just connect the batteries like in the photo. You have to put the batteries on rose quartz! You will hear an amazing improvement! It is not good to put them next to each other, they must be in contact with the crystal!

SpoilerContent stolen from a totally serious comment on the blog post.

[-] Quibblekrust@thelemmy.club 5 points 3 days ago

We only know what we can measure. We don't really know what an atomic nucleus looks like, for example. We can only measure what happens when another particle hits it. Between measurements, it might not even be real. We don't even know what measurement is.

Pick your favorite quantum interpretation: Copenhagen, Broglie–Bohm, Many Worlds. We'll probably never know the truth.

[-] Quibblekrust@thelemmy.club 10 points 3 days ago

Lack of space was Fermat's excuse for not proving his last theorem.

[-] Quibblekrust@thelemmy.club 11 points 5 days ago

I would argue it's still mysterious. If it were simple, we wouldn't have what's called the measurement problem.

Also, there is more than one way to measure something, and not all of them require a real photon to hit some particle. In the Elitzur–Vaidman bomb tester, you can "measure" whether the quantum bomb's sensor is working or not without actually hitting it with a photon. Instead, you hit it with the "chance" of a photon hitting it, and that's good enough. (It'll still blow up half of the time, but you can design the tester with multiple recursive tiers to increase your tested-but-unexploded bomb yield to arbitrarily close to 100%.)

That's pretty mysterious in my mind.

[-] Quibblekrust@thelemmy.club 4 points 6 days ago

In a folder called javpy, of course!

78
submitted 1 month ago* (last edited 1 month ago) by Quibblekrust@thelemmy.club to c/programmer_humor@programming.dev

By viewing this post you are infected, and all future clocks you attempt to make will fail to render, too.

1
submitted 2 months ago* (last edited 2 months ago) by Quibblekrust@thelemmy.club to c/thunder_app@lemmy.world

Update: It's worse than I thought. It's crashing my VPN! I use the Mullvad VPN app. After that crashes, Thunder crashes. This happens every time.


First, it slows way down and stutters a bit, then turns all black and crashes to my home screen.

Is this happening to anyone else?

Android 16. Pixel 7 Pro.

5

If not, can you please add a setting to disable it? It's just not for me. At best it's a distraction while I wait for the image to load. At worst, it blocks part of the image.

[-] Quibblekrust@thelemmy.club 56 points 2 months ago

Umm... That's just alphabetical.

1
2

I woke up one day and Fennec wouldn't browse any web page. Like, if I do a search, which goes to DuckDuckGo, I get a loading bar that never goes anywhere. (See screenshot).

If I disable all of my extensions, it'll work again. Then, if I enable them one by one to try to find the culprit that was making Fennec not work, it doesn't break! Until it does, randomly. I basically can't easily reproduce it working or not working.

I switched to IronFox, and installed all the same extensions, and have had no problems for two days.

Extensions:

  • JShelter
  • UBlock Origin
  • Decentraleyes
  • Cookie AutoDelete
  • Absolute Enable Right Click & Copy
27
submitted 3 months ago* (last edited 3 months ago) by Quibblekrust@thelemmy.club to c/linux@lemmy.ml

Update #1

I fixed my boot issue, but now I have to fix the issue with snapper not working right.

The boot issue: Something—I don't know what—added a removable drive to fstab, and the error was that drive couldn't be mounted at boot. I have two guesses:

  1. I formatted a microSD card using YaST Paritioner sometime before doing the distro upgrade.
  2. The drive might have been mounted during the distro upgrade, though I don't think it was.

At any rate, I commented out that line in fstab and it booted right up.

Mullvad is working fine when I boot normally. I guess it was only broken when booting a snapshot from before I upgraded it.

Update #2

I also fixed /.snapshots by adding it to fstab. Now it gets mounted on every boot, and this version of fstab will be in all future snapshots. I just took a manual snapshot for good measure.


I don't know which action caused the issue, so I'm going to list everything I did. I'm new to OpenSUSE Tumbleweed, and I haven't used Linux since like Linux Mint 17.

  1. I disabled KWallet because I got tired of typing in a password every time my desktop launched just for wifi passwords. I decided to just let Linux store them in plain text since my whole system is encrypted with LUKS.
  2. I did a distro update. (zypper dup) After that succeeded, I logged off and back on.
  3. I noticed Mullvad had a new version. They don't officially support OpenSUSE, so I downloaded the new RPM. I ran rpm -e mullvad-vpn to remove the old one. That might have been a mistake since my notes say I used zypper to install it the first time. I installed the new one with zypper. It launched and connected just fine.
  4. I had some trouble getting network settings to store/retrieve my wifi password, so I decided to reboot my system since I changed so much stuff.
  5. It wouldn't boot. I see a few "BIOS" and "ACPI" errors.
  6. Time to try out Snapper! I reboot and choose the most recent snapshot from before tonight.
  7. It boots, but when I try snapper rollback I get IO error (.snapshots is not a btrfs subvolume)
  8. I get the same error trying to open the YaST snapshot viewer.
  9. I check btrfs, and I see @/.snapshots plus a bunch of numbered snapshots, of course.
  10. I check fstab, but I don't see an entry mounting anything on /.snapshots.
  11. I do see a directory at /.snapshots, but it appears just be an empty directory.

Mullvad seems broken with this snapshot. I can't connect to the internet. The mullvad-daemon won't start, so I think the killswitch is active. I've had to type all this on my phone.

What can I do to fix this? I just want to rollback to this good snapshot, and then I can worry about fixing Mullvad when the filesystem isn't read-only.

One month. That's how long it took me to break my system. ☹️

7

I've had three comments in my inbox for about a week and every day I try to mark them as read, but it doesn't work. They disappear from the list at first, but then when I refresh they're still there. I get the error in the picture which says, LemmyApiException: couldnt_find_comment_reply

I just went to the website and logged into my instance, and I had no problem marking the comments read from there. They disappeared from my Thunder inbox, too, after a refresh.

I saved one of the comments for debugging purposes, in case there's something we can look at.

[-] Quibblekrust@thelemmy.club 27 points 4 months ago

He invented JavaScript, so definitely don't use that either. For real. JavaScript sucks.

[-] Quibblekrust@thelemmy.club 55 points 4 months ago

I am so grateful for this post! You always post such interesting content. 🦐⛹️‍♂️📷

[-] Quibblekrust@thelemmy.club 32 points 5 months ago

Nature's Pop-Rocks

[-] Quibblekrust@thelemmy.club 42 points 7 months ago* (last edited 7 months ago)

I highly doubt it was the code. They probably reduced texture and background fidelity and compressed the cutscenes heavily. It's simply impossible to reduce a codebase by 91% and have it still be recognizable. However, the N64 had better hardware and it's possible that some code could be eliminated because the chips had features that made them code not needed. But not nearly 686 MB worth.

view more: next ›

Quibblekrust

joined 10 months ago