101010.pl

☮ ♥ ♬ 🧑‍💻Big question, Why ATProtocol from <a href="https://ioc.exchange/tags/BlueSkySocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlueSkySocial</a> <a href="https://ioc.exchange/tags/PBC" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#Mastodon</a>.Account <a href="https://ioc.exchange/tags/portability" class="mention hashtag" rel="nofollow noopener" 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" 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" 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" 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" 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" target="_blank">#scalability</a>. <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#activity</a>.”Short version, WE CANT CONTROL YOU. <<a href="https://atproto.com/guides/faq" rel="nofollow noopener" 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" target="_blank">#DIDs</a> and <a href="https://mastodon.social/tags/UCAN" class="mention hashtag" rel="nofollow noopener" 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" 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" translate="no" target="_blank">https://chromewebstore.google.com/detail/dscan-own-your-identity-o/idpfgkgogjjgklefnkjdpghkifbjenap</a>

W3C DevelopersWanna get an overview of current <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> work? Watch this 🎬 from <a href="https://w3c.social/@plehegar" class="u-url mention" rel="nofollow noopener" target="_blank">@plehegar</a> about <a href="https://w3c.social/tags/WebNN" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebNN</a> <a href="https://w3c.social/tags/MachineLearning" class="mention hashtag" rel="nofollow noopener" target="_blank">#MachineLearning</a> <a href="https://w3c.social/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://w3c.social/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebRTC</a> <a href="https://w3c.social/tags/PrivateAdvertising" class="mention hashtag" rel="nofollow noopener" target="_blank">#PrivateAdvertising</a> <a href="https://w3c.social/tags/WebAssembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAssembly</a> <a href="https://w3c.social/tags/WebGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebGPU</a> <a href="https://w3c.social/tags/WebTransport" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebTransport</a> <a href="https://w3c.social/tags/WebCodecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCodecs</a>, <a href="https://w3c.social/tags/DIDs" class="mention hashtag" rel="nofollow noopener" target="_blank">#DIDs</a> <a href="https://w3c.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#WCAG</a>, and much more! <a href="https://youtu.be/rNFpgT8ZRqQ?si=H74Z5Eyo0718eH2o" rel="nofollow noopener" target="_blank">https://youtu.be/rNFpgT8ZRqQ?si=H74Z5Eyo0718eH2o</a>This talk is among the 20 presentations recorded during the "Web Technology Forum" event, organized by the W3C China team. English and Chinese captions are avail.!: <a href="https://www.youtube.com/watch?v=3VxD4_4NTBI&list=PLNhYw8KaLq2UvXR79_FPMFcHLG0ipGly4" rel="nofollow noopener" target="_blank">https://www.youtube.com/watch?v=3VxD4_4NTBI&list=PLNhYw8KaLq2UvXR79_FPMFcHLG0ipGly4</a>Read more about this successful event: <a href="https://www.w3.org/blog/2023/infinite-intelligence-and-secure-connection-w3c-chinas-web-technology-forum-report/" rel="nofollow noopener" target="_blank">https://www.w3.org/blog/2023/infinite-intelligence-and-secure-connection-w3c-chinas-web-technology-forum-report/</a>

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" 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" target="_blank">#ActivityPub</a> und <a class="hashtag" href="https://social.biblioco.de/tag/nostr" rel="nofollow noopener" target="_blank">#Nostr</a>. Danke an <a class="u-url mention" href="https://scholar.social/@Lambo" rel="nofollow noopener" 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" target="_blank">#Fediverse</a> <a class="hashtag" href="https://social.biblioco.de/tag/nomad" rel="nofollow noopener" target="_blank">#Nomad</a> <a class="hashtag" href="https://social.biblioco.de/tag/identity" rel="nofollow noopener" target="_blank">#Identity</a> <a class="hashtag" href="https://social.biblioco.de/tag/privacy" rel="nofollow noopener" target="_blank">#Privacy</a> <a class="hashtag" href="https://social.biblioco.de/tag/e2ee" rel="nofollow noopener" target="_blank">#E2EE</a> <a class="hashtag" href="https://social.biblioco.de/tag/dpki" rel="nofollow noopener" target="_blank">#DPKI</a> <a class="hashtag" href="https://social.biblioco.de/tag/dids" rel="nofollow noopener" target="_blank">#DIDs</a> <a class="hashtag" href="https://social.biblioco.de/tag/ssi" rel="nofollow noopener" target="_blank">#SSI</a> 1/11

