Live data from Hacker News

Making Truth Social Comply with the AGPL

boehs.org

51–60 of 99 posts

Re: Making Truth Social Comply with the AGPL

#52
post #23

Earlier quoted context omitted.

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.

I don't think our policy would have flagged that post on its own, let alone banned an account over it; if that happened it was an error.

Re: Making Truth Social Comply with the AGPL

#53

Earlier quoted context omitted.

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.

Trade secrets are a type of IP.

Re: Making Truth Social Comply with the AGPL

#55

Thank 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.

Like FTX, their site is not about the “product” its about creating bagholders

https://www.justice.gov/usao-sdny/pr/two-individuals-plead-g...

Re: Making Truth Social Comply with the AGPL

#58
post #31
post #20

Earlier 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.

Just curious, does AGPL require actively publishing the source code, or making it available upon request within a reasonable timeframe?

It depends on how the program is itself distributed. For programs that users interact with over the network, the program must have a way to offer those users the source code as well, though it need not be located on the same server.

Paragraph 6d:

    Convey the object code by offering access from a designated place
    (gratis or for a charge), and offer equivalent access to the
    Corresponding Source in the same way through the same place at no
    further charge. You need not require recipients to copy the
    Corresponding Source along with the object code. If the place to
    copy the object code is a network server, the Corresponding Source
    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source. Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is
    available for as long as needed to satisfy these requirements.
This just means that it should have some user–visible page that describes the software and any open–source components it uses, and that this same page should offer a way to download their source code. If you use an open–source component but haven’t modified it, you can send your users to its own webpage to download it if you prefer, but if you have modified it then you have to allow them to download the modified code.

Re: Making Truth Social Comply with the AGPL

#59

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.

Given who your owners are, I sincerely doubt that.
Post reply on HN