Indeed, and it’s useful to be aware of that.. things like pinger numbers. But I certainly would not cut the bank any slack for their oppressive mandate that excludes people without a mobile phone.
That’s not an ATM machine.
It’s not about the last €20¹. It’s about the last €18.45. How do you get €18.45 from an ATM?
Well, shit, that could be an answer too.. cashless banks could have a special kind of ATM that has no denomination limitations. Even my local grocer has a cash machine capable of dispensing all small denominations.
So there are several reasonable things they /could/ be doing, but there is no pressure on them to be competent.
¹ I will edit my post to make this more clear.
(edit) it just occurred to me this is a human rights violation. A very minor one, but against international law nonetheless. You cannot deprive someone of their property. UDHR Art.17:
- Everyone has the right to own property alone as well as in association with others.
- No one shall be arbitrarily deprived of his property.
The answer is in what you quoted: cash.
There should always be an option to cash out when closing an account. The ATM can get all but the last ~~€20~~ €19.99. It’s foolish and embarrassing that the bank cannot handle the remainder.. that they are so anti-cash that they refuse to have some petty cash around for micro transactions.
Or the bank could accept a small cash deposit. If the balance is €18.45, a customer should be able to deposit €1.55 so that they can pull €20 from the ATM. But cashless banks refuse to accept even the tiniest of deposits.
It should be illegal. It’s a kind of “binding”, where a business requires you to use another business. People should have a right to exit the banking system, full stop. Forcing someone to open another account as a condition to exiting (in effect) is absurd and denies people autonomy.
Apart from that, if a cashless bank insists on being 100% balls-to-the-wall anti-cash in their war on cash, they /could/ give customers who close their account a prepaid credit card funded with their account balance. Customer still has the problem of spending an exact amount but at least they could deal with it later, without fees eating away at their balance. They could do the split restaurant bill at a time of their choosing.
Worth noting that some banks are pushing this transition in a more subtle way. By gradually removing options from their web banking and making functions that are smartphone-only.
I’m not sure how it works but it may still conform to standards (just not conventional norms). E.g. consider eduroam which is common in EU schools. You need a special app for eduroam but it’s possibly combining various authentication standards with wi-fi standards. Before using eduroam I skimmed through all 1000+ SLOC of the bash script before deciding to trust it. I was revolted that I had to inspect all that code just to safely connect to campus wi-fi with confidence.
That said, I have no idea how wifi4eu works. It could be similar to eduroam and perhaps a FOSS app will eventually emerge. But until then, all we get is an all-rights-reserved copyrighted black box and no specs (AFAIK). So yes, it’s a shit show of exclusivity and privacy surrender nonetheless.
Yikes. I am disturbed to hear that. I was as well appalled with what I saw in a recent visit to a university. It’s baffling that someone could acquire those degrees without grasping the discipline. Obviously it ties in with the fall of software quality that began around the same time the DoD lifted the Ada mandate. But indeed, you would have to mention your credentials because nothing else you’ve written indicates having any tech background at all.
How have I made your point at all?
You have acknowledged the importance of having multiple points of failure. It’s a good start because the defect at hand is software with a single point of failure.
You're a bit incoherent with what you're talking about.
I suppose I assumed I was talking to someone with a bit of engineering history. It’s becoming clear that you don’t grasp software design. You’ve apparently not had any formal training in engineering and likely (at best) you’ve just picked up how to write a bit of code along the way. Software engineering so much more than that. You are really missing the big picture.
This has nothing to do with software design or anything else along those lines.
What an absurd claim to make. Of course it does. When software fails to to protect the data it’s entrusted with, it’s broken. Either the design is broken, or the implementation is broken (but design in the case at hand). Data integrity is paramount to infosec and critical to the duty of an application. Integrity is basically infosec 101. If you ever enter an infosec program, it’s the very first concept you’ll be taught. Then later on you might be taught that a good software design is built with security integrated into the design in early stages, as opposed to being an afterthought. Another concept you’ve not yet encounted is the principle of security in depth, which basically means it’s a bad idea to rely on a single mechanism. E.g. if you rely on the user to make a backup copy but then fail to protect the primary copy, you’ve failed to create security in depth, which requires having BOTH a primary copy AND a secondary copy.
This is a simple thing. If your data is valuable you secure it yourself.
That has nothing to do with the software defect being reported. While indeed it is a good idea to create backups, this does not excuse or obviate a poor software design that entails data loss and ultimately triggers a need for data recovery. When a software defect triggers the need for data recovery, in effect you have lost one of the redundant points of failure you advocated for.
When you reach the university level, hopefully you will be given a human factors class of some kind. Or if your first tech job is in aerospace or a notably non-sloppy project, you’ll hopefully at least learn human factors on the job. If you write software that’s intolerant to human errors and which fails to account for human characteristics, you’ve created a poor design (or most likely, no design.. just straight to code). When you blame the user, you’ve not only failed as an engineer but also in accountablity. If a user suffers from data loss because your software failed to protect the data, and you blame the user, any respectable org will either sack you or correct you. It is the duty of tech creators to assume that humans fuck up and to produce tools that is resilient to that. (maybe not in the gaming industry but just about any other type of project)
Good software is better than your underdeveloped understanding of technology reveals.
Thinking that a federated service is going to have a uniform or homogenous approach to things is folly
Where do you get /uniform/ from? Where do you get /homogenous approach/ from? Mbin has a software defect that Lemmy does not. Reporting mbin’s defect in no way derives and expectation that mbin mirror Lemmy. Lemmy is merely an example of a tool that does not have the particular defect herein. Lemmy demonstrates one possible way to protect against data loss. There are many different ways mbin can solve this problem, but it has wholly failed because it did fuck all. It did nothing to protect from data loss.
on your end and a failure of understanding what the technology is.
It’s a failure on your part to understand how to design quality software. Judging from the quality of apps over the past couple decades, it seems kids are no longer getting instruction on how to build quality technology and you have been conditioned by this shift in recent decades toward poorly designed technology. It’s really sad to see.
Exactly. You’ve made my point for me. Precisely why this defect is a defect. The user’s view should be separate and disjoint from the timeline. Lemmy proves the wisdom of that philosophy. But again, it’s a failure of software design to create a fragile system with an expectation that human users will manually compensate for lack of availaiblity and integrity. I know you were inadvertenly attempting again to blame the user (and victim) for poor software design.
It’s a shame that kids are now being tought to produce software has lost sight of good design principles. That it’s okay to write software that suffers from data loss because someone should have another copy anyway (without realising that that other copy is also subject to failures nonetheless).
Who cares?
Anyone who values their own time and suffers from data loss cares about data loss, obviously.
This is a serious question.
Bizarre.
Anything that is important to you should be backed up and/or archived. Relying on a third party social media app is folly.
This is a bug report on faulty software. If you have a clever workaround to the bug, specifics would be welcome. A bug report is not the place for general life coaching or personal advice. If there is an emacs mode that stores posts locally and copies them into a lemmy or mbin community and keeps a synchronised history of the two versions, feel free to share the details. But note that even such a tool would still just be a workaround to the software defect at hand.
The premise of the question is when the bank refuses you access to your money, which manifests in a number of circumstances. Receiving a check from the bank is useful only in scenario 1, and only possible in parts of the world that still have checks.