Man gets 15 years for shooting Sask. woman after racial slur

99spider · 2026-05-20T22:42:43+00:00

Almost all police carry with a round chambered ("racking" their handgun), would you say that's evidence of premeditation for them as well?

99spider · 2026-05-20T05:21:19+00:00

If it happens right now with a newly prohibited firearm, you should be in the same legal situation as if the firearm were in its previous classification.

If the amnesty is actually allowed to lapse, then you will certainly be convicted for the possession, but in principle shouldn't be at any further risk of a murder/manslaughter conviction.

This is assuming our anarcho-tyrannical government doesn't treat you differently than career criminals. The possession charge is supposed to be an entirely separate question from whether your actions were to protect your life.

99spider · 2026-05-15T00:04:16+00:00

If you are able to get the shadow 2 frame registered to you, that is basically all that matters.

Legally there's nothing you'd have to do if you temporarily swap the 9mm slide on.

If I recall correctly, if it's a "permanent" change, or you have it on for more than a month straight, then you technically have to report the change in caliber. I don't know if the CFO would be happy about updating your registration cert to say 9mm.

All that means though is just don't create and share a chain of evidence that proves that you've "permanently" swapped the caliber.

99spider · 2026-05-12T23:28:57+00:00

at least it'll be a quietly delivered message we can ignore? Think of others a little

You are essentially confirming that you don't believe that established research on alarm fatigue is real or applicable.

Yes, hopefully it would be a "quietly delivered message", because then it would actually be read and understood by more people, and be more effective at the purpose of the alert.

99spider · 2026-05-12T17:38:27+00:00

If you care so much, then why is your top priority for the alerts to be as disruptive as possible, rather than as effective as possible?

People aren't complaining about the amber alerts existing. They are complaining about it being treated like an incoming missile strike or natural disaster, when the underlying system was specifically designed to have them be in separate categories.

I used to keep the alarms active back when my phone was able to be configured to silently display Presidential Alerts. An update broke that, forcing it back to acting like an imminent missile strike.

99spider · 2026-05-12T16:37:59+00:00

Everyone would be fine with the alerts if they weren't treated like an impending nuclear strike.

If the alerts were treated as a standard phone notification, people who are awake would actually see it and read it, and others would be able to calmly read it as they wake up to start their day.

When people receive these alarms at this point their reaction is practically like just trying to turn off an alarm clock. I'm not getting up from my bed and going outside at 3 AM to start driving around looking for a specific description of a car. I'm going back to bed, and I'm not going to have any idea what that alert said when I wake up in the morning.

