Recent searches

No recent searches

Search options

Only available when logged in.
med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

365
active users

med-mastodon.com: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#tivolization

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://kotaro.me/@kotaro" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kotaro</span></a></span> gramted, all of tuhe <a href="https://infosec.space/tags/Forks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Forks</span></a> that are <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a>-licensed had way more <a href="https://infosec.space/tags/effort" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>effort</span></a> put into them.</p><ul><li>I just think that <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> is as bad as <a href="https://infosec.space/tags/Tivolization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tivolization</span></a> in terms of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> and <a href="https://infosec.space/tags/useability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>useability</span></a>.</li></ul><p><a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> is still worse than <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a>, but <a href="https://infosec.space/tags/AGPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPL</span></a> &amp; <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> are just completely disregarding the legal reality of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a> and <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a>.</p><ul><li>If they don't want to accept <a href="https://infosec.space/tags/competition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>competition</span></a>, they could've chosen <span class="h-card" translate="no"><a href="https://mastodon.social/@creativecommons" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>creativecommons</span></a></span> <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCBYNCSA</span></a> instead, but they did not! </li></ul><p>Needless to say if I were a <a href="https://infosec.space/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developer</span></a> of it and had contributed under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a> license I'd expect to either get my code removed entirely or the license to be kept the same.</p><ul><li>And now you know why I'll refuse to sign any <em>"<a href="https://infosec.space/tags/ContributorLicenseAgreement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ContributorLicenseAgreement</span></a>"</em> (<a href="https://infosec.space/tags/CLA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLA</span></a>) <em>UNLESS</em> I get a paid, non - term-limited position as an enployee in return…</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastos.online/@Nicholasr_ITSulu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Nicholasr_ITSulu</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nixCraft</span></a></span> it doesn't enforce the terms on the license/copyright-holders!</p><ul><li>Allowing <a href="https://infosec.space/tags/Tivolization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tivolization</span></a> big time...</li></ul>
Kevin Karhan :verified:<p><span class="h-card"><a href="https://merveilles.town/@nasser" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nasser</span></a></span> that's what a lot of dual-licenses and free-for-noncommercial setups already do....</p><p><a href="https://mstdn.social/tags/Copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copyleft</span></a> like in <a href="https://mstdn.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> and espechally the hard <a href="https://mstdn.social/tags/MustLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MustLicense</span></a> requirement for <a href="https://mstdn.social/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> make <a href="https://mstdn.social/tags/Tivolization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tivolization</span></a> hard-to-impossible...</p>
TrendingLive feeds
About