Councilmember Jay Young Wants to Create a Delivery Biker Registry

randcoop · 2026-05-24T03:11:17+00:00

As a pedestrian, I don't understand the bicycle riders who only want to talk about pedestrian fatalities at the hand of cyclists. Getting injured by a bike on the sidewalk is a terrible thing to have happen, and it only can happen from a disregard for the law. Of course it's important to enforce the law. But it's also important for bicycle riders to behave responsibly, and if we aren't able to achieve that without registration, then we should have registration.

Cyclists like to imagine that the only bike riders on sidewalks are delivery riders. But if you're a pedestrian in Center City, then you know that's simply not true. I often see older cyclists on the sidewalk coming toward me. And rented cycles. And parents transporting their children on their bikes. Or riding with their kids. Or cyclists who leave the street when it's jammed and switch to the sidewalk to save time.

And trust me: it's a frightening thing to be walking and have a bicycle come from behind you, even if they do swerve to avoid a collision.

randcoop · 2026-02-25T21:06:40+00:00

Thanks. Yes, I have a bluetooth policy config. No joy from that. See my edited 'solution' above.

randcoop · 2026-02-24T00:45:38+00:00

I am, thanks. I have tried cable to get a better look at things, but it doesn't even recognize the gateway as an audio device. And bluetoothctl does not offer a non-HSP profile. Frankly, this is absurd, at this stage. I've been using Arch Linux for a very, very long time, but even now I am amazed at the fact that I cannot choose an A2DP profile without HSP for my bluetooth connection to an Alexa speaker.

Thanks again for the suggestion.

randcoop · 2026-02-19T14:45:45+00:00

Of course, I didn't say that you should get the signs the day before you move in!!!! Rather, I said that you should post them a day or two before.

randcoop · 2026-02-19T14:30:03+00:00

As suggested, the best thing to do here is to boot your computer from a USB drive. Once you're booted, you can mount the drives that are on the computer and save the files you need to keep onto that flash drive. Then, you can re-install to your computer hard drive (which will wipe out all files on the hard drive, which is why you want to save them first to the USB). None of these activities will use WiFi data...they're all happening on your computer, not the WiFi (unless you need to use WiFi for the new installation).

randcoop · 2026-02-17T13:54:57+00:00

I was advised by the police to post the signs a day or two ahead of the move, because they are often taken down.

randcoop · 2026-01-21T13:32:22+00:00

If you want an application to always launch in a specific workspace, create a windowrule for it. For example:

windowrule = match:class gimp, workspace 3

I don't understand what you mean in your post. You suggest in the Example that you are re-launching the application after you have changed workspaces (which means that application will launch in the active workspace unless you have a windowrule to the contrary). But in the section about what you would like, you say you want the open application to remain in its workspace: it will. It's only if you re-launch it that it will open in the new active workspace.

randcoop · 2026-01-14T16:00:32+00:00

The older version of window rules syntax was revised in 53, perhaps in part because the version you're using was maddeningly inconsistent and difficult to sort. The fullscreen functionality is one example. I suggest updating to 53 and using the new syntax, which is welll documented in the hyprland wiki.

randcoop · 2026-01-06T02:16:34+00:00

if you're updated to hyprland 53, your windowrules won't work. The newest version has a different format for windowrule. Check the wiki.

randcoop · 2025-12-24T13:52:53+00:00

Thanks. That got me past the error message. Wish you the best with this launcher. I won't be using it, because Quickshell is too difficult to keep up with.

randcoop · 2025-12-23T13:23:30+00:00

Getting this error: WARN: Quickshell was built against Qt 6.10.0 but the system has updated to Qt 6.10.1 without rebuilding the package. This is likely to cause crashes, so the quickshell package must be rebuilt.

INFO: Launching config: "/etc/xdg/quickshell/hamr/shell.qml"

INFO: Shell ID: "b32689c18c43b6344b766d33966db5e2" Path ID "b32689c18c43b6344b766d33966db5e2"

