- Yes, the privacy infractions listed by esbranson are accurate.
- But we don't have an alternative right now.
- But something better is coming! It's totally right around the corner!
I'm very pleased to see dissatisfaction of the form "this isn't good enough; here are ideas for incremental improvements to it", but have totally lost my patience with the far more common "this isn't good enough; we should do nothing instead".
I've noticed as well, it's quite common that when a well-constructed solution takes much more time (and may be harder to identify) than an quick fix, proponents of the quick fix will claim that the 'do it right' folks are actually saying we should do nothing.
In my view, "partial solutions piled on partial solutions" is just life as a human being, where the alternative to that is not perfect solutions with no piling required, but rather no solutions. And yes, it is just like software, where incrementalism is also the better approach, in my view.
> proponents of the quick fix will claim that the 'do it right' folks are actually saying we should do nothing.
We don't think you're actually saying we should do nothing, just that it's the common end result, despite your best intentions.
And in the sphere of politics in particular, I think well-meaning people who really do want better solutions are often used by more cynical people who really do want to do nothing, for their own ends. Like the tax software industry lobbyists, in this case. Or like how old school environmentalists often find themselves aligned with fossil fuel industry lobbyists when it comes to building renewable or nuclear power generation, or transmission lines.
I don't begrudge people their dislike of partial solutions, I just don't subscribe to the same strategy.
I don't think the person you're responding to is a perfectionist. He just has a different view on how to improve things.
These aren't intractable, or even difficult, problems to resolve. Literally the only thing you have to change is some text.
The corollary to this is that the text is difficult to change for precisely the same reason that people dislike it: it holds legal baggage. If it were "just" some text, you could ignore it. But it's text that is related to contracts and agreements that would need to be renegotiated and audited and more I'm not thinking of.
Progress must include work: otherwise it is no longer progress.
My objection isn't to your opinion that we should make progress or change, it is to trivializing the complexity of that change.
Don't make perfect the enemy of good. The rent-seeking of tax preparation businesses is a bigger problem than these privacy issues. That doesn't mean those aren't also a problem. (And I'd be shocked if Intuit has a less problematic set of terms with respect to privacy...)
But what the IRS is doing here is the correct prioritization of problems to attack.
> But what the IRS is doing here is the correct prioritization
I read this as: "saving money, and keeping it out of unscrupulous hands, is more important than preserving our privacy and freedom". I don't agree with that, and you shouldn't assume that others agree with your take.
Indeed, I assume my take on that trade-off is the less popular one amongst the commenters, and perhaps also the readers, of this thread. But I do think it is the far more popular view among the population at large. And part of the reason I'm commenting here is to point that out.
The government saying "we are being more scrupulous than TurboTax" from the start, with a clear plan to improve is really only net gains. And the normal objections about things being worse because government don't really apply, since the IRS ultimately needs and has this information anyway, the risk is just them sharing it.
There's no justification for the IRS needing higher security than free fillable forms or normal turbo tax to deliver a similar self prepared efiling, so they are repeating the same crime the next level down, choosing a private system to provide something that benefits the IRS and is of negative value to the tax payer themself.
They literally have an alternative that they've already rolled out. And they've stated the reasons they can't use the more modern IDP yet. What's so hard to understand about a v1?
Do you have any evidence they're even working on this right now? Last news I heard was 2 years ago when they promised ID.me was a temporary solution for that tax season, but it sure looks like that was to make the public happy, and ID.me is here to stay.
Note: This isn't an argument against releasing the tax tool, I'm just commenting on the login.
IRS functions in general when conducted via paper or electronically via existing third parties also do not have to this level of identity assurance, so its kind of hard for me to believe that this is a hard minimum for the function. That justifies compromising privacy.
> Login.gov’s identity verification process does not currently conform to the IAL2 specification because it does not include biometric verification.
https://www.login.gov/partners/our-services/
> Login.gov continues to work toward achieving certification of compliance with NIST’s IAL2 standard from a third-party assessment organization.
https://www.login.gov/policy/how-does-it-work/
https://developers.login.gov/overview/
https://developers.login.gov/attributes/
> In FY 2024, Login.gov plans to offer a solution that complies with the IAL2 level of NIST 800-63 Digital Identity Guidelines.
https://www.login.gov/docs/login-gov-roadmap-november-2023.p...
Maybe not, but it absolutely makes sense for me to ignore this pilot until/unless they stop using something like id.me.
If not wanting to have my data exposed to yet another data broker makes me "super-privacy-sensitive", then so be it. As currently implemented, this program is simply a nonstarter for me because of the use of id.me.
I am immensely disappointed because I really want to be able to file my taxes in the way this program is aimed. Well, what I actually want is for the IRS to compute my taxes for me and send me a bill, but this would be better than nothing.
I'm also disappointed that I can't use this this year, because I'm not in one of the pilot states. But that's what makes it a pilot program! It's explicitly not intended to be used by everyone at this stage.
If this were to become required for everyone, and still leaked tons of data to a third-party at that point, then I would be right there with all of you that it's unacceptable. But we're far from that point.
Some people just can't be pleased.
False and false. No wonder you can't understand?
I will never participate in facial recognition to file my taxes. Never. I'd rather go to jail.
I've filed online in a foreign country and it was a breeze. California as well... breezy enough. Neither required privacy invasion by a malicious third-party.
It's time to ask yourself, what exactly are you rooting for here? Your creepy insults come off as very self-serving.
I'd ask you to consider how the companies with the dominant products in this space afford the "file for free" products that most people use. Perhaps it is altruism? Or maybe it's the normal way that companies offer free products that collect a lot of personal information, by profiting off that data.
I'm incredibly sympathetic to people here who don't want to personally use this until it is no longer using ID.me (I may well make the same choice if this were available at all in my state this year), but I'm incredibly unsympathetic to criticizing this pilot program for not waiting until this problem (which the vast majority of people don't care about) to be solved.
It is available in my state but does not handle some detail (this year) I need. But still I won't touch it with a ten foot pole with F.R. etc, and not going to be chastised for saying so.
It's not like complaining here on HN is going to influence even one percent of the non-technical public anyway. And I learn things from others griping. :-D
For paid, professional preparers (who don't use TurboTax, but rather commercially available software designed for practitioners who prepare dozens or hundreds of returns), the security requirements are higher, even if not quite IAL2. The IRS has worked for a number of years now on a "Security Summit" in concert with all the pro software vendors to tighten up their security, resulting in drastically less filing fraud than in previous years. By "filing fraud" I mean filing returns using a false identity, not simply reporting wrong income or deductions.
They’re a government agency. Especially for a voluntary pilot, it makes no sense to lower standards that way.
Again, they already accept efile from providers that do not follow these standards. There's 0 benefit to upping the requirements here.
No evidence of this happening. If anything, the pilot is proving they made the right call. It’s doing well despite ID.me.
Are you confident login.gov will be caught up and avaialable by next filing season and if so based on what?
Your cite at [3] above (thanks!), is dated Feb 2022, and doesn't have a timeline, but also sort of implies that login.gov should be ready by the "next" tax season (Feb 2023), when it says "While Login.gov is not expected to be ready in time for use by taxpayers during the current tax season…"
So this is now the third tax season since then that login.gov is still not available. What leads you think it'll be available next filing season?
(Note: I am not saying it may not make sense to move ahead with the pilot in parallel anyway, instead of blocking on waiting for auth solution work. Certainly in a normal industry software engineering scenario, parallel development is often better than blocking. I don't really have an opinion here. I do wonder what the budget allocation to login.gov looks like and if it's really being considered a necessary component of this product or not…).
[3] https://fedscoop.com/irs-to-adopt-login-gov-as-user-authenti...
Login.gov does not provide a sufficient level of identity assurance (IAL2 [1]) to serve as the IDP for this pilot and IRS functions in general (ID.me liveness check and facial recognition). IRS is working with Login.gov to upgrade Login.gov to deprecate ID.me for this purpose [2] [3].
Would it make sense to not proceed with this pilot until this was ready? Certainly not; Login.gov will catch up and meet IRS in the future as Direct File expands next filing season. Very similar to when Social Security Administration (ssa.gov) transitioned from ID.me and their internal IDP to Login.gov.
(Login.gov partners with USPS to perform in person identity proofing for those who cannot perform remote proofing via a mobile device)
[0] https://news.ycombinator.com/item?id=39691325
[1] https://pages.nist.gov/800-63-3-Implementation-Resources/63A...
[2] https://news.ycombinator.com/item?id=30430851
[3] https://fedscoop.com/irs-to-adopt-login-gov-as-user-authenti...