Hacker Newsnew | past | comments | ask | show | jobs | submit | ranger_danger's commentslogin

I was hoping this would talk about the hordes of ungrateful users demanding more and more free labor from the unpaid volunteers of open source projects, but I guess we still don't know how to deal with that properly.

> required branding, logos

I'm no lawyer but I don't think the AGPL says you must use the same branding in a fork, in fact most hard forks tend to prefer changing it in my experience, as the original branding might be trademarked and so they can't legally use it themselves without permission, and/or they just want to distance themselves further from the parent.


I'm assuming this is related to the previous drama back in 2020:

https://lwn.net/Articles/833233/

Apparently TDF wanted to host LibreOffice Online for free, when it had previously been a source-only project. Collabora didn't like that as they did 95% of the development and wanted to be able to sell support for their own version, but they didn't want to be competing against TDF's version at the same time.


I can understand Collabora not being jazzed about it, but is there anything in the license that would prevent a third party who is neither Collabora nor TDF from doing the same? I mean, it's one Dockerfile away from anyone doing it, right? May as well be TDF who distributes an official binary.

I don't think so, I think it's more about TDF considering their involvement at that point a conflict of interest.

April Fools.

The description doesn't make sense either... like "Color-word interference at maze decision points", but there are no colors (or words) at the decision points.


Mandatory Fun (TM)

It's a bit confusing. QVector in Qt 6 is an alias to QList, which has now been changed to work like QVector did.

https://www.youtube.com/watch?v=nSFIFlLpsTQ


Even if you're flying commercial, wealthy people can just pay Perq Soleil $250 a pop to waltz them through the employee line with no wait.

Some OCR solutions do change the original file, like OCRmyPDF. They take layers that were just images before and replace it with text layers so that you can search the document.

That isn't OCR, but an application of the resulting output of OCR. Again, a signature on a PDF or any type of file doesn't prevent you from reading it. (It also doesn't technically prevent you from changing it, it just enables the detection of changes to a particular file.)

There's nothing about PDFs or image formats that prevent anyone from doing OCR. The reason construction documents are difficult to OCR is because OCR models are not well trained for them, and they're very technical documents where small details are significant. It doesn't have anything to do with the file format


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: