smileybarry

I remember how it needed specific telecom support to work at all, whereas iPhone needed carrier help for a subset of things like APNS. So for most of BlackBerry’s life none of the carriers here supported running one on their network.

> There is Windows Server Core which removes everything but a CLI, but you still have the normal login experience, you still have a "desktop" (no start menu, taskbar, etc), you can still launch normal Win32 apps... for the most part (task manager, notepad, and so on).

Yep, they've replaced nearly every UI with text (the login window is a TUI), though there's still some shell DLLs and the whole thing still uses a window manager. That's honestly for the best, since it allows you to migrate full installations with some UI-based apps to a Core installation with them intact.

> That said, with a bunch of modifications, NTDEV did get Windows 11 down to it's bare minimum, and text only to boot. So I guess it's technically possible, though not useful.

Windows has had a "text mode" since at least Windows XP IIRC, but it's really not that useful, if at all. Even for rescue operations you're better off with Windows PE.

> The core issue is that `EndpointSessionMapEntry` imposes no limit on the number of sessions. Consequently, an attacker can forge fake client IP addresses and port numbers , repeatedly creating new sessions until system resources are exhausted.

Aren't you just able to flood any DHCP server instead? PXE deployment already hinges on DHCP provision > PXE broadcast > download image > launch, you might as well just exhaust the DHCP server's pool by using all ephemeral addresses or spoofing MAC addresses endlessly.

Additionally, WDS is active only in-LAN and usually only on areas like employee office networks (i.e.: not listening on the servers' subnet, for example, unlike AD services). You'd need lateral movement to an "office LAN" to reach said WDS server.

Note the link may prompt Google Account re-auth, strangely it did on my work browser. Opening in incognito side-steps this.

> $99/year with no limits on data, as far as I can tell.

The limit is as much data as you have plugged in. Backblaze only backs up your currently-available data, with a 30-day grace for external disks[1]. IMO, if you have a computer with a 1TB drive, you'll probably use <1TB at all times, accounting for you not using the entire 1TB locally and your changed data probably fitting in the excess. (e.g.: 800GB used space and you change <200GB over 365 days)

1: https://www.backblaze.com/computer-backup/docs/external-hard... . Essentially, if you unplug an external drive for >30 days, that drive's backup will be deleted.

Wasabi used to be the cheaper option when B2 didn't offer variable free egress. B2 was basically "cheaper S3" as it still charged $0.005/GB for egress, while Wasabi was free egress (I think their upper limit used to be >1x your storage, so maybe that changed, or I'm misremembering?).

If your storage was fairly consistent, not tiny, and you intended to pull it regularly, Wasabi would come out on top. B2's egress change probably shifted the scales to favor B2 for those cases.

IIRC it used to just say “annual” in some words, then the actual terms included the obligation to pay 12 months or pay a cancellation fee. I remember (a while ago when this made headlines) seeing a screenshot of the plans without it being clearly underscored as “annual, paid monthly”.

> People will run their .net framework software until they literally can't anymore. If MS won't/can't support it, another way will be found

Yep, I'm sure there's at least some out there who switched to running off something like Mono on Windows to work around some unpatched .NET Framework issues.

I'd add that WPF was "don't bother" up until recently when WPF support was added. (Though I don't know if that means stock WPF or that it supports the breadth of WPF controls out there, and whether it requires WPF component vendors to make changes)

We have a(n enterprise) product that uses .NET 4.x for the UI, and I've explored moving to current .NET, however:

* Supporting some older OSes and requiring less system base updates is key

* There's a priority to keep installation size (relatively) small

* There's a (higher-up) notion of "if it works, why change it"

On top of that, some technical issues I've encountered (since resolved) and gave up on upgrading were:

* Up until relatively recently there was no "single executable" deployment

* For some part of Core's lifetime you had this weird deployment of DLL-run-by-EXE that's a dealbreaker for the software's security boundaries & requirements

* Huge executable size, until recently where trimming unused framework code was added

There was also some period of time where the .NET party line was "WPF is legacy, we don't support it on modern .NET" and our UI is already built in WPF. We couldn't move to something like WinUI due to supporting Windows <10 and even then, WinUI 3 increases your deployment executable's size by a lot. Thankfully they added WPF support in .NET 8/9.

I got that option via OOBE, not automated install.

Sadly I mean "code sent via SMS", which is one reason why I haven't automated much of the retrieval for these things.

