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.
[flagged]
Making Truth Social Comply with the AGPL
21–30 of 99 posts
Re: Making Truth Social Comply with the AGPL
#22Thank 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…
> We also review the source for IP/security concerns before releasing. Any modifications you make need to also be open sourced.
Best practice when releasing source code generally is making sure no one left API keys, etc. in source code. (Obviously you never check secrets in in the first place, keeping them separate, but it's still worth automated and manual review before releasing.)
Re: Making Truth Social Comply with the AGPL
#23Earlier 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.
You mean solely for the deplatformed, and not necessarily free speech for anyone else?
Edit: I was banned for saying Ashley Babbit was committing a crime and that we should not have double standards where she is a martyr but George Floyd can’t be.
Re: Making Truth Social Comply with the AGPL
#24Thank 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…
Masks don’t protect against viral licenses either. IP isn’t a valid claim to withhold the source. Security needs to be managed outside the code via vaults and other runtime secret stores. There’s no leg to stand on for not releasing the entire code consistently.
Re: Making Truth Social Comply with the AGPL
#25This is a great start with Truth Social, lets also do something with this poor student, who's AGPL software is being still used by Andrew Tate's "The Real World" scam. Can we make them comply with the AGPL as well? See: https://insrt.uk/post/andrew-tate-stealing-software-revolt
They should email compliance@sfconservancy.org, the non-profit that is currently suing Vizio and previously represented Mastodon in this case.
Re: Making Truth Social Comply with the AGPL
#26Earlier quoted context omitted.
> We also review the source for IP/security concerns before releasing. Any modifications you make need to also be open sourced.
Best practice when releasing source code generally is making sure no one left API keys, etc. in source code. (Obviously you never check secrets in in the first place, keeping them separate, but it's still worth automated and manual review before releasing.)
That's not IP, that's secrets. IP needs to be included.
Re: Making Truth Social Comply with the AGPL
#27Thank 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…
Masks don’t protect against viral licenses either. IP isn’t a valid claim to withhold the source. Security needs to be managed outside the code via vaults and other runtime secret stores. There’s no leg to stand on for not releasing the entire code consistently.
The other mastodon instances voluntarily chose to refuse to peer with Truth Social. Maybe they should show their face in court too.
Re: Making Truth Social Comply with the AGPL
#28Earlier 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.
Why did you ban me then? Just like Free Speech Extremist all over again, can't actually live up to the claims you make.
Re: Making Truth Social Comply with the AGPL
#29Thank 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…
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.
Re: Making Truth Social Comply with the AGPL
#30Earlier quoted context omitted.
We believe in free speech and giving a voice to the deplatformed, so while we could, we won't.
[flagged]
If you don’t like it just ignore it. Just let all of them echo each other lol.
I have to do that with X because I joined and I’m bombarded by lunatic shit because it forces me to follow Elon when I sign up.
All these social media sites suck.