brimble

33 ms·

301.
by brimble 5y ago
> This was the '60s and '70s, not the '20s and '30s, but it still seemed like another world, compared to today. Most food was local and full of taste, having been on a farm just hours before it appeared in the store.
302.
by brimble 5y ago
The pros seem to give less of a shit about live wires than I do, from what I've seen. And I already give fewer shits than I probably should.
303.
by brimble 5y ago
Oh no I forgot about badges! IIRC early on on iOS all you could do was set them to a specific number, so you had to track that state server-side (by having the app report when a notification was seen). There was no "take whatever it is
304.
by brimble 5y ago
I'd still be fine with 8GB, aside from Electron shitware eating 25+% of that for one app, and virtual machines being memory-hungry.
305.
by brimble 5y ago
Part of my job was tech support at the time. ME was notably worse than everything else. IIRC they also decided to screw around with placement of stuff on a bunch of settings screens for no reason, adding insult to injury.
306.
by brimble 5y ago
Well, sure. Logically, your language/libraries almost certainly present it as something resembling a persistent connection, though, probably not a ton different from how they present TCP (just with fewer features). However, technical
307.
by brimble 5y ago
OK, well, if that's true now, it wasn't true in the early '10s. Unless their API docs at the time were simply lying.
308.
by brimble 5y ago
Seems wrong to edit this in, so I'll make this post for lookers-on to see what creating a reliable push messaging service looked like in the early '10s: 1) Your app needs to register with Apple to get a push token, using the app&#
309.
by brimble 5y ago
If you had certain scale assurances—a set number of apps you're sending to, never more than low-five-figures pushes in a batch, never overlapping sends at the same time, et c.—it could be a lot simpler because you could skip most of th
310.
by brimble 5y ago
My recollection is also that local notifications didn't exist yet in 2010 on iOS, or had just been added. I tried to confirm it but it's actually pretty hard to find that information, it seems. Could be wrong. But, I was heavy i
311.
by brimble 5y ago
I built, all on my own, a dual-platform multi-app on-demand push notification service around the same time. I can assure you, Urban Airship was not providing "absolutely nothing". If they hadn't been so expensive, we'd h
312.
by brimble 5y ago
You're already being recorded by a dozen surveillance doorbells and cheap outdoor cameras when you walk outside your house, in a normal middle-class neighborhood, these days :-/ For whatever reason, a bunch of other tech-crap has
313.
by brimble 5y ago
> And in any case, current theory suggests that the sun will expand in the next few hundreds of millions of years making Earth uninhabitable to current life on Earth. It's the brightening, more than the expansion, that'll do it
314.
by brimble 5y ago
I'm convinced this is why so many rich folks have been buying land and citizenship in New Zealand. It's one of the nicest countries in the world that's also very hard to get to, without resources. They're preparing for
315.
by brimble 5y ago
I think months or even a year is fine—longer-term deals, especially if tied to a whole catalog, start to look too much like ownership.
316.
by brimble 5y ago
> every time it does get touched seems to end up needing half a day to untangle everything. This is exactly why I run everything in docker :-) One shell file or docker-compose file per service, and each concisely documents exactly what&#
317.
by brimble 5y ago
> in a small town of 200-300 people/very rural area, I take a different approach of course Hell, in a town that size, you know the mentally unstable folks and might even enjoy chatting with (some of) them if you see 'em at th
318.
by brimble 5y ago
Oh good lord, I meant to write "I've not had a problem with them." Jeez. Too late to edit now. That is, Jellyfin's been fine for me but it might only be because I've been lucky, since I haven't tried a ton
319.
by brimble 5y ago
If you're running it in docker, just backup the config and cache dirs and try the new version. If there's a problem, roll back. If that breaks (probably not, but maybe), restore the backup, then roll back. If you're not run
320.
by brimble 5y ago
I recall the "zbar" library being (relatively) easy to integrate and working damn well out of the box, on both iOS and Android, back in 2011 or 2012. I'd expect it's gotten even easier, if anything. It's been a whil
321.
by brimble 5y ago
I've got about a dozen (yeah, I know, not a lot) anime series on my Jellyfin, and also prefer subs in nearly all cases. I've had a problem with them. But, if someone's got something that's already working, they should pr
322.
by brimble 5y ago
Different niches. Jellyfin's a server first, with a built-in (but I think, technically, removable) web UI, and optional clients for a variety of platforms, including set-top boxes like Roku and Android TV and (I think) Apple TV—and Kod
323.
by brimble 5y ago
> That's an unfortunate holdover from it's origin as an Emby fork. Unfortunate? My initial guess on first contact with the project was that it'd be some Node thing. I was so relieved to see it wasn't. My unkind but
324.
by brimble 5y ago
Indeed: #/bin/bash docker run -d \ --volume /opt/jellyfin/config:/config \ --volume /opt/jellyfin/cache:/cache \ --net=host \ --restart=unless-stopped \ jellyf
325.
by brimble 5y ago
We ought not allow production companies to own distribution channels (and vice-versa), nor long-term exclusive deals with distributors. That's how we solved this when similar issues arose with studio ownership of movie theaters—those r
326.
by brimble 5y ago
The Roku app is tolerable (so, about as good as anything not from one of the companies that's big enough to gain access to the lower-level SDK) The Android app works really well on a Shield, and is much more pleasant to use. Can't
327.
by brimble 5y ago
Is it not entirely normal for a version currently or recently under active development to be easier to confidently work with than something you have to pull out of mothballed status? I know good practices improve that situation (the "n
328.
by brimble 5y ago
Big Sur should see at least another 18 months of support. Admittedly, that's just guessing based on past behavior, not a guarantee, which does kinda suck, but in fact it will probably see that much more support. Will likely remain safe
329.
by brimble 5y ago
I just checked and I'm on Big Sur. It's the reboot, for me. It's just inconvenient enough that I put off upgrades for a long time, usually. I usually apply iOS updates promptly, because it's much easier to say "yes&
330.
by brimble 5y ago
Steps are more convenient if you own a smartwatch or health-monitoring watch. Most people don't ("but I never see anyone without one!" yes, you live in a tech-hub bubble), so yeah, time would be easier.

More ›