71–80 of 165 posts
I really wanted to like it, but it's just so difficult to actually find people and content, considering you can only search for hashtags and all...
Right after read an article on WAPO about Truth Social likely violating Mastodon's license, I hop on HN and find this as the first post.
To learn more about this: https://twitter.com/VValkyriePub/status/1451035108266233863?...
I really wanted to like it, but it's just so difficult to actually find people and content, considering you can only search for hashtags and all...
I've been trying to set this up for years and it continues to defeat me. Even the Docker method is still fraught. I hope they can dumb it down at some point, or clean up the docker setup. There's a LOT of different frameworks & tooling at play in this ecosystem to debug when things go wrong. But I guess it is close to rocket science.
The go-to managed hosting option is masto.host if you have $7/month and no great urge to run your own.
Mastodon recently hit 1 million active users. It has about 2.89 million total users among 3,400+ servers. https://fediverse.party/en/mastodon
Earlier quoted context omitted.
If they did update their production code since their last source code release, then you're right, it would be a license violation. I don't know if this is the case. Either way, it is much better to make occasional source code releases than to not release any code at all, when the code is under a copyleft license.
Honest question: There is a lot of talk about Truth Social violating the AGPL license. If it it a work in progress and not yet public, do they need to share their source code, or do they need to share it once they launch?
It depends on if the accidentally public instance could be considered a trade secret.
Earlier quoted context omitted.
If they did update their production code since their last source code release, then you're right, it would be a license violation. I don't know if this is the case. Either way, it is much better to make occasional source code releases than to not release any code at all, when the code is under a copyleft license.
Honest question: There is a lot of talk about Truth Social violating the AGPL license. If it it a work in progress and not yet public, do they need to share their source code, or do they need to share it once they launch?
> d) 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.
There's also pleroma, which I've run and is pretty great and low on resource requirements. And there are tons of other social UX paradigms like link aggregators and even Peertube which is a tube site server on the same network as mastodon using the same ActivityPub protocol.
I'd love to see people implement novel types of social sites besides functional clones of existing social media, there are some significant architectural and UX differences in a distributed, federated social architecture that can be leveraged to great effect.