Lingolol

0 posts0 participants0 posts today

☮ ♥ ♬ 🧑‍💻Big question, Why ATProtocol from <a href="https://ioc.exchange/tags/BlueSkySocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlueSkySocial</a> <a href="https://ioc.exchange/tags/PBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PBC</a>’s mouth instead of Mastodon and ActivityPub?: “Why not use ActivityPub? <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> is a federated social networking technology popularized by <a href="https://ioc.exchange/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a>.Account <a href="https://ioc.exchange/tags/portability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#portability</a> is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects <a href="https://ioc.exchange/tags/users" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#users</a> from sudden bans, server shutdowns, and policy disagreements. Our <a href="https://ioc.exchange/tags/solution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solution</a> for portability requires both signed data repositories and <a href="https://ioc.exchange/tags/DIDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DIDs</a>, neither of which are easy to retrofit into ActivityPub. The migration <a href="https://ioc.exchange/tags/tools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tools</a> for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.Another major reason is <a href="https://ioc.exchange/tags/scalability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scalability</a>. <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual <a href="https://ioc.exchange/tags/nodes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nodes</a> to be flooded with traffic and generally struggles to provide global views of <a href="https://ioc.exchange/tags/activity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#activity</a>.”Short version, WE CANT CONTROL YOU. <<a href="https://atproto.com/guides/faq" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://atproto.com/guides/faq</a>>

Akhilesh ThiteOwn your identity, own your data!DScan v4.0 leverages Web3Storage's w3up-client, incorporating <a href="https://mastodon.social/tags/DIDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DIDs</a> and <a href="https://mastodon.social/tags/UCAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UCAN</a> to create a robust framework for decentralized authentication and authorization.DScan is the fastest way to store and share data over <a href="https://mastodon.social/tags/IPFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPFS</a> directly from browsers.💻 Chrome web store: <a href="https://chromewebstore.google.com/detail/dscan-own-your-identity-o/idpfgkgogjjgklefnkjdpghkifbjenap" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://chromewebstore.google.com/detail/dscan-own-your-identity-o/idpfgkgogjjgklefnkjdpghkifbjenap</a>

nbHeute ist Tag 4 der Downtime des <a class="hashtag" href="https://social.biblioco.de/tag/urn" rel="nofollow noopener noreferrer" target="_blank">#URN</a>-Services der <a class="u-url mention" href="https://openbiblio.social/@DNB_Aktuelles" rel="nofollow noopener noreferrer" target="_blank">@DNB_Aktuelles</a>. Alle URNs im urn:nbn:de Namensraum verweisen momentan ins Nichts, diese von vielen Repositorien in <a class="hashtag" href="https://social.biblioco.de/tag/bibliotheken" rel="nofollow noopener noreferrer" target="_blank">#Bibliotheken</a> und <a class="hashtag" href="https://social.biblioco.de/tag/wissenschaft" rel="nofollow noopener noreferrer" target="_blank">#Wissenschaft</a> genutzten persistenten Identifier <a class="hashtag" href="https://social.biblioco.de/tag/pids" rel="nofollow noopener noreferrer" target="_blank">#PIDs</a> sind damit aktuell unbrauchbar. Es können gerade "weder URNs aufgelöst noch Neuregistrierungen bzw. Änderungen vorgenommen werden.": <a href="https://lists.dnb.de/pipermail/urn-announce/2023-May/000008.html" rel="nofollow noopener noreferrer" target="_blank">https://lists.dnb.de/pipermail/urn-announce/2023-May/000008.html</a> Bereits 2009 wurde von <a class="u-url mention" href="https://openbiblio.social/@acka47" rel="nofollow noopener noreferrer" target="_blank">@acka47</a> der erste Vorschlag hin zum Aufbau zusätzlicher dezentraler Resolving-Dienste aufgebracht: <a href="https://inetbib.de/listenarchiv/msg40914.html" rel="nofollow noopener noreferrer" target="_blank">https://inetbib.de/listenarchiv/msg40914.html</a> Seit 2022 haben wir mit Decentralized Identifiers <a class="hashtag" href="https://social.biblioco.de/tag/dids" rel="nofollow noopener noreferrer" target="_blank">#DIDs</a> einen W3C-Standard, der genau u.a. ein solches dezentrales Resolving mit offenen Standards ermöglicht. Ich hatte mich bereits 2021 in einem o-bib Artikel für deren Notwendigkeit ausgesprochen und auf die bestehenden Probleme der derzeit gängigen <a class="hashtag" href="https://social.biblioco.de/tag/pid" rel="nofollow noopener noreferrer" target="_blank">#PID</a>-Systeme hingewiesen: <a href="https://www.o-bib.de/bib/article/view/5755" rel="nofollow noopener noreferrer" target="_blank">https://www.o-bib.de/bib/article/view/5755</a> Was braucht es noch, bis die zentralen PID-Provider endlich auf das Single Point of Failure Problem aufmerksam werden?