Anil John 🇺🇸⟨ " Small wonder that, from the beginning, the internet has been a fight between those who want to build a commons and those who wish to enclose it. [...] But standard protocols exert powerful network effects on corporations. When everyone is adhering to a standard, when everything can talk to everything else, then it's hard to lure users into a walled garden. [...]The enclosure of online communities can't be understood without also understanding the policy choices that led to the enclosure of tech more broadly [...]These are the laws and technologies that transform network effects from a tool for openness – where even the largest, most vicious corporations must seek to pervert, rather than ignore, standards – into a tool for enclosure, where we are all under mounting pressure to move inside a walled garden." ⟩This piece by <a href="https://mamot.fr/@pluralistic" class="u-url mention" rel="nofollow noopener" target="_blank">@pluralistic</a> is so worth the read to understand much of the <a href="https://infosec.exchange/tags/competition" class="mention hashtag" rel="nofollow noopener" target="_blank">#competition</a> and market dynamics that play out within and between standards development organizations and vendor dominated foundations that seek to produce standards.<a href="https://pluralistic.net/2022/12/23/semipermeable-membranes/#free-as-in-puppies" rel="nofollow noopener" target="_blank">https://pluralistic.net/2022/12/23/semipermeable-membranes/#free-as-in-puppies</a>I particularly loved this part:⟨ " The Fediverse's foundation is a standard called ActivityPub, which was designed by weirdos who wanted to make a durably open, interoperable substrate that could support nearly any application. This was something that large corporations were both uninterested in building and which they arrogantly dismissed as a pipe dream. This means that Activitypub is actually as good as its architects could make it, free from boobytraps laid by scheming monopolists. " ⟩.. which was the point I was trying to make @ <a href="https://infosec.exchange/@aniltj/109537052991250665" rel="nofollow noopener" target="_blank">https://infosec.exchange/@aniltj/109537052991250665</a> to ensure support for and existence of organizations where such work on the "Internet Commons" can take place!I would also note that in the early part of the work on <a href="https://infosec.exchange/tags/VerifiableCredentials" class="mention hashtag" rel="nofollow noopener" target="_blank">#VerifiableCredentials</a> and <a href="https://infosec.exchange/tags/DIDs" class="mention hashtag" rel="nofollow noopener" target="_blank">#DIDs</a>, we had the same type of dismissal taking place -- Though now, we have moved into the phase were many who were dismissive are seeking to embrace, extend and appropriate!

fridaysforfuture, but everyday<a href="https://mastodon.social/@trwnh" class="u-url mention" rel="nofollow noopener" target="_blank">@trwnh</a> Decentralized Identifiers (DIDs) I'm curious about. Happy to see that evolve. All I can say on the matter between <a href="https://todon.nl/tags/dids" class="mention hashtag" rel="nofollow noopener" target="_blank">#DIDs</a> and how zot does it, that <a href="https://octodon.social/@cwebber" class="u-url mention" rel="nofollow noopener" target="_blank">@cwebber</a> and dev of zot <a href="https://quitter.es/macgirvin" class="u-url mention" rel="nofollow noopener" target="_blank">@macgirvin</a> have a different perspective on how to solve the mentioned isse. I have way to little knowledge to make a judge about. <a href="https://mastodon.memoryandthought.me/@alex" class="u-url mention" rel="nofollow noopener" target="_blank">@alex</a> <a href="https://manowar.social/@zatnosk" class="u-url mention" rel="nofollow noopener" target="_blank">@zatnosk</a>

Recent searches

Search options

Administered by:

Server stats:

#dids