Readit NewsAlternatively…
Huge fan of Reticulum, fixes some of my biggest gripes with Meshtastic. Shame it hasn't got as much adoption yet. For those looking for Meshtastic-equivalent things in the Reticulum ecosystem:
- Sideband: iOS/Android chat app (https://github.com/markqvist/Sideband)
- NomadNet: Desktop CLI chat app (https://github.com/markqvist/NomadNet)
- Rnode: Reference node hardware/firmware (https://unsigned.io/rnode/)
AFAIK and this may have changed, but at least in the US, AI-generated content is not copyrightable so it's effectively public-domain.
It's not that any content created by AI is not copyrightable, it's that work created solely by AI without human input is probably not copyrightable.
See also [1] mentioned in the framework linked by sibling comment, AI copyright is essentially a logical extension of this.
[1] https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...
0x62 commented on Show HN: I wrote a modern Command Line Handbook commandline.stribny.name/... · Posted by u/petr25102018
The content seems really great, however the typesetting makes it quite hard to read:
* Code blocks on a subsequent page to the explanation, especially when there is enough space to show it (p18/19)
* Call-outs as above (p26/27)
* Single words broken by a page (p51/52)
* Footers spanning multiple pages (p61/62)
It sounds quite nitpickey but I find it really breaks the flow when I’m reading, and trying to comprehend a section requires scrolling back and forth between two pages.
I am not an expert here but I had a thought that JSON-Schema might be a good choice because since it's schema based, i can implement the validators in Non-Typescript languages too.
https://ajv.js.org is one such JSON Schema library. How does zod compare to this?
Zod 4 supports converting a Zod schema to JSON-Schema (natively, this has always been possible with 3rd-party libs).
One key difference is preprocessing/refine. With Zod, you can provide a callback before running validation, which is super useful and can't be represented in JSON. This comes in handy more often than you'd think - e.g converting MM/DD/YYYY to DD/MM/YYYY before validating as date.
0x62 commented on Auntie PDF – an open source app built using Mistral OCR auntiepdf.com/... · Posted by u/bilater
I find it challenging to accept something that talks about "OCR" but then I upload a PDF with text in images, and when I query the document after upload, I get a message that says "I can't interpret images"..
Then are you actually doing OCR, or are you just extracting embedded text?
I’d imagine their capabilities mirror that of Mistral OCR [1]. Mistral outputs markdown, the image would have to be convertible to a reasonably useful markdown structure (charts, tables etc).
> It's not about data is sent to where, it's about what happens when it arrives to the physical servers, who has access to these files, and what can they do with it.
Right, but the EU can only enforce its laws on companies that have a presence in the EU. A company that doesn't do business in the EU and never will do business in the EU will not obey EU law regardless of what those laws say.
Meanwhile, a company that does business in the EU would be subject to fines by the EU and wouldn't be able to dodge them without just stopping doing business in the EU. So why do the laws not just say "here's how you have to treat data belonging to our citizens if you want to continue to do business in the EU"? Why does the physical location of the data that is being thus protected matter at all?
That works fine if the company itself stores the data, but becomes difficult to enforce when 3rd parties store the data. Imagine a company with an EU presence stores it's EU data in US, with a hypothetical cloud provider that doesn't have an EU presence.
The company would need to have a DPA with it's cloud provider. That cloud provider technically would also need a corresponding DPA with any 3rd parties that they themselves use, except without an EU presence that is hard to enforce.
In this case where there is one hop you could argue that it's the companies responsibility to ensure that their service providers are operating in compliance. Imagine the same scenario, but with one, two or more middlemen and the whole thing becomes an unenforceable mess of jurisdictions for the company to do meaningful due diligence on their service providers.
It's much easier for the EU to say EU data has to be stored in the EU, and know that any party touching the data is likely to be in compliance, and significantly easier to investigate if they are not.
https://www.ietf.org/archive/id/draft-yasskin-http-origin-si...