If it was be that simple. In that case I would have to go to the bank for every transaction/payment I want to initiate online. Banking app doesn't work for jailbroken devices. Using PC to access banks website works, but transactions still require 2FA and they don't support any other 2FA flow except the one in the app.
There's always a workaround. There are banks with far less annoying root checking and you can just switch. Many banks allow SMS or a physical authenticator for web banking or 3DS 2FA. There are also many was to bypass root detection. If your main problem is 3DS 2FA for online card payments, get a proxy card.
"you can just switch" and yet then you have to contact X people and change Y contracts that are related to your prior bank account. It is not that simple.
Plus nothing ensures the bank you switch to won't up their "defenses" in a week.
I never said it was trivial, I said it was possible. In many places, it's actually very easy. In others it takes some work, but we're talking about de-googling your life, having to put in some work is already implied.
At least around here, I can walk into a bank, sign a few papers, then that bank coordinates with my old bank to transfer all my direct debits, move all my money and notify all my periodic creditors (employer, social security, tax office...). Peer-to-peer payments (like splitting bills with friends) are usually done by alias (phone number or email) on our instant payment scheme, not by IBAN, and my new bank will take care of rerouting that too. And if for whatever reason someone has my old IBAN and tries to send me money in the future, they'll get a rejection and will just have to ask me for my new one, no big deal.
As for "in a week", come on, you're just being intentionally annoying. Obviously there's no guarantee. If they don't have root detection now, after everyone has had it for a decade, there's probably a reason and they won't implement it any time soon. And if you're just supremely unlucky and they actually do it right after you switch, oh well, you wasted and afternoon. Definitely less time wasted than trying all the million different root hiding techniques that probably don't work anymore.
You don't have to go to the bank for every transaction, you can just go there once to close out your account and open one somewhere that doesn't require that.
Depends though what you mean by "do not use Google". Having an Android phone with a Google account logged in will not affect you much. If they would block one account you just create another.
Having all your emails on Gmail and used for external services (bank, insurances, etc) is a different story though. I prefer to pay my email provider, at least they will care a bit more than they do for a free account...
I'm surprised, most banks I've come across force sms or phone-call 2fa only. A rare few allow generic TOTP authenticators, and maybe one or two has an app as an option. And I've only come across one bank that detects and warns for root access. Is there no "jailbreak hide" on ios?
In Poland it's SMS OTPs, bank app (heavily recommended and in some cases enforced by the bank) or additionally paid physical TOTP token devices. And almost all banks throw a hissy fit once you have some sort of vector of root detection left open.
SVGs also are mostly unsupported for og:image tags (dependents on the app/browser). I know it's supper specific and I am not even sure if open graph is standardized protocol or not, but it's used everywhere.
I don't mind the size, but lack of colors is annoying. If common icons where color-coded, like green to save, blue to download/print/export, red to delete, UI would be friendlier to use.
I think it is important to stress that both, color _and_ shape should be visible distinctive, and as you say it is important that the color palette is chosen in a way that even if the color does not stand out for a the color-blind person, the contrast stays visible.
Making everything monochrome is surly not more accessible, because there sure are people who find it easier to distinguish by color than shape.
Why in the world would colors discomfort you if you can't discern between them? Icons have until recently always been color coded. That doesn't make them a problem for the color-blind. You can look at the shape of the icons and read the text next to them. Would a pedestrian traffic light be better if it wasn't color coded? Would a white car be preferable to a red car?
> Why in the world would colors discomfort you if you can't discern between them?
Because pretty much as soon as one starts colour coding items in the UI, people start using the specific colours to encode meaning. If your UI requires someone to discern between the red and green versions of the same icon in your UI twice, congrats, you just lost 8% of male users!
> Would a pedestrian traffic light be better if it wasn't color coded?
If they weren't colour-coded, they would have to be differentiated by shape, and then when I traveled to Canada, I wouldn't have to guess whether the fancy horizontal traffic lights are ordered left-to-right or right-to-left
> Would a white car be preferable to a red car?
Even fully colour-sighted folks can't see red very well at night, so yes, white car > red car
Personal anecdote re the traffic lights: I thought "green light" was a metaphor until sometime my twenties, when a friend explained that the 3rd light actually is green to other people. It's always been a white light to me
With that line of reasoning we arrive at the conclusion that all graphical elements of an interface should be removed, as the blind cannot see icons.
> If your UI requires someone to discern between the red and green versions of the same icon
Color coding has never been about this, only when implemented wrongly. It is just an extra differentiator for GUI elements which are already differentiated by icon shape and text labels.
> Color coding... is just an extra differentiator for GUI elements which are already differentiated by icon shape and text labels.
In principle, I agree, but I do not believe I have ever used a software package that follows this philosophy. In practice, once you give people a tool, they are inclined to use it, and most projects only try and address accessibility concerns post-ship
Laziness is one of the three virtues (of a good programmer), but I think Larry didn’t anticipate the current situation when he wrote it:
”The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don't have to answer so many questions about it.”
> I imagine 90%+ is peered or hosted inside ISPs, not via transit
How hosting inside ISPs function? Does ISP have to MITM? I heard similar claims for Netflix and other streaming media, like ISPs host/cache the data themselves. Do they have to have some agreement with Steam/Netflix?
Yea netflix will ship a server to an ISP (Cox, comcast, starlink, rogers, telus etc) so the customers of that ISP can access that server directly. It improves performance for those users and reduces the load on the ISP’s backbone/transit. Im guessing other large companies will do this as well.
A lot of people are using large distributed DNS servers like 8.8.8.8 or 1.1.1.1 and these cansometimes direct users to incorrect CDN servers, so EDNS was created to help with it. I always use 9.9.9.11 instead of 9.9.9.9 to hopefully help improve performance.
The CDN/content provider ships servers to the ISP which puts them into their network. The provider is just providing connectivity and not involved on a content-level, so no MITM etc needed.
> 80% of new developers on GitHub use Copilot in their first week
I am not sure how honest this statement is. I remember typing something in an input which I thought was search, but no, it was AI search or something like that. Free copilot got activated on my account simply by submitting a search query. Statement may be technically true but it's target audience are investors and maybe higher management (someone is getting a raise or a bonus), not actual developers.
Not really, you should learn Typescript by learning JavaScript first. Then consider learning C#. Or if you want to focus on the back end side learn C# and skip TS/JS.
They are created by the same person but they are very different in my opinion.
TypeScript is "a tool" for JS, it is possible to compile without errors but still fail in runtime (e.g. wrong object type returned from API), on the other hand parsing JSON with C# will give you correct object type, it may fail if some properties are missing but it will fail at parsing call, not further down when you try to use missing property. In other words typing is not glued on top of the language it's core of the language.
reply