Earlier quoted context omitted.
You could just, like, turn it all off and go on holiday.
We believe in free speech and giving a voice to the deplatformed, so while we could, we won't.
Making Truth Social Comply with the AGPL
41–50 of 99 posts
Re: Making Truth Social Comply with the AGPL
#42Re: Making Truth Social Comply with the AGPL
#43Earlier quoted context omitted.
We believe in free speech and giving a voice to the deplatformed, so while we could, we won't.
ISIS and Al Qaeda are deplatformed too. Will you carry their speech?
Re: Making Truth Social Comply with the AGPL
#44Thank 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…
Main issue is probably that your team is too busy trying to one-up FTX
https://www.bloomberg.com/news/articles/2024-04-03/trump-spa...
Re: Making Truth Social Comply with the AGPL
#45Re: Making Truth Social Comply with the AGPL
#46Re: Making Truth Social Comply with the AGPL
#47Wow sounds like they comply better then pretty much any company I wasn't expecting that when I started the article.
Re: Making Truth Social Comply with the AGPL
#48Earlier quoted context omitted.
What's the work culture like at Truth Social? Are you guys mostly remote? How many developers are there? Are you hiring a lot of new people? Is there an ideological current to the workplace culture? I won't be applying, but I'm genuinely curious what it's like to work at a company in such a unique situation.
Pretty good! Relatively small team (between 10 and 100), biased toward senior with a few ~5 year more intermediate people, mostly remote across the US although we do have an office and try to get together monthly to quarterly. Ironically, lots of open source contributors. We are hiring for a few roles but mostly just being opportunistic rather than needing to hire. Remarkably little turnover for a tech company. We've…
Re: Making Truth Social Comply with the AGPL
#49Earlier quoted context omitted.
> We will probably add a quarterly task to update it, until/unless we start maintaining a public branch and do it automatically. Unless you only update the code running on the website quarterly, I don't think this complies with the license.
Strictly speaking, the source code needs to be made to users upon request. It doesn't need to be proactively published. That's just the easiest way to do it. So it would be within the license to update "quarterly, and whenever someone bothers to ask".
Re: Making Truth Social Comply with the AGPL
#50Thank 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…