Weird. Other than how it used to choke when there were conflicts (and all uploads stopped until that was fixed) I haven’t had any issues like that. Guess I’m just lucky.

I’ve had pretty good experience with Nextcloud’s instant upload. The only time I’ve had it shit the bed was ages ago when it would occasionally get stuck on a conflict, but that hasn’t happened in a long time. Pretty much all of my image folders (camera/DCIM, Screenshots, Downloads) get synced. The only annoying thing was when apps would suddenly change where they download to and I’d have to reconfigure yet another sync folder, but I can’t really fault NC for that.

Mine is set to upload and keep a local copy and only do a one way sync (phone to NC). Not sure if that causes less issues than a 2 way sync or deleting the local copy after upload?

I suspect zram’s swap device only consumes RAM when it actually contains swapped pages, but I don’t know for sure. Can anyone link an authoritative statement on this?

I’m wondering the same. I haven’t read anything authoritative, but it definitely seems like it only consumes the RAM it’s using. Otherwise, it wouldn’t be able to create block devices that exceed the physical memory. I started to wonder when I had it set to 50% (4 GB) and gave it a stress test. The 4 GB it allocated filled up but was compressed to just about 1 GB, so I thought “surely this isn’t wasting 3 GB of RAM to hold 1 GB of pages.”

The guidelines I’ve read seem like there’s some guesswork involved in the planning. Basically you can make the zram device as large as you want so long as the compressed data is less than the physical RAM (not all pages compress equally as you mentioned).

I’ve since bumped it to 200% of system ram (16 GB), and I think that’s probably good enough for my use cases. I’m seeing about a 4:1 average compress ratio, so I could go higher, but 8 GB has been plenty usable up until now. :shrug: I also left the original swap file in place with a lower priority as a spillover (I’m not really missing the 4 GB of disk space that uses, so might as well keep it).

Yeah, I’m still tweaking things and just kindof came to the same conclusion I need to bump it up.

I was assuming that it thick-allocated the RAM for the compressed swap block device, but it seems to be dynamic now that I’ve read deeper into it. I just bumped it from 50% to 350% (basically one extreme to another).

I haven’t really watched usage since I dug it out and wiped it, but it mostly depends how many tabs I have open at a given time. It’s mostly used for web browsing, web apps, and basic productivity software (Thunderbird, Matrix, LibreOffice, etc).

When I used it last in late 2022, it was typically using most of its memory (excluding filesystem cache) keeping a bunch of browser tabs open.

Yeah, I found that out when I was using my old phone with T-Mobile. It was listed as supported, and it mostly worked, but there was at least one LTE band it didn’t support.

T-Mobile uses multiple bands in the same area: one higher frequency, higher bandwidth, lower range one for fast data and a lower frequency, lower bandwidth higher range one to fill in the gaps. My phone didn’t support the lower frequency one so I would lose coverage if I was too far away from a window in my house (despite living close to 3 towers).

Not to mention, they can and do reallocate spectrum periodically so while you may be fine for a while, if they reallocate and the device doesn’t support the new bands, you may suddenly lose service.

TL;DR: If it’s listed as Verizon-incompatible, treat it as such.

It should work, technically, but there’s no guarantee. While Verizon shut down their CDMA network in 2023 and everything uses 4G/VoLTE now, it may have other limitations that prevent it from working as expected.

You’d need to make sure the LTE bands it supports are used by Verizon in your area. If it doesn’t support the bulk of Verizon’s bands, you may find yourself (artificially) without coverage.

Verizon may also refuse to allow it if it’s not on their compatibility list (though you can possibly SIM-swap into it from an already activated device). It’s been a while since I dealt with them, but from memory, they’re pretty strict about what devices they allow on the network.

I’m sad I’m just now learning about Twin

I rarely go to Walmart. This is from the local Kroger (grocery store).

Good. May other retailers and grocery chains follow.

I hate those things - they treat you like a thief by default. I rarely use them and prefer to wait in line for the 1-2 cashiers, but I did the other day because I only had a few bottles of water to check out, and it was unsurprisingly horrible.

Scanned and bagged all my stuff. More slowly than I’d have liked, but otherwise uneventfully. I unpocket my wallet to get my shopper’s card and debit card out. “Oh no, you didn’t!” the machine said as it called for backup. Cue waiting 3-4 minutes for the attendant to get to me.

The machine asked the attendant if I was stealing and showed a replay of what it assumed must be me trying some Ocean’s 11 level of grand larceny. In the video? It was me getting my wallet out to pay.

Absolutely no time was saved. Nothing was more convenient, and to top it off, I was once again accused of stealing by a bathroom scale with delusions of grandeur.

Dude, it’s your platform, Meta.

I was gonna say…“just stop selling them the ad space”. Like, wtf?

It’s because your Linux PC is doing what you want it to do, and your Win 11 PC is doing what your employer + Microsoft wants it to do.

Can confirm, but depending on the VPS, your traffic may only be metered in one direction. Mine only meters egress, not ingress, so it’s not too bad if I want to use my media server.

All of mine use bind mounts so I can just tar-gz the whole deploy folder for backups and migrations. For volumes that connect to remote shares (SMB, NFS, etc) I use named volumes and let Docker take care of their lifecycle.

If named docker volumes would let me specify the local filesystem location, I’d use them. As-is, I rarely do.

My Kobo has (er, had) Pocket support, so it was nice, in theory, to save something to Pocket in FF and have it sync to my e-reader. That said, it was kind of glitchy and a lot of sites didn’t seem to work well with it (typically documentation pages for things like Oracle, etc that I’d want to save for offline reference).

I looked into it, but more for development purposes than installing it onto anything.

Seems like it would be easy to develop for, but the ecosystem seems to be pretty locked down due to the permissions model. There’s some ability to jailbreak devices, but it’s not a huge list of supported models.

For basic apps it’d be fine. But if I wanted to make custom applications for SMS, use bluetooth, make a new default dialer (e.g. to add SIP dialing), etc, it wouldn’t be possible since only OEMs can “bless” those. Even the next permission level down (Privileged) requires the apps to be signed by an authorized KaiStore.

Since my goal at the time was to make a lightweight Meshtastic client, I just gave up since I wouldn’t have the necessary permissions to make it work.

But I’m surprised at this laptops performance since I got it off an eBay business auction and not for gaming.

Same. This thing is amazing. Granted, I’ve always been a Thinkpad fanboy, but this is my first “new” Thinkpad since my T420.

Which settings? I’m replying from a 2019 X1 Carbon and have that in my Steam library.

[Currently playing Bioshock 2: Minerva’s Den via Proton.]

Then you really should list all of the secondary functions you plan to add to it, make sure they understand what those are, and agree to each of them: full disclosure.

If you do something on it that could get them in trouble, it’s their ass on the line, not yours.

Are you friends okay with you doing that? I would not be, especially if my so-called friend didn’t disclose the secondary operations of the device that’s in my home, on my internet connection, under my name.