Yep, while I like moving all snail mail to email, I hate that (almost) every single service now just sends a "monthly/quarterly report now available in your account area!" email. A rare few of them at least offer the option of just sending it attached (with the default being a useless reminder email), but most are essentially a chore, because nearly everything here uses phone+2FA as login rather than a password or passkey.

It does, I just made a Windows 11 Pro 24H2 VM for testing (with the stock ISO) and used the "domain join" option to make a local account.

> For example, aspects of the API just don't work as expected, like for some reason search and mention endpoints do not have support for long form posts (>280 characters)

At the risk of sounding blunt, they probably fired the people who actually built the API at Twitter and it's now (internally) in maintenance mode. They very openly don't care about giving other companies data -- even with the new pricey API tiers -- or making the non-app/-website experience good at all. I doubt any of the new item types -- Articles, ordered media in tweets, etc. -- even have an API exposed.

Should also point out that even if the model has Wi-Fi, it's optional. (Source: just bought one in EMEA) Even if you set it up, the app can't remotely activate it without the washer being pre-set to the "Remote Start" side of the knob.

I reinstalled a BLE inspect app to troubleshoot something, and I was shocked at the sheer amount of Samsung TVs (and I own none) I had to wade through to find my device. The fact they're all in discoverable mode at all times makes opening my regular Bluetooth just as bad, too.

I just bought one and yes, mine also comes with WiFi but it's 100% optional: all features are available in menus or physical buttons too. (Including the infamous rinse cycle the blog post mentions)

It's a European model ("SMV4HAX48E", I'm in EMEA) so it might differ by markets.

Even then, Apple also bind (an increasingly larger amount of) component IDs to the motherboard, so nowadays a stolen device can't (really) be used for parts either. (The display will not authenticate and Face ID & HDR won't work, in addition to a message showing that in Settings)

And to answer the obvious repair question -- yes, parts can be rebound to other motherboards etc., they just need iPhone Activation to pass first.

> and you can sometimes phish the Apple ID credentials from the victim, which is why stealing those devices is still profitable enough.

Yep, I always see "is this text legit?" posts with clear phishing URLs in iOS help groups on Facebook, posted by people who had their iPhones stolen and think it's Apple Support attempting to get it back.

Ah, if there’s one thing you should run very outdated versions of, it’s a PDF reader. Can I get a TIFF reader last updated in 2010 to go along with it?

Windows 8 shipped with build 8400 (apparently), so I assume this PDF reader is pre-UWP rewrite from one of the early Windows “8” builds, that were mostly Windows 7.

Ironically, Protobuf does have field options for "required" and "optional", but over a decade ago (I guess shortly after it was first introduced), Google added a huge "do not use required! validate required fields in your own logic!" warning to the docs, because a missing "required" field throws out the whole packet. (And when it's time to deprecate a required field -- it's way more effort)

We originally used "required" for fields that must be present and it screwed us over later due to that. Switched everything to "optional" with the code checking for those fields' existence instead.

+1 for NextDNS. Have been using them for years for blocking ads but also helped me troubleshoot some issues, as I could live track DNS queries by device.

Note the free plan is great for several devices as long as they’re not Apple. For some reason, 2+ Apple devices blow through the 300,000 query limit really easily. When I used a Pixel 2 I think it averaged 60,000 and fit in the quota with my other devices, and when I switched to iPhone it pushed the total over 300,000. But they’re cheap and definitely worth it.

Probably better to rename this to the app’s name + description, as this is a direct App Store link.

EDIT: Looking at their past submissions this even looks like their app, i.e. this is a “Show HN”.

Probably better to just do update signing, certificates rotate frequently and at some point you’re bound to run into an enterprise customer with a MITM / caching proxy.

I guess the worse part about S3 buckets vs domains is that it’s bound to AWS (would you maintain a dead AWS account with an empty bucket forever after you switched to GCP?), and potentially more expensive than domain upkeep. (Not really but there’s always the worry of keeping a cloud account with resources left unmonitored)

At least with a domain you can park it somewhere and pay a yearly renewal fee without worrying.

The QR codes aren't really single-use, my carrier reuses the QR code and you can move devices by removing the eSIM from one and re-importing the QR code on the newer. (The QR code is invalid so long as the eSIM is provisioned on a device, not necessarily powered on)

With the amount of "if cloud IP then block" rules in place for many things (to weed out streaming VPNs and "potential" ddos-ing) I wouldn't doubt that at all.

I know, but usually a lot of these have hobbyist plans. I wouldn't mind being throttled and QoS'd behind businesses for a lower price.