FateOfNations

It's less about paying for a service than thinking that you are a welcome member of a community and then suddenly finding out that you aren't.

> They provide a service

Codeberg seems to disagree about that point.

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.