sugar_in_your_tea

joined 2 years ago
[–] sugar_in_your_tea@sh.itjust.works 4 points 15 hours ago (1 children)

Yeah, I completely agree.

I drive old cars because they don't spy on me and they're inexpensive to own. I have an 07 hybrid and an 06 minivan. They're only an expression of my personality to the extent that I don't care about my car and need something to get from A-B. I don't flaunt it, and I'll probably replace it with an older EV because refilling gas is annoying for my dedicated commuter (the hybrid).

I'd rather ride my bike, but my work is too far away (2 hours on transit, ~1.5 hybrid w/ bike, maybe 1 with a riced ebik, each way), and my reasons for sticking with my employer and not moving are more important than my preference for cycling.

My mode of transportation is about utility, not expression of personality. I'd drive a truck if it made sense, I just haven't found one that makes more sense than renting one the 2-3 times per year I need to haul something that doesn't fit in my minivan.

When I need to upgrade my car, I'll find something sensible and maybe remove the parts I don't like. It's not a big deal.

Also performance, maintenance, and regression.

CoMaps

I haven't. I looked into it, and that's quite the drama. I like the name of CoMaps better, so I'll check it out. I see shared commits, but they seem to go to Organic Maps first and then I guess get cherry-picked onto CoMaps?

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

The main blocker is MFA. I can technically work around Google Authenticator (I use Aegis currently) because I can run it on my laptop, but I also need Okta verify (work VPN), Symantec VIP (bank), and the Steam app.

And some other very nice to haves:

  • Signal messenger
  • SSH client
  • Libby app
  • Organic Maps

I can find workaround for the rest.

That said, wouldn't it just be easier to uninstall the apps that cause distractions?

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

Privacy guides is the forked project by the original contributors.

You mean Connecdicud.

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

Where's Nevada? And Montana?

you hand picked 2 peices from that whole page. The first one when you read the example below doesn’t even fit your case, so you left that out.

Words have meaning given context, I pointed to the definition that fit the context. When talking about wealth and assets, "money" means anything that could be easily converted to cash. I didn't copy the first because it wasn't relevant to the context.

Then you had to do mental gymnastics to make the second one fit.

I provided two to drive home the point.

How about an example. If I said, "how much money does Elon Musk have?", that would obviously include his stocks and whatnot because he probably only has a few million in actual cash, if that. If you ask how much money I have on the street, I'd assume you're talking about cash in my wallet, or maybe cash in my checking, and I wouldn't include my stocks or even savings balance.

Context matters a lot.

But when conversing with normal people, you will be hard pressed to find people who agree.

Are you saying that if I asked how much money you have in your retirement account, you'd say $0 because you only have stocks? If so, that's really weird.

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

My vote is Podman with an immutable distro, like OpenSUSE MicroOS or Fedora Silverblue. Here are my reasons:

  • rolling base, with very minimal footprint, so you don't need to worry about upgrades
  • podman runs proper rootless containers, so you get better security vs docker, which tends to run as root (breaking out does less damage if you manage permissions properly)
  • deploying a new service (or moving a service) just means copying configs and running, no concerns about what the host has
  • there's nothing special about the host, so if MicroOS or Silverblue are abandoned, just copy the configs and data to a new host

It's a little more work to set up, but once things are running, it's drama free. And I think that's the best thing to optimize for, keeping things boring is a good thing.

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

If we're going to change the name, it should be the department of the military/armed forces.

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

That is basically Schrodinger’s cat

No, it's not.

Schrödinger's cat thought experiment is about things where observing state will impact the state. That would maybe apply if we're talking about something unique, like an ungraded collectible or one of a kind item (maybe Trump's beard clippings?) where it cannot have a value until it is either graded or sold.

Stocks have real-time valuations, and trades can happen in near real time. There's no box for the cat to be in, it's always observable.

money

Look up the definition. Here's the second usage from Webster:

2 a: wealth reckoned in terms of money

And the legal definition, further down on the same page:

2 a: assets or compensation in the form of or readily convertible into cash

Stocks are absolutely readily convertible to cash, and I argue that less liquid investments like RE are as well (esp with those cash offer places). Basically, if there's a market price for it and you can reasonably get that price, it counts.

When my stocks go down, I may not have realized that loss yet from a tax perspective, but the amount of money I can readily convert to cash is reduced.

Why would you go to what's most likely your router?

 

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.

view more: next ›