Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Transparency and verification (Score 1) 42

Easiest solution is to issue employees a corporate credit card that they are responsible for. All reimbursable expenses have to be correlated against the copy of the statement issued by the credit card company to the corporation.

But what about cash expenses, you ask? Issue a per-diem for travel, and a periodic "here's your budget for IT refresh, whatever you don't spend, you get to keep."

My question is, what kind of receipt fraud are we looking at? Invented expenses that they're using to defraud the company, or real expenses that normally wouldn't be reimbursed that they're disguising as reimbursable ones?

Also, wouldn't invoice fraud be a bigger threat? Fake suppliers sending you real looking invoices in the same of actual suppliers, but with the bank details modified to point to the scammer's accounts instead? Instead of hundreds of dollars in fraud perpetrated by dozens, maybe hundreds of insiders (employees), you get tens, if not hundreds of thousands dollars of fraud perpetrated by outsiders trying to pretend that they're trusted suppliers. Or worse... an insider at your supplier deciding to doctor the outgoing invoice so they can skim money off the top...

Comment Not the open-source ecosystem (Score 1) 45

I don't think genAI is a threat to the open-source ecosystem as far as it's copying of FOSS code goes. The people looking for that kind of code wouldn't be looking for the source code for FOSS projects anyway. The threat, if any, will be from genAI code being contributed back to FOSS projects. Aside from provenance issues, it tends to be low-quality and buggy and will just increase the workload for FOSS maintainers without offering anything useful. Witness genAI offering a suggestion to a bugfix submission: https://social.hails.org/@hail...

Comment Re:Complete fallacy (Score 3, Interesting) 45

Thanks to Google LLC v. Oracle America, Inc., 593 U.S. 1 (2021), even relatively small pieces of code (such as function declarations in header files) must be considered copyrightable. It's possible they aren't, but the appeals in that case resulted in rulings that they were copyrightable, and the SC decision in favor of Google turned on fair use, not whether the code in question was copyrighted or not, so it can't really be used to stand for the proposition that the appeals courts got it wrong.

With AI-generated snippets, it's going to turn on whether the snippet is close enough to identical to the original code to be considered a copy and whether that copying could constitute fair use. I think any lawyer would tell you that's not the kind of thing you want to bet on in court. If the code's simple enough that it clearly wouldn't be a copyright violation even if it were nigh-identical, it's simple enough you're better off not using AI and having your engineers write the code themselves, and if it's significant enough that that's not feasible then it's almost certainly copyrightable and the fair-use argument is going to be an uphill battle for something that significant. Either way, you're better off avoiding anything where you don't know the provenance of every line of your code.

Slashdot Top Deals

"If I do not want others to quote me, I do not speak." -- Phil Wayne

Working...