Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
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:

244
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#cwtch

0 posts0 participants0 posts today
desirable_dialogue<p><span class="h-card" translate="no"><a href="https://snac.el-hoyo.net/social/uhuru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>uhuru</span></a></span> <br><a href="https://ni.hil.ist/tags/DeltaChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DeltaChat</span></a> has no forward secrecy. <br>And depended on SHA-1 and using MD5.<br>Both are considered weak cryptography if I'm not mistaken. <br>While I believe deltachat to be a great app with good use case, it's not what I'm looking for. </p><p><a href="https://ni.hil.ist/tags/xmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>xmpp</span></a> ecosystem is?/was! pretty bad in serving proper e2ee cross platform implementation.<br>Till recently there was only conversations as a usable app. Since some weeks ago it seems that <span class="h-card" translate="no"><a href="https://fosstodon.org/@dino" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dino</span></a></span> now also offers e2ee by default. But also both conversations and Dino using an outdated omemo specification, and are by that not compatible with <span class="h-card" translate="no"><a href="https://fosstodon.org/@kaidan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kaidan</span></a></span>. <br>I will reconsider xmpp when they adapt the newer specification. </p><p><span class="h-card" translate="no"><a href="https://fosstodon.org/@briar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>briar</span></a></span> not mentioned, but also no, cause it's not working on <a href="https://ni.hil.ist/tags/TailsOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TailsOS</span></a> or on android with Orbot. <br>So very much unusable, since it's not running on the platforms we use. </p><p><a href="https://ni.hil.ist/tags/simplex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>simplex</span></a>, no, I don't like nor trust the dev. </p><p><a href="https://ni.hil.ist/tags/cwtch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cwtch</span></a>, yes, maybe</p>
uhuru<a href="https://snac.el-hoyo.net/social?t=deltachat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeltaChat</a><br>decentralized, e2ee + can be used with any radical email provider.<br><br><a href="https://snac.el-hoyo.net/social?t=xmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a> as 2nd option.<br><br>a more difficult (not effortlessly) 3rd option , <a href="https://snac.el-hoyo.net/social?t=cwtch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CWTCH</a><br>
Feral Thoughts<p><span class="h-card" translate="no"><a href="https://mastodon.social/@sarahjamielewis" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>sarahjamielewis</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@dazo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dazo</span></a></span> <span class="h-card" translate="no"><a href="https://social.coop/@ambiguous_yelp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ambiguous_yelp</span></a></span> <span class="h-card" translate="no"><a href="https://fediscience.org/@GeorgKrammer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>GeorgKrammer</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@simplex" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>simplex</span></a></span> <span class="h-card" translate="no"><a href="https://noc.social/@light" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>light</span></a></span> </p><p>In summary, I don’t think the <a href="https://union.place/tags/SimpleX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SimpleX</span></a> approach of assigning ids to user connections instead of users, and using their own onion routing, provides superior metadata-resistance as compared to a centralized service like <a href="https://union.place/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Signal</span></a>.</p><p>In most scenarios, it will provide less metadata-resistance (but will be more convenient to use) than a <a href="https://union.place/tags/p2p" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>p2p</span></a> messenger like <a href="https://union.place/tags/Briar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Briar</span></a> or <a href="https://union.place/tags/Cwtch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cwtch</span></a>.</p><p>(continues)</p>
Charlotte Walker<p><span class="h-card" translate="no"><a href="https://strangeobject.space/@moonrabbit" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>moonrabbit</span></a></span> You poor love. Sending many Welsh cuddles <a href="https://beige.party/tags/cwtch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cwtch</span></a></p>
ExploreLive feeds
About