FateOfNations

It's more that they want to disaggregate the customer service and tech stack responsibilities from the financial ones, with the profits split accordingly. At least in the US, Chime and other "banking fintechs" do have real banks underpinning them (The Bancorp Bank and Stride Bank, in Chime's case). This new the three-way relationship (customer-"fintech"-bank) can present new types of risks, and there's definitely room for overhauling the rules that regulate it, but it isn't an inherently bad business model.

While Chime, the company, isn't a bank, they do resell banking services. They are functionally value added resellers for The Bancorp Bank, N.A. and Stride Bank, N.A.

Seems like governments, at least ones of the size under discussion here, are big enough to have a general services agency run a consolidated data center for the rest of the government, allowing individual agencies/departments get similar benefits of outsourcing to a commercial entity.

It also would essentially have blocked all traffic enforcement cameras (red light, speed, bus lane, school bus passing, etc.) too.

Not Invented Here Syndrome?

Rewrite the anecdote with the truck racing to the supplier to make the pickup on time.

The same attackers are releasing the database of personal information separately (for a fee).

That said, Sweden takes a different approach to PII, so most of that information would have already been public. You can generally just look up any resident and their ID number and other biographical details in a public directory (among other things… their tax returns are also public records).

Thankfully no signatures involved. You roll up, swipe/dip/tap your card in a reader on the gas pump, enter your postal code (archaic security measure from the pre-chip card era), wait a few moments for the electronic authorization (they pre-authorize an amount in the $75-150 range), then pump, and leave.

If you are paying cash, you generally have to go inside before pumping and prepay, and then go back inside afterwards to get your change, if applicable.

apt is a package manager. It's only relevant if the system uses it to manage it's packages. Red Hat based distributions, for example, don't use apt. Embedded devices typically don't manage packages on an individual basis, rather updating the entire distribution via "firmware updates".

Data point: Albertsons/Safeway/etc. is rolling out new card readers that have a camera in them. Software support likely isn't in place yet, but that's definitely something they are thinking about long term.

Generally the hangup/timeline is with the state government, not Apple/Google.

Technically, the web server can do content negotiation based on Accept headers with static files. But… In theory, you shouldn't need a direct link to the RSS feed on your web page. Most feed readers support a link-alternate in the HTML header:

<link rel="alternate" type="application/rss+xml" title="Blog Posts" href="/feed.xml">

Someone who wants to subscribe can just drop example.com/blog in to the feed reader and it will do the right thing. The "RSS Feed" interactive link then could go to a HTML web page with instructions for subscribing and/or a preview.

On iOS there is the concept of "Managed Apps" that is appropriate for a BYOD scenario. They are info sandboxed and can't share information (either direction) with unmanaged apps. That would count as an MDM enrollment, if you are looking for it.

The problem is dealing with those other 5% of calls. If you are in a 5% situation, you're seemingly SOL these days.

At some point customer service died. Businesses of seem to no longer be interested in dealing with customers. Good customers come in all shapes and sizes, and often don't exactly fit a cookie cutter. It's frustrating to see businesses just cut and run the moment something becomes a problem that needs more than a series of pre-scripted responses to be resolved.

The reason Expensify does that is because they want/need access to the cookies from the login flow. The in app browser provides the hosting application access to those, but they can't access Safari's cookiejar. The modern way of doing it is to put the login in Safari (or iOS's dedicated "in app browser for logins") and then redirect to something like expensify://login_complete?token=xxxxxx, which pops back over to the app. This is mostly tech debt on Expensify's part, but it might not solve the Edge vs. Safari issue.

I wonder what iOS Edge does which iOS Safari doesn't do

Being a "Managed App" through MDM/Intune. Typically it's used when installing corporate apps in a BYOD scenario. The managed apps are isolated from information sharing with unmanaged apps, e.g. policies can be applied preventing copy/paste, access to Files.app, etc. It (and it's isolated storage) can also be remote wiped without nuking the whole device. Edge.app still uses the Safari rendering engine, etc. like is generally the case with 3rd party browsers on iOS.

You can't do this with Safari.app unless the whole device is managed, which doesn't work well for BYOD.

Inspect containers leaving the country for contraband. Require shipping companies to do KYC. Require documented proof of ownership for vehicle exports.

What counts as “a view” has pretty much never been particularly straight forward. The question is why YouTube can't just say, “Yes, in early August we made some changes to how views are counted.”

All the available evidence seems to suggest that this is an accounting change, rather than a change in viewer behavior.

Looks like a lot of small ISPs have been procrastinating about getting their robocalling mitigation/compliance policies implemented, and didn't think the FCC was serious about the “Final Warning”. They'll get their stuff fixed eventualy.

All the companies have a direct connection to the phone network in the US. The FCC is cutting them off from the US phone network because they have failed to adopt robocall mitigation measures.

I don't get it… isn't up to the landowner whether they farm corn, soybeans, or solar radiation? The government may provide different incentives for each, but AFAIK, they aren't forcing a choice.

It isn't centralized, but the emerging mDL/mID (ISO/IEC 18013-5) + Digital Credentials API (W3C) standards do enable sharing a “this device contains a secure credential for someone over 18 years of age” assertion, cryptographically signed by a government agency. Critically, this doesn't require sharing any other personal information.

It was even done in consultation with the Dahl estate/family, although they choose to ignore Roald Dahl's professed opinions about editing his works.

Our local Panera has this. It's popular with the MLM ladies.

Functionally, it can do a lot of the same things as SWF/Flash. Can do animations (see article) and it's scriptable using JavaScript for interactivity.

Minor exception: https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootk...

interesting, that's specifically in the Spanish localization.

A "Windows Subsystem" is a concept that dates back to the original Windows NT line of operating systems. Historically, there've been a number of supported "Windows Subsystems", essentially APIs for the kernel. In Windows NT 3.1, there were multiple subsystems: Win32, POSIX, and OS/2, plus a separate one specifically for security.

https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem

While WSL2 isn't implemented as an architectural sub-system (it uses a VM instead), WSL1 was far closer to the original architecture, providing a Linux compatible API for the Windows kernel.

Your bank/credit/debit/etc. card is a “physical token with a crypto key that is protected by a password and tied to one's bank account”. FIDO and EMV even both use the same underlying ISO/IEC 7816 and 14443 protocols for communications.