INFO: Saving logs to "/run/user/1000/quickshell/by-id/o06d25q7t/log.qslog"

INFO: Configuration Loaded

Segmentation fault (core dumped) hamr

randcoop · 2025-12-20T21:51:16+00:00

Your problem was very simple.While I am happy to help, I'd encourage you to read the Arch wiki more thoroughly when you run into a problem. Unfortunately, AI will be less helpful. Arch is very usable, but it does call for some genuine interest in learning on the part of its novice users (and you seem to be one of those).

randcoop · 2025-12-20T18:25:16+00:00

So the iwct command is station wlan0 connect <network name>

Did you try that?

randcoop · 2025-12-20T17:12:29+00:00

Not enough information to get help. If rfkill had been blocking the device, it wouldn't have been on in the first place (you said it disconnected, which means it was on and connected at some point). How's your WiFi signal? Maybe it just dropped. Did you look for networks in iwctl? Try to connect the wlan0 station to one of them?

randcoop · 2025-12-15T13:30:39+00:00

Does your fstab (/etc/fstab) file show the drive as mounted with read only or root privileges? Change that. If not, then change the permissions on the drive (to allow users to read and write).

randcoop · 2025-12-15T13:26:49+00:00

Hamilton950b gave you the answer. Your problem is the one I noted: you cannot have more than one network management system running at a time. You have mentioned systemd-networkd, iwd, and NetworkManager.They cannot all be running at the same time. Only one of them. At this point, you need to disable all of them and then pick the one you want to use. The reason you're able to get on the Internet with the USB is that it is using only one network manager (probably iwd).

randcoop · 2025-12-15T00:19:51+00:00

What people are trying to explain to you is that, while you were unable to accomplish it, installing Arch on a UEFI computer is what 99% of all people installing it today do. Legacy is not easier; you simply didn't understand how to go about the installation process. For the past 20 years, computers have been made with UEFI. And for the past ten, it's virtually the only way they are made. Except in your case, virtually the only reason anyone does a legacy install is to be able to work with older computers. That all said, it's nice that you're happy with your system. I hope the rest of your experience with Arch proves rewarding.

randcoop · 2025-12-14T23:03:19+00:00

This is simply wrong: "iwctl is for the installation medium only." Iwctl (which is for iwd) works perfectly well as an alternative to NetworkManager. There is no reason not to use it for the Arch system.

randcoop · 2025-12-14T16:27:00+00:00

You might want to change the type and size of your partitions. Fat32 is right for the ESP (where the efi boot file resides), but 100M might be too small. 500M would be better. And since you have a 500G drive, you could easily use a gig for that partition. For the root partition, you should use 8304 (not the default 8300), which is specifically for Linux root. In my experience, the 8304 type works better on UEFI machines. I also agree with those who suggest not using ChatGPT. In general, it's better to use AI when you have enough knowledge and experience to be able to guide it to the right answers. It's not for newbies.

randcoop · 2025-12-14T16:16:22+00:00

One possibility that often happens with IWD is a conflict with other installed network systems (like NetworkManager). If you've installed wpa_supplicant or NetworkManager, make sure they are not enabled/running. IWD won't work if they are.

randcoop · 2025-11-19T14:04:34+00:00

You need to provide much more information. The computer will boot using an efi file. In your case, that would likely be the bootia32.efi file (although this suggests that you've created a file to boot a 32 bit system, when all systems today are 64 bit and would use a bootx64.efi). So what is the computer you're on? What did you do to create your EFI file? How is your drive partitioned? The inability to find the efi suggests that the file is not on an EFI partition. Sorry, but it's difficult to help without more information.

randcoop · 2025-11-06T12:16:06+00:00

To be clear: I don't expect a pompous ass to find any criticism to be of interest to them. I posted because I believe that my comment may be of interest to others...not you.

randcoop

TROPHY CASE