nbAfter extensive research into decentralized social networks, it is now time for a state of the art 🧵 thread on the subject of <a class="hashtag" href="https://social.biblioco.de/tag/datasovereignty" rel="nofollow noopener noreferrer" target="_blank">#DataSovereignty</a> and its relation to end-to-end encryption and decentralized identity management. For this, I will contrast the two currently most used decentralized social networks protocols: <a class="hashtag" href="https://social.biblioco.de/tag/activitypub" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> and <a class="hashtag" href="https://social.biblioco.de/tag/nostr" rel="nofollow noopener noreferrer" target="_blank">#Nostr</a>. <a class="hashtag" href="https://social.biblioco.de/tag/fediverse" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a class="hashtag" href="https://social.biblioco.de/tag/nomad" rel="nofollow noopener noreferrer" target="_blank">#Nomad</a> <a class="hashtag" href="https://social.biblioco.de/tag/identity" rel="nofollow noopener noreferrer" target="_blank">#Identity</a> <a class="hashtag" href="https://social.biblioco.de/tag/privacy" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a class="hashtag" href="https://social.biblioco.de/tag/e2ee" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> <a class="hashtag" href="https://social.biblioco.de/tag/dpki" rel="nofollow noopener noreferrer" target="_blank">#DPKI</a> <a class="hashtag" href="https://social.biblioco.de/tag/dids" rel="nofollow noopener noreferrer" target="_blank">#DIDs</a> <a class="hashtag" href="https://social.biblioco.de/tag/ssi" rel="nofollow noopener noreferrer" target="_blank">#SSI</a> 1/11

nbNach einer intensiven Auseinandersetzung mit dezentralen Sozialen Netzwerken wird es Zeit für einen State of the Art 🧵 Thread zum Thema individuelle <a class="hashtag" href="https://social.biblioco.de/tag/datenhoheit" rel="nofollow noopener noreferrer" target="_blank">#Datenhoheit</a> und dem Zusammenhang mit Ende-zu-Ende-Verschlüsselung und dezentralem Identitätsmanagement. Dabei werde ich die beiden derzeit meistgenutzten dezentralen Social-Network-Protokolle gegenüber stellen: <a class="hashtag" href="https://social.biblioco.de/tag/activitypub" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> und <a class="hashtag" href="https://social.biblioco.de/tag/nostr" rel="nofollow noopener noreferrer" target="_blank">#Nostr</a>. Danke an <a class="u-url mention" href="https://scholar.social/@Lambo" rel="nofollow noopener noreferrer" target="_blank">@Lambo</a> für die Inspiration 😃 English translation to follow in a separate thread. <a class="hashtag" href="https://social.biblioco.de/tag/fediverse" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a class="hashtag" href="https://social.biblioco.de/tag/nomad" rel="nofollow noopener noreferrer" target="_blank">#Nomad</a> <a class="hashtag" href="https://social.biblioco.de/tag/identity" rel="nofollow noopener noreferrer" target="_blank">#Identity</a> <a class="hashtag" href="https://social.biblioco.de/tag/privacy" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a class="hashtag" href="https://social.biblioco.de/tag/e2ee" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> <a class="hashtag" href="https://social.biblioco.de/tag/dpki" rel="nofollow noopener noreferrer" target="_blank">#DPKI</a> <a class="hashtag" href="https://social.biblioco.de/tag/dids" rel="nofollow noopener noreferrer" target="_blank">#DIDs</a> <a class="hashtag" href="https://social.biblioco.de/tag/ssi" rel="nofollow noopener noreferrer" target="_blank">#SSI</a> 1/11

Recent searches

Search options

Administered by:

Server stats:

#dids