News for hackers. Stuff that matters.
Re:Elasticsearch is open source, again by tensor on Friday August 30, 2024 @11:55AM (#41401887)
If the client talks to service A, which talks to AGPL service B, I assume that would count as having to "prominently offer the source code for service B". No? If that's true, then it becomes a real pain to track all the places where an end user could indirectly come in contact with service B.

If that's not how to interpret the license then wouldn't a simple API gateway or proxy circumvent it?

Re:Elasticsearch is open source, again by skrtskrt on Friday August 30, 2024 @12:31PM (#41402268)
> then it becomes a real pain to track all the places where an end user could indirectly come in contact with service B

Easy solution: then you just publish your patches for anyone to get. Or just anyone with a login to your SaaS. If you haven't changed anything then they can just get the original source themselves.