Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment More, please (Score 2) 34

I'm all for removing reliance on TurboTax, H&R Block, etc, though I do have friends and clients that are tax preparers. I think Direct File is very much a step in the right direction, though it will naturally cost money to wean the public off the current providers.
IRS stated through the GAO that the combined costs to develop and run this initial pilot ran about $25 million**. That's pretty steep, but doesn't seem particularly egregious for essentially breaking into and disrupting an entrenched industry. The running costs for Direct File were estimated at $2.4 million**, which will certainly go up as/if the program expands, but so will the amount of revenue diverted from tax preparers.

** These numbers are disputed. According to a GAO report, there were a number of additional costs that should have been included, particularly costs related to the Direct File pilot incurred by the US Digital Service (USDS, a technology unit that is part of the Executive branch of the government) that were not required to be reimbursed from IRS. USDS developed the prototype that was eventually developed into the Direct File program and also loaned 29 staff to the IRS to assist with building and running Direct File)
GAO report about IRS Direct File

Comment Economics (Score 1) 428

Interesting. The first thought that comes to mind is whether such bans/rules will be challenged under the Commerce Clause. Labelling requirements are probably fine, and outright banning them would probably pass muster (at least with the current judicial landscape).

Bit disappointing, though. While there are sectors and industries that are likely valuable enough to warrant domestic protection/incentives, is ranching really one of those?

Comment Nice (Score 1) 177

Wish I heard about this happening more often. Sadly, I suspect this is very unusual. Also, some scalpers may be turned off of doing this by such cases, but the more successful...middlemen...will likely absorb this as a cost of doing business.

Still, nice to hear of it happening at all. It's not like TicketsMaster has any desire to shut this crap down.

Comment Re:SPF should die in a fire (Score 1) 23

The problem with this approach is that by reflecting the incoming message to other addresses, you are re-sending it from a new server while still claiming the message originated from the original account/server.

Obviously, this will fail SPF since the entire purpose of SPF is to designate which servers are allowed to claim sent messages are from a given domain.

If you want to forward incoming messages to one or more other recipients, you need to generate a new message quoting the old one with the new origin being the original recipient. I don't really see a problem with this, outside of the forwarding mechanisms that attempt to use an external domain as a glorified alias for other email addresses.

This is just my stance on it, though, and perhaps I misunderstand why this is a bad thing.

Slashdot Top Deals

"Why can't we ever attempt to solve a problem in this country without having a 'War' on it?" -- Rich Thomson, talk.politics.misc

Working...