social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.8K
active users

#dataportability

0 posts0 participants0 posts today
@Joaquim Homrighausen @Kevin Beaumont To be fair, full data portability via ActivityPub has only been available in a stable release of anything for two weeks.

That was when @Mike Macgirvin 🖥️'s Forte, created in mid-August of 2024 as a fork of his own streams repository and the latest member of a family of software that started in 2010 with Friendica, had its very first official stable release.

And, in fact, Forte just uses ActivityPub to do something that (streams) and its predecessors all the way to the Red Matrix from 2012 (known as Hubzilla since 2015) have been doing using the Nomad protocol (formerly known as Zot). It's called nomadic identity. This is technology that's over a dozen years old on software that was built around this technology from the get-go, only that it was recently ported to ActivityPub.

Now, nomadic identity via ActivityPub was @silverpill's idea. He wanted to make his Mitra nomadic. He started working in 2023. The first conversion of existing non-nomadic server software to nomadic still isn't fully done, much less officially rolled out as a stable release.

If Mastodon actually wanted to implement nomadic identity, they would first have to wait until Mitra has a first stable nomadic release. Then they would have to wait until nomadic identity on Mitra (and between Mitra and Forte) has become stable and reliable under daily non-lab conditions. (Support for nomadic identity via ActivityPub on (streams) worked nicely under lab conditions. When it was rolled out to the release branch, and existing instances upgraded to it, it blew up in everyone's faces, and it took months for things to stabilise again.)

Then they would have to look at how silverpill has done it and how Mike has done it. Then they would have to swallow their pride and decide to adopt technology that they can't present as their own original invention because it clearly isn't. And they would have to swallow their pride again and decide against making it incompatible with Mitra, Forte and (streams) just to make these three look broken and inferior to Mastodon.

And only then they could actually start coding.

Now look at how long silverpill has been working on rebuilding Mitra into something nomadic. This takes a whole lot of modifications because the concept of identity itself has to be thrown overboard and redefined because your account will no longer be your identity and vice versa. Don't expect them to be done in a few months.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mitra #RedMatrix #Friendica #Hubzilla #Streams #(streams) #Forte #DataPortability #NomadicIdentity
Codeberg.orgforteNomadic fediverse server.
Replied in thread

@TheBreadmonkey My dude, that suuucks. My condolences... I hope you can get everything back. Also, WTF Evernote. "

But about #Obsidian, I think you're wrong about one thing. I'm using it on my Android phone and in the app I can switch between different vaults. (See screenshot) I am not paying for Services.

The fact that Obsidian is basically a bunch of text files is the main reason I use it as I can just copy everything over to another computer, import it into another app etc.

Instead of doing that manually though (which would be a drag and failure-prone) I have #Syncthing regularly sync all my notes to my laptop and my always-on #RaspberryPi. It works very well and is a huge burden off my chest. Let me know if you want some details...

FEP-ef61 update: https://codeberg.org/fediverse/fep/pulls/455

I added a couple of sentences clarifying FEP-ef61 design goals. In particular:

1. "This document describes web gateways, which use HTTP transport. However, the data model and authentication mechanism are transport-agnostic and other types of gateways could exist."

FEP-ef61 is designed to be compatible with any transport protocol, including the sneakernet. For example, it should be possible to replace web gateways with iroh nodes.

2. Location discovery using DID services. It came to my attention that some developers are trying to implement a variation of FEP-ef61 where gateways are specified in a DID document instead of an actor document. That significantly differs from existing FEP-ef61 implementations (Streams and Mitra), and has a serious practical disadvantage: it doesn't work with generative DID methods such as did:key. Support for pure key-based identities is important for several reasons:

- It is very useful for client-to-client (#p2p) communication without servers.
- Interoperability with other protocols that use public keys as identities. #Nostr is probably the most popular, but there are many more.
- It lowers the barriers to entry for client developers, who otherwise would need to deploy a did:web or something more complicated like did:webvh.

So, don't do that.

Also added a discussion section about media access control.

If media identifier only contains a digest, the gateway can't restrict access to it. This may not be a big problem because digest is very hard to guess, but an access control mechanism still might be useful. One way to implement it is to add an 'ap' identifier of a parent document to a hashlink and make it mandatory.

Codeberg.orgFEP-ef61: Update proposal- Updated "History". - Replaced did:tdw with did:webvh. - Added a note about non-web gateways. - Describe location discovery using DID services. - Clarified how gateways with arbitrary paths can work. - Added a section about media access control.

Since #Twitter is more unwilling than unable to comply with my request for handing over data and deleting my account (Imerely refused to use it since I announced it's shutdown) I guess I'll have to call up either wbs.legal or someone else.

  • I think it's not unreasonable to demand them to provide me my data in an offlice-searchable and human-readable form on a physical media since they are untterly unable to provide me a working download link!

Maybe @maxschrems and other folks at @noybeu want to get involved too.

WBS.LEGALWBS.LEGAL | Rechtsanwälte bundesweitIhre Kanzlei für Internetrecht und Medienrecht: WBS.LEGAL (ehemals Wilde Beuger Solmecke) - Bundesweit aktiv - Wir helfen Ihnen gerne!
#data#privacy#GDPR

My uncle ended up with two #Facebook accounts associated with his two email addresses, so I'm trying to help him consolidate them down into one account.
To facilitate that, I requested an export of his friends list from both accounts to use to figure out who to transfer over to the account being saved.
My uncle doesn't have a lot of Facebook friends.
It's 24 hours later, and the exports still aren't finished.
You can see how seriously #Meta takes #dataPortability.
#enshittification

Continued thread

I’m looking at extracting all my data and moving to more open source solutions. I’m really still only here because of the legacy of my data (and Apple, seemingly, knows this).

It’s the grating irritation on top of everything else about the world being so terrible. I’m trying really hard to be okay with existence.

Quick post, mostly to journal things. This evening, I went along to an interesting talk about ATProto and its ecosystem, that was held at Newspeak House in Shoreditch. This was a presentation by Dan Abramov, one of the developers over at Bluesky1.

I’m on Bluesky, and I use it from time to time. I’m interested in a couple of aspects of the underlying protocol, particularly the elements around data portability and the way that usernames are essentially tied to domains.

Overall it was a good talk and event and very useful overview of the current state of ATProto (for me anyway – someone with an interest, but not the time to spend immersed in that world). Thanks, Dan!

Oh, and the Pocket Reform drew a few curious onlookers and conversations 😄

  1. I met Bryan Newbold, one of the tech leads at Bluesky, at an event in Princeton back in the spring, but sadly didn’t get too much time to talk to him. ↩︎
  2. We now use this for organising the Techgrumps podcast recordings; and, I had a contribution accepted for Gathio earlier in the week. ↩︎

Like it? Share it -

https://andypiper.co.uk/2024/08/27/learning-about-the-atmosphere/

The feature is not fully functional yet (do not use it yet) but this is the first time it’s been possible to point a custom domain to a Small Web¹ place running a Kitten² app that was originally set up by Domain³.

This upcoming feature (should have it fully operational tomorrow 🤞) alongside full backup + restore (already functional) = data portability.

¹ ar.al/2024/06/24/small-web-com
² kitten.small-web.org
³ codeberg.org/domain/app

I love that I can use Kitten’s own shell (REPL) to prototype new features for Kitten¹ :)

(Coming soon: the ability to change the domain that points to your Small Web place via Kitten’s settings. That, combined with the already existing database backup and restore features mean that Small Web places will have full data portability / zero hosting lock-in from Day 1.)

:kitten:💕

¹ kitten.small-web.org/tutorials

Hier & Jetzt – Open Web 1: Wo das Open Web heute steht

Vor ein paar Wochen kam Marcel Weiß auf mich zu und fragte, ob ich nicht Lust hätte, mit ihm über das Thema „Open Web“ zu podcasten. Die letzte Ausgabe des OpenWeb-Podcasts ist jetzt fast 7 Jahre alt und natürlich freue ich mich wie bolle, wieder mit jemandem über mein Nischen-Thema zu sprechen 😉

Im Ernst, ich freue mich sehr, dass Marcel Interesse an dem Thema hat (und das schon seit einer ganzen Weile) und nach einem kurzen Vorgespräch haben wir auch gemerkt, dass uns der Stoff so bald nicht ausgehen wird!

Inhalt von share.transistor.fm anzeigen

Hier klicken, um den Inhalt von share.transistor.fm anzuzeigen

Inhalt von share.transistor.fm immer anzeigen

Inhalt direkt öffnen

Die erste Ausgabe ist eine Bestandsaufnahme der letzten 15 Jahre „Open Web“ und ein kleiner Ausblick auf zukünftige Themen.

In der ersten Ausgabe der neuen Podcastreihe zum Themenkomplex ‚Open Web‘ sprechen Matthias Pfefferle und Marcel Weiß über die Evolution von OpenID, die uns einen Hinweis auf allgemeine Herausforderungen für Protokolle in der heutigen Zeit gibt; Stichwort Extrawürste der großen Teilnehmer, welche zu Balkanisierung führen. Weitere Themen sind die DSGVO und Dataportability, Mastodon, Identi.ca und wie ActivityPub aktuell OStatus als zugrundeliegendes Protokoll für dezentrale Netzwerke ablöst. Wir ordnen die Irrungen von Diaspora ein und reden last not least über die Tragödie der Microformats.

Viel Spaß beim Hören!

‚Hier & Jetzt‘ kann man per RSS-Feed abonnieren und findet man natürlich auch bei Apple Podcasts und in jeder Podcast-App.

neunetz.comneunetz.comAnalysen für die Entscheidungsebene.