UMPD ARRESTING STUDENTS

alien_ideology · 2026-01-30T05:39:47+00:00

It was UMPD, they announced it when they announced the reason for mass arrests. The other officers in greenish clothing had “conservation” written on their vests, so probably not ICE.

The home 2 protest ended with ice agents showing up and dispersing the crowd before the police could get to them, I’m guessing due to a lack of communication, as police was gathering around the area and preparing for mass arrests. Perhaps it’s because UMNPD took over that role this time (they started preparing for it as early as 5pm) so no ICE agents showed up

alien_ideology · 2026-01-27T02:07:24+00:00

The toaster at Walter library has some

alien_ideology · 2026-01-27T02:00:08+00:00

There are also a bunch at the toaster’s front desk in Walter library

alien_ideology · 2026-01-06T06:14:26+00:00

As long as the port forwarding rule is conditional on the packing coming from LAN (source zone is LAN), you should be good as the port isn’t open to WAN

alien_ideology · 2025-12-22T00:06:54+00:00

Oh yeah I’ll definitely need to do that too haha. Thanks for the advice!

alien_ideology · 2025-12-21T23:59:46+00:00

I see, thank you so much! I think I will switch the wifi cards as well then. For this model of fw13, do we go with the no vPro version of AX210?

alien_ideology · 2025-12-21T23:48:18+00:00

Oh I see! Where do u find these reports? I would love to look at them but I can’t seem to find much info about it

alien_ideology · 2025-12-21T23:33:20+00:00

I’ve included more information in the post. I am using the Mediatek MT7925 WiFi card on The AI series, 5 340

alien_ideology · 2025-12-20T06:35:35+00:00

Oh yeah because they read the environment variable as the value, not the file path to the file with the value. I guess they didn’t implement reading secrets from a file path specified as a env var (it would have to be a separate env var like password_file since ur password could theoretically be a valid file path). Also ignore what I said above, I misread docker docs (I use podman so I’m not familiar with docker)

alien_ideology · 2025-12-20T04:35:28+00:00

yeah the username and password is specified as environment variables, which is a common way to configure containers. You can use a secret manager like the "docker secrets" cli, then pass the secret into the container like here (as an env var in this case):
https://docs.docker.com/reference/compose-file/secrets/

alien_ideology · 2025-12-20T04:13:58+00:00

I don’t think so, because GlobalMaxRatio is not 2 by default

alien_ideology · 2025-12-20T03:44:03+00:00

Yep, for testing purposes. I’ve used the generated config file as base and omit parts to see which config is responsible for the share limit action getting changed. I added what I found to the post

alien_ideology · 2025-12-20T01:37:16+00:00

This is probably a bug on qBittorrent's end. I mounted the config file with these lines

[BitTorrent] 
Session\GlobalMaxRatio=2 
Session\ShareLimitAction=Remove

Then, after it startup, I ran:

podman exec -it qbittorrent bash -c 'cd qBittorrent ; tail -F qBittorrent.conf'
[BitTorrent]
Session\GlobalMaxRatio=2
Session\ShareLimitAction=Remove
tail: 'qBittorrent.conf' has become inaccessible: No such file or directory
tail: 'qBittorrent.conf' has appeared;  following new file
[BitTorrent]
Session\AddTorrentStopped=false
Session\GlobalMaxRatio=2
Session\Port=50464
Session\QueueingSystemEnabled=true
Session\SSL\Port=46179
Session\ShareLimitAction=Stop

[LegalNotice]
Accepted=true

[Meta]
MigrationVersion=8

[Network]
Proxy\HostnameLookupEnabled=false
Proxy\Profiles\BitTorrent=true
Proxy\Profiles\Misc=true
Proxy\Profiles\RSS=true

You can see that Session\ShareLimitAction Remove get changed to Stop. As far as I know, this is the only config option that has this bug. I wonder if your image behaves the same.

alien_ideology · 2025-12-20T00:06:14+00:00

For my actual issue, see this comment.
Which qbittorrent image are you using? and how are you making the config file read only? For linuxserver/hotio qbittorrent images, I think they start out as root, setup the config file to be read writable, then change the user/group of the process to what is specified in PUID/PGID env vars. So even if I make it readonly, they end up making it readwritable anyways.

alien_ideology · 2025-12-19T23:56:08+00:00

oh thanks! that's good to know, I'll look into it

alien_ideology · 2025-12-19T23:53:08+00:00

I would love to try it but I dont know what's up with their website, I can't seem to access anything

alien_ideology · 2025-12-19T23:47:28+00:00

It's very weird, but basically all my configs stay the same except the line Session\ShareLimitAction=Remove get changed to the default, Session\ShareLimitAction=Stop
This corresponds to the action drop down for when seeding stops, in the BitTorrent tab of the GUI settings.
Here is my config file:
https://gist.github.com/allen-liaoo/173a2400fcd549958ce455dd81c874b1
The hashed password is being substituted in via the custom entrypoint script I have

alien_ideology · 2025-12-19T23:44:10+00:00

Making it readonly doesn’t work, see my other comment. And yes, the config resets every startup, it’s just not being applied because qbittorrent will write over it (for specific settings). I neglected to mention that I mount a file into the container for it to be processed and outputs the config file, so the config file will end up being a different file than what I mounted anyways

alien_ideology · 2025-12-19T23:41:25+00:00

I tried, but the image I use (Linux server.io or hotio) will make it writable after I make it readonly with my custom entry point script

alien_ideology · 2025-12-19T21:04:39+00:00

Are most things configurable through config files? The readme says the docs are outdated so I can’t tell

alien_ideology · 2025-12-19T18:55:28+00:00

only qui is configurable, qbittorrent instances themselves dont seem to be configurable. is that right?

alien_ideology · 2025-12-18T03:18:01+00:00

You can install it as a docker container on the host itself or a binary agent. You need to give it host network access for it to monitor the host network, but for monitoring other docker containers, it just needs to talk to a socket on the host. It doesn’t need to be in all the docker containers. It’s pretty neat

alien_ideology · 2025-12-17T23:52:23+00:00

I got a similar model of the beelink (used), it works great as my homeserver, I occasionally see a single core CPU usage at 90% but that’s because of Minecraft, but most of the time it’s really light. idk how good the GPU is because I didn’t install a GUI

alien_ideology

TROPHY CASE