shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

267
active users

#tou

0 posts0 participants0 posts today
Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:​<p>Have decided to give <a href="https://infosec.space/tags/ZenBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZenBrowser</span></a> another go, but with conditions:</p><ul><li><a href="https://infosec.space/tags/Sidebery" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sidebery</span></a>, not its unreliable* &amp; <em>not-my-cup-of-tea</em> native tabs</li><li><a href="https://infosec.space/tags/FirefoxSecondSidebar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FirefoxSecondSidebar</span></a> <a href="https://github.com/aminought/firefox-second-sidebar" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/aminought/firefox-s</span><span class="invisible">econd-sidebar</span></a>, not its unsatisfactory native <a href="https://infosec.space/tags/WebPanels" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebPanels</span></a> </li></ul><p>In case anyone wonders, this [temporary?] change from my hitherto daily :firefox_nightly: [<a href="https://infosec.space/tags/FirefoxNightly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FirefoxNightly</span></a> + <a href="https://infosec.space/tags/Sidebery" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sidebery</span></a> + <a href="https://infosec.space/tags/uBlockOrigin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uBlockOrigin</span></a> + <a href="https://infosec.space/tags/FirefoxSecondSidebar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FirefoxSecondSidebar</span></a>] has <strong><em>nothing</em></strong> to do with the recent global <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FUD</span></a> wrt Mozilla's <a href="https://infosec.space/tags/TOU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TOU</span></a> / <a href="https://infosec.space/tags/EULA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EULA</span></a>, but instead is due to the aesthetic pleasantness of :zenbrowser: &amp; the desire to use its <a href="https://infosec.space/tags/SplitTabView" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SplitTabView</span></a> <a href="https://infosec.space/tags/TabSplitView" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TabSplitView</span></a> <a href="https://infosec.space/tags/TabPaneView" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TabPaneView</span></a>; two undeniable advantages over Nightly. </p><p>* the Zen subreddit is full of users posting that Zen spontaneously lost all their tabs, or all their pinned tabs, or all their unpinned tabs. In my own past months of using Zen with its native <a href="https://infosec.space/tags/Workspaces" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Workspaces</span></a> &amp; tabs, it also happened to me, twice, &amp; it is most exasperating.</p>
☮ ♥ ♬ 🧑‍💻<p>“On Wednesday we shared that we’re introducing a new Terms of Use (TOU) and <a href="https://ioc.exchange/tags/PrivacyNotice" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PrivacyNotice</span></a> for <a href="https://ioc.exchange/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a>. Since then, we’ve been listening to some of our community’s concerns with parts of the <a href="https://ioc.exchange/tags/TOU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TOU</span></a>, specifically about licensing. Our intent was just to be as clear as possible about how we make Firefox work, but in doing so we also created some confusion and concern. With that in mind, we’re updating the language to more clearly reflect the limited scope of how Mozilla interacts with <a href="https://ioc.exchange/tags/UserData" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UserData</span></a>.</p><p>Here’s what the new language will say:” — Ajit “CockWomble” Varma</p><p> “MY REALITY IS JUST DIFFERENT THAN YOURS,”</p><p>&lt;<a href="https://blog.mozilla.org/en/products/firefox/update-on-terms-of-use" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.mozilla.org/en/products/f</span><span class="invisible">irefox/update-on-terms-of-use</span></a>&gt;</p>
Cliff<p>Mozilla over here adding Terms of Use to Firefox, which I don't think will go over very well. </p><p>Why are people still using and supporting Mozilla in any way at this point?</p><p><a href="https://www.mozilla.org/en-US/about/legal/terms/firefox/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">mozilla.org/en-US/about/legal/</span><span class="invisible">terms/firefox/</span></a></p><p><a href="https://infosec.exchange/tags/Mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mozilla</span></a> <a href="https://infosec.exchange/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a> <a href="https://infosec.exchange/tags/ToU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ToU</span></a> <a href="https://infosec.exchange/tags/TermsOfUse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TermsOfUse</span></a> <a href="https://infosec.exchange/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>News</span></a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tech</span></a> <a href="https://infosec.exchange/tags/TechNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechNews</span></a> <a href="https://infosec.exchange/tags/AllThingsTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AllThingsTech</span></a></p>
Chuck Darwin<p><span class="h-card"><a href="https://wikis.world/@wikipedia" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wikipedia</span></a></span><br>This page is an explanation of the overall updates that the <a href="https://c.im/tags/Wikimedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wikimedia</span></a> Foundation Legal department is proposing to the Terms of Use (<a href="https://c.im/tags/ToU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ToU</span></a>) in early 2023. This document lays out a brief summary section by section of what we are proposing would be updated and why we want to make the change. We hope that this is helpful for community members when reviewing the proposed changes during the feedback cycle.</p><p><a href="https://meta.m.wikimedia.org/wiki/Wikimedia_Foundation_Legal_department/2023_ToU_updates/About" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">meta.m.wikimedia.org/wiki/Wiki</span><span class="invisible">media_Foundation_Legal_department/2023_ToU_updates/About</span></a></p>