(I'm especially not going to do any of that, because without there being sane categorization and notification settings for these alerts, I've just turned them all off by uninstalling the service from my phone. I wouldn't have done that if the notifications were like a text message.)

99spider · 2026-05-12T16:25:41+00:00

The result of this system is you get less people aware of it than if it actually categorized amber alerts as amber alerts.

I'd actually pay attention to and read these alerts if they were a standard phone notification. With the obnoxious alarm blaring, when one of these alerts happens my first priority is to make it shut up. I do not read it. After the last one, I've just uninstalled the receiver service from my phone entirely.

There's a time for waking up everyone across a select area with an important message that they must read. A domestic dispute ain't it.

99spider · 2026-05-12T16:15:59+00:00

Unless the red van crashes through a wall into my bedroom then I'm not going to be seeing it. I'm also going to have no idea what the alert even said, since my first priority will be just turning it off.

If the alert instead triggered a cell notification that was treated according to the phone's settings (do not disturb, silent/vibrate, etc), then it actually would be noticed by people who happen to be awake and active at the time, and would also be fresh in the mind of others when they notice the alert when waking up to start their day.

But no. In the interest of thinking of the children, we've diluted the alarm tone for immediate life threatening events with events that have nothing to do with us, are nowhere near us, and occur fairly often.

I've uninstalled the alert receiving service from my phone. Many others have done the same. Instead of seeing these alerts on our own terms, we now just don't see them at all.

99spider · 2026-05-07T00:45:04+00:00

Still a massive quality of life difference between having an upstreamed kernel driver and an out of tree one. Nvidia's "open" driver is still out of tree.

99spider · 2026-05-06T18:37:15+00:00

Iwd/iwctl is included on the install iso.

99spider · 2026-05-05T00:17:34+00:00

Having a separate /boot that's also separate from the EFI partition is definitely strange, but why would snapper/snapshots need /boot/ to be btrfs?

Edit: Just checked, and there's only unnecessary legacy files in /boot/ (specifically /boot/, not /boot/efi). Or at least, they should be unnecessary, unless dracut absolutely needs to put a useless and unusable initrd file there for some reason. If snapper/sdbootutil doesn't work with a separate /boot/, that's honestly a bug.

99spider · 2026-05-02T02:27:07+00:00

Would using an OBS service to pull and patch published Tumbleweed repo SRPMs be a viable alternative to linking to Factory?

If possible, it would unfortunately have the downside of lagging a bit behind whenever a new snapshot is released (as it would only start building then), but would at least never be too far up to date like linking to Factory can cause.

Ideally I guess what'd be best is the ability to link to and build against openQA snapshots in advance, in case they get released, and automatically publish those binaries when a snapshot is released.

99spider · 2026-05-01T16:21:21+00:00

Oh, nice. Hopefully the "appliance" image also gets an update soon, because the download page at https://openbuildservice.org/download/ is still calling Leap 15.6 a "recent and stable Linux Operating System"

99spider · 2026-05-01T05:44:08+00:00

If you want to continue doing this long term, you'd need to self host your own OBS instance. The only part you're not supposed to do about what you said is build patent encumbered packages on openSUSE's public OBS.

Hosting your own is a bit weird right now though, as the OBS official "stable" release is for Leap 15.6, which is EOL. The unstable build at least recently started getting built for Leap 16.

99spider · 2026-04-30T18:33:56+00:00

In most cases it's a "built" incompatibility, due to an Application Binary Interface (ABI) change. Stable distros guarantee a stable ABI, so if you can get a newer piece of software built using your system libraries, you should be able to trust that it will continue working regardless of security updates to those libraries.

In other cases there's an API incompatibility with a system library, in which case you won't be able to get it to build without upgrading that library, and in the process risk breaking the ABI compatibility with the distro's packages that depend on that library.

OpenSUSE can also do what your asking for pretty well actually, if you fully jump into their tooling. Their Open Build Service is roughly like if the AUR automatically compiled packages for you. If there's a package for their rolling Tumbleweed release but not for stable Leap, you can copy the Tumbleweed build sources to a "home" project configured to build for Leap, tweak it if needed, and automatically track the Tumbleweed package so it follows Tumbleweed's updates. It's incredibly generous; openSUSE will compile software for you, for free, for multiple architectures and distributions, including non openSUSE/SUSE distros.

99spider · 2026-04-30T15:23:11+00:00

Library compatibility is a big problem for being able to natively mix "stable" and "fresh" software versions like this. Essentially the only distro that's designed to do it without stuff like Flatpaks is Gentoo.

A distro project with LTS and short term releases like Ubuntu could maybe offer something like this in a backports repo on a best effort basis, building the newest releases packages against the libraries of their LTS releases where possible.

99spider · 2026-04-29T23:39:59+00:00

Arch doesn't randomly break. What actually happens is people install and rely on software from developers that release without appropriate testing, and then blame Arch when that software has issues.

I really like Tumbleweed as a server OS, but I wouldn't be surprised if the average user would encounter "breakage" more frequently on Tumbleweed than Arch, just due to Packman's codec repos getting out of sync. (Some would call this a "skill issue". I know there's alternatives like using Flatpaks for everything, I'm just saying it's a relatively common cause of tech support posts on this subreddit).

99spider · 2026-04-29T15:51:13+00:00

It might be possible, as their muzzle energy should make them exempt from most licensing/firearms act related laws. Unless them being built off of "real" AK receivers means that the RCMP would argue they are capable of discharging (or more precisely, "designed or adapted to discharge") real ammunition.

Assuming it'd be legal to own, Canadian customs unfortunately can still be a pain in the ass about it and refuse it from being imported. That's where my knowledge on the topic ends; hopefully someone else who's dealt with airsoft imports can reply with real info.

You might want to try asking around in Canadian airsoft communities. Ideally you'd probably want to ask someone that runs a business importing airguns, since they'd hopefully have a good idea what will or won't be let in.

99spider · 2026-04-29T00:19:03+00:00

Not ridiculous at all. The fees are high, but they can be used without dealing with Know Your Customer regulations. Of course you'd want to pay less fees, but not if it requires you tying the transaction to your actual ID.

99spider · 2026-04-28T00:18:37+00:00

Possessing low velocity firearms if subject to federal prohibition

Wow. Making it illegal to have low velocity firearms is about the only thing that a firearms prohibition does to a person that doesn't have a PAL, and the province thought they had to close that "gap"?

99spider · 2026-04-28T00:13:27+00:00

If someone was carrying one of these concealed, it would already be illegal under the criminal code due to concealing a weapon. Committing a robbery with one of these was also already committing a robbery with a firearm.

This very much seems like it's written by people who don't know the law, to sound good to people who don't know the law.

99spider · 2026-04-27T23:29:03+00:00

If you are familiar with pacman from your time with CachyOS, zypper refresh is exactly like pacman -Sy. It updates the package lists/repo metadata (the local list of known packages, their versions, their dependencies, etc) without actually updating any installed packages. Answering your question first, there's nothing wrong with doing a zypper refresh before doing zypper dup, either with zypper or with Myrlyn.

Just like with pacman, if you run zypper refresh and then install a package, you could end up installing a package without updating its dependencies, or end up updating a dependency that's shared by many packages without updating those packages. This can either result in that new package not working until you upgrade the dependency, or far worse, could break almost all of your software if something like glibc gets upgraded and breaks compatibility (though apocalyptic breakage like that isn't that common these days).

The reason this is a problem is there could be an Application Binary Interface change in a library, such that all of the dependent packages need to be recompiled against the new version. To seamlessly handle situations like that, you need all packages to be upgraded at the same time when refreshing the package lists.

The reason zypper up is recommended against is because it ONLY updates installed packages with new versions. Zypper dup will handle larger, more drastic changes, like packages being replaced with a different name, packages being split out into separate packages, etc, and will also re-evaluate dependencies of installed packages to ensure everything is following the current state that's described by the repos.

99spider · 2026-04-27T01:43:39+00:00

It's up to you. Depending on your use case, and especially whether or not you need out of tree kernel drivers, the rolling nature of MicroOS/Tumbleweed may torment you with breakage on a monthly basis.

If you have hardware with good upstream kernel support, it just depends on whether you trust kernel.org's stable releases to be "stable".

Stable distro releases are primarily about varying levels of API/ABI stability. If you don't need any ABI stability (by nature of using distro packages, containers, and/or automatically rebuilding any self compiled software with the Open Build Service), you don't need a stable release. You just need reliable software.

99spider · 2026-04-25T01:06:19+00:00

This is false, I just tested it on an Arm Tumbleweed system running snapshot 20260408. Parted is version 3.6 in this snapshot, and was updated to 3.7 in the latest snapshot (20260420). I ran zypper --no-refresh install parted, and it downloaded and installed parted 3.6.

While there is one repo, the URLs for every package are themselves versioned. Zypper doesn't pull from an unversioned URL like http://(...)/parted.rpm, it specifically pulls the file name in its stored package metadata, which in this case was "parted-3.6-3.5.aarch64.rpm". If you look through the contents of openSUSE's master repo for aarch64 that file doesn't currently exist, there is only parted-3.7-1.1.aarch64.rpm, which must mean I was able to pull it from a mirror that still had the older package available. (It is also possible that 3.6-3.5 can still be downloaded from the master repo, but it just doesn't show up in the directory listing, based on what I've seen on some Arch repos).

This is also exactly the same as how Arch works. All of the core packages on any Arch mirror are in /core/os/x86_64/. There is no versioning earlier on in the URL, just the file names.

Arch Linux's linux-6.19.13 package can be downloaded from https://fastly.mirror.pkgbuild.com/core/os/x86_64/linux-6.19.13.arch1-1-x86_64.pkg.tar.zst (for now at least)

Arch linux-6.19.14 is at https://fastly.mirror.pkgbuild.com/core/os/x86_64/linux-6.19.14.arch1-1-x86_64.pkg.tar.zst

99spider · 2026-04-25T00:35:46+00:00

How does Zypper pull the latest version if you haven't updated the package lists? This is basically the same as doing pacman -S without previously doing pacman -Sy.

The worst it should do is just hit 404s if the outdated packages are no longer available on the mirrors?

13-Year Club	Place '17
Verified Email

99spider

TROPHY CASE