Making Truth Social Comply with the AGPL
11–20 of 99 posts
Re: Making Truth Social Comply with the AGPL
#12Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing.
We will probably add a quarterly task to update it, until/unless we start maintaining a public branch and do it automatically.
Re: Making Truth Social Comply with the AGPL
#13Re: Making Truth Social Comply with the AGPL
#14Can we make them comply with the AGPL as well?
See: https://insrt.uk/post/andrew-tate-stealing-software-revolt
Re: Making Truth Social Comply with the AGPL
#15Thank you for your request (routed through legal, which added a day or so of latency). Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing. We will probably add a quarterly task to update it, until/unle…
Re: Making Truth Social Comply with the AGPL
#16Thank you for your request (routed through legal, which added a day or so of latency). Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing. We will probably add a quarterly task to update it, until/unle…
Any modifications you make need to also be open sourced.
Re: Making Truth Social Comply with the AGPL
#17Thank you for your request (routed through legal, which added a day or so of latency). Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing. We will probably add a quarterly task to update it, until/unle…
Still not good enough.
You still need to address this though, you are exploiting open source software by ignoring the license.
Re: Making Truth Social Comply with the AGPL
#18Thank you for your request (routed through legal, which added a day or so of latency). Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing. We will probably add a quarterly task to update it, until/unle…
You could just, like, turn it all off and go on holiday.
Re: Making Truth Social Comply with the AGPL
#19Thank you for your request (routed through legal, which added a day or so of latency). Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing. We will probably add a quarterly task to update it, until/unle…
Re: Making Truth Social Comply with the AGPL
#20Thank you for your request (routed through legal, which added a day or so of latency). Main issue is we don't have an automated pipeline to update the published tarball/zipfile from our internal source control system, so it has to be done manually, and no one has that as a specific task. We also review the source for IP/security concerns before releasing. We will probably add a quarterly task to update it, until/unle…
Unless you only update the code running on the website quarterly, I don't think this complies with the license.