sugar_in_your_tea

joined 2 years ago

I would delete my account the moment I'm too lazy to check if I've already deleted it.

[–] sugar_in_your_tea@sh.itjust.works 1 points 18 hours ago* (last edited 18 hours ago) (1 children)

I disagree that anything you describe could actually be both commercially viable and deployable without authoritarian involvement

You haven't heard of Ring cameras? Commercial security systems? They do basically what I'm describing, just not as well because they don't have as much of an incentive. Are end users willing to pay for these more advanced models? No, so consumer grade cameras stick to object detection like deer vs racoon instead of specific individual detection (e.g. scanning eyes).

Governments, however, are willing to pay that amount. Why? Because they think it'll help them detect criminals, and they think that helps keep people safe. It's an extension of the HOA idea, just with government-scale funds backed up with law enforcement to go after threats. That, in itself, isn't authoritarian, but setting up such a system opens the door for authoritarians to take control and misuse it.

I'd go so far as to say that the people in your theoretical HOA are analogous to supporters of a authoritarian regime.

Analogous, sure, but the HOA has no enforcement arm for non-residents, so all they can do is ask the police to intervene. That's the difference with a city, it has a police force it can order to intervene using information from that system. It's the mixing of enforcement and surveillance that makes it authoritarian.

So a surveillance system is not itself authoritarian, it's only authoritarian of there's some enforcement arm to enforce obedience or punish disobedience.

If it is nearly impossible to meaningfully use apolitically, then it is not apolitical.

Again, I disagree. Something is only political when used for political ends.

[–] sugar_in_your_tea@sh.itjust.works 7 points 22 hours ago (1 children)

What's crazy is I agree with some of what he says, but disagree entirely with his company.

Basically, he says the Antichrist promises security in exchange for giving up your freedom. However, his company does exactly that, it promises security in exchange for taking away freedom from the people. So at best he's a hypocrite and at worst an accelerationist.

I agree that people are willing to trade freedom for security, but I disagree that's what governments should do. Governments need to protect freedoms first, and security second.

[–] sugar_in_your_tea@sh.itjust.works 1 points 1 day ago (3 children)

Similarly, even if HOAs could deploy a system like that, that’d make them authoritarian.

That really depends how the system is used. If it explicitly doesn't record regular residents and people who have signed up officially as visitors (and homeowners can review footage), I don't think the camera system itself would really be authoritarian. Yeah, the system would be capable of violating privacy, but as long as the system is transparent and reviewable by the residents, I think it can be privacy-respecting. Basically, it would be like a home security system, but across a neighborhood, and it can even be self-hosted to not let third parties access the data (and police requests would go through the HOA board, which consists of residents).

That's my point. If the system itself can be used in a privacy-respecting way (and the vast majority can), even if it's typically not used that way, the system itself cannot be authoritarian. If an institution uses it in an authoritarian way, then the institution is authoritarian.

In short:

  1. cameras are not authoritarian
  2. databases are not authoritarian
  3. license plate and face recognition software isn't authoritarian
  4. connecting 1-3 together in a searchable way isn't authoritarian (would be a fun hobby project)
  5. Sharing info from 4 isn't authoritarian (again, could be a fun hobby with friends)
  6. An institution (gov't, business, HOA, etc) using 4 and/or 5 to enforce policy on citizens/employees/residents/etc is authoritarian

I have friends that use home cameras to do object classification as a hobby, mostly to identify and fee record wildlife. I've also heard of people doing this to identify package deliveries and catch package thiefs. Sharing those models with others on the internet is largely the same idea as what flock is doing, and with enough data, similar solutions to what Palantir is doing could be done entirely by hobbyists.

The products Flock and Palantir aren't authoritarian in and of themselves, it becomes authoritarian when those products are used to enforce policy.

[–] sugar_in_your_tea@sh.itjust.works 1 points 1 day ago (1 children)

Letting the shampoo sit is only needed for medicated shampoo, like for dandruff, and that's so the medicine has time to work. For every other type of shampoo, you should rinse it right after thoroughly getting to the scalp to not irritate the scalp.

I use dandruff shampoo, hence why I wait before rinsing. If I didn't have dandruff, I'd probably do shampoo last.

I just checked all of my shampoo bottles (apparently we have almost 10... we have shampoo for dyed hair, dandruff, kids, dry hair, etc). None of them recommend waiting before rinsing, not even the dandruff shampoo (well, Selsun Blue doesn't, can't check the other since it's in my SO's native language, which I can't read). I remember seeing some other brands mention waiting (I think Head and Shoulders?), so YMMV.

Some solutions here are technically illegal to make laws about. The government cannot force a company to give away its copyrighted server code, not even in compiled form. Since there are alternatives that don't require giving away copyrighted material, it's better to keep it vague.

So it's both the friendliest to companies and the easiest to pass as a law.

Yeah, I never appreciated how long it takes to wash hair until I washed my daughter's shoulder-length hair. My hair has always been short, so a shampoo would only take 10-20 sec to get everything lathered and maybe 30 sec to rinse. My daughter's hair took about double that time for both steps.

So yeah, I can see dealing with long hair taking significantly longer. That said, that's more like 10-15 min instead of 5 min, not 30 min.

If you're struggling with body dysphoria, wouldn't you want to be naked for a shorter amount of time?

I have a waterproof ereader, but there's no way I'd read in the shower. It's much more comfortable to read on my bed or on a chair. It's also too noisy to listen to audiobooks, unless I'm wearing noise-cancelling headphones, but then I can't wash my hair or ears properly.

So yeah, in and out in 5 min, and then read in more comfortable place.

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 day ago* (last edited 1 day ago) (3 children)

Simple:

  1. get everything wet - 10 sec?
  2. shampoo, but don't rinse - 30s-1m?
  3. lather soap everywhere, with a scrubby (loofah or similar) - 1-2. min
  4. rinse top down - 1-2 min?

That takes about 5 minutes, more if I shave at the same time (am dude, but don't shave every day). I don't think I've ever taken more than 10 min.

[–] sugar_in_your_tea@sh.itjust.works 1 points 2 days ago (5 children)

I would argue that such a product would be by its nature political, because it’s only practical use case was the furtherance of a political goal.

Again, I disagree. Surveillance has a lot of use cases outside of government, and a huge use case is keeping the government in check. Palantir could have sold its services to non-profits like the ACLU as a check on local, state, and law enforcement agencies. They could have sold it to HOAs and neighborhood watch associations as an early warning system for repeat offenders.

The government skirting the 4th amendment (and a few others) doesn't automatically make its sub-contractor's products "authoritarian," it makes its use of those products authoritarian.

So a system that does so (like the ones sold to the govt) is a political software product.

I disagree with that conclusion. The use by the government is authoritarian, but that doesn't make the product authoritarian.

To me where it gets tricky is when private entities grow to government-sized proportions, and begin to use these same tools for similar purposes

A private entity can do authoritarian things, like spying on its employees or customers. Authoritarianism isn't strictly tied to governments, but anything that acts like a government. Here's the first definition I found:

Characterized by or favoring absolute obedience to authority, as against individual freedom.

Software can't really favor obedience to authority, it can't really deny you your freedoms, it's just software. Likewise for a camera system. The only way those things can be authoritarian is if paired with some form of enforcement arm, like corporate security or law enforcement. So that combined system is authoritarian, the cameras or software on their own cannot be authoritarian.

That's my point.

And ideally give enough forewarning that the community can build it before they shut the servers off.

 

Current setup:

  • one giant docker compose file
  • Caddy TLS trunking
  • only exposed port is Caddy

I've been trying out podman, and I got a new service running (seafile), and I did it via podman generate kube so I can run it w/ podman kube play. My understanding is that the "podman way" is to use quadlets, which means container, network, etc files managed by systemd, so I tried out podlet podman kube play to generate a systemd-compatible file, but it just spat out a .kube file.

Since I'm just starting out, it wouldn't be a ton of work to convert to separate unit files, or I can continue with the .kube file way. I'm just not sure which to do.

At the end of this process, here's what I'd like in the end:

  • Caddy is the only exposed port - could block w/ firewall, but it would be nice if they worked over a hidden network
  • each service works as its own unit, so I can reuse ports and whatnot - I may move services across devices eventually, and I'd rather not have to remember custom ports and instead use host names
  • automatically update images - shouldn't change the tag, just grab the latest from that tag

Is there a good reason to prefer .kube over .container et al or vice versa? Which is the "preferred" way to do this? Both are documented on the same "quadlet" doc page, which just describes the acceptable formats. I don't think I want kubernetes anytime soon, so the only reason I went that way is because it looked similar to compose.yml and I saw a guide for it, but I'm willing to put in some work to port from that if needed (and the docs for the kube yaml file kinda sucks). I just want a way to ship around a few files so moving a service to a new device is easy. I'll only really have like 3-4 devices (NAS, VPS, and maybe an RPi or two), and I currently only have one (NAS).

Also, is there a customary place to stick stuff like config files? I'm currently using my user's home directory, but that's not great long-term. I'll rarely need to touch these, so I guess I could stick them on my NAS mount (currently /srv/nas/) next to the data (/srv/nas//). But if there's a standard place to stick this, I'd prefer to do that.

Anyway, just looking for an opinionated workflow to follow here. I could keep going with the kube yaml file route, or I could switch to the .container route, I don't mind either way since I'm still early in the process. I'm currently thinking of porting to the .container method to try it out, but I don't know if that's the "right" way or if ".kube` with a yaml config is the "right" way.

 

Apparently US bandwidth was reduced to 1TB for their base plan, though they have 20TB for the same plan in Europe. I don't use much bandwidth right now, but I could need more in the future depending on how I do backups and whatnot.

So I'm shopping around in case I need to make a switch. Here's what I use it for:

  • VPN to get around CGNAT - so all traffic for my internal services goes through it
  • HAProxy - forwards traffic to my various services
  • small test servers - very low requirements, basically just STUN servers
  • low traffic blog

Hard requirements:

  • custom ISO, or at least openSUSE support
  • inexpensive - shooting for ~$5/month, I don't need much
  • decent bandwidth (bare minimum 50mbps, ideally 1gbps+), with high-ish caps - I won't use much data most of the time (handful of GB), but occasionally might use 2-5TB

Nice to have:

  • unmetered/generous bandwidth - would like to run a Tor relay
  • inexpensive storage - need to put my offsite backups somewhere
  • API - I'm a nerd and like automating things :)
  • location near me - I'm in the US, so anywhere in NA works

Not needed:

  • fast processors
  • lots of RAM
  • loose policies around torrenting and processing (no crypto or piracy here)
  • support features, recipes, etc - I can figure stuff out on my own

I'll probably stick with Hetzner for now because:

  • pricing is still fair (transfer is in line with competitors)
  • can probably move my server to Germany w/o major issues for more bandwidth
  • they hit all of the other requirements, nice to haves, and many unneeded features

Anyway, thoughts? The bandwidth change pisses me off, so let me know if there's a better alternative.

 

Here's what I currently have:

  • Ryzen 1700 w/ 16GB RAM
  • GTX 750 ti
  • 1x SATA SSD - 120GB, currently use <50GB
  • 2x 8TB SATA HDD
  • runs openSUSE Leap, considering switch to microOS

And main services I run (total disk usage for OS+services - data is :

  • NextCloud - possibly switch to ownCloud infinite scale
  • Jellyfin - transcoding is nice to have, but not required
  • samba
  • various small services (Unifi Controller, vaultwarden, etc)

And services I plan to run:

  • CI/CD for Rust projects - infrequent builds
  • HomeAssistant
  • maybe speech to text? I'm looking to build an Alexa replacement
  • Minecraft server - small scale, only like 2-3 players, very few mods

HW wishlist:

  • 16GB RAM - 8GB may be a little low longer term
  • 4x SATA - may add 2 more HDDs
  • m.2 - replace my SATA SSD; ideally 2x for RAID, but I can do backups; performance isn't the concern here (1x sata + PCIe would work)
  • dual NIC - not required, but would simplify router config for private network; could use USB to Eth dongle, this is just for security cameras and whatnot
  • very small - mini-ITX at the largest; I want to shove this under my bed
  • very quiet
  • very low power - my Ryzen 1700 is overkill, this is mostly for the "quiet" req, but also paying less is nice

I've heard good things about N100 devices, but I haven't seen anything w/ 4x SATA or an accessible PCIe for a SATA adapter.

The closest I've seen is a ZimaBlade, but I'm worried about:

  • performance, especially as a CI server
  • power supply - why couldn't they just do regular USB-C?
  • access to extra USB ports - its hidden in the case

I don't need x86 for anything, ARM would be fine, but I'm having trouble finding anything with >8GB RAM and SATA/PCIe options are a bit... limited.

Anyway, thoughts?

view more: next ›