@GossiTheDog "Mastodon" really needs to get cracking on full data portability, IMHO.

It's a shame this hasn't been pushed higher up on the list of things to do.

I think many people have invested quite a bit of time and effort into their posts and profiles, and moving all that data, or somehow managing a switch-over doesn't seem to be that simple, if at all possible.

If you’ve ever had to leave an instance behind too soon, or hopelessly tried to find an old post in an archive you kept; you know the feeling of loss.

With #Posty you can turn that Mastodon archive into a functioning static website, with (my favourite part) a tag index.

See an example of what’s possible in the post below.

From: @oliphant
https://oliphant.social/@oliphant/113626365697015833

#Posty #Mastodon #DataPortability #Migrate #HTML #CSS #Archive #Backup @oliphant

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.

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 https://www.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.

How can health and fitness #dataSilos still be legal? Whatever happen with the #GDPR’s #DataPortability requirement?
“Strava’s API debacle highlights the messiness of fitness data” — Victoria Song, The Verge
https://www.theverge.com/2024/11/22/24303124/strava-fitness-data-wearables

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

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.

¹ https://ar.al/2024/06/24/small-web-computer-science-colloquium-at-university-of-groningen/
² https://kitten.small-web.org
³ https://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.)

¹ https://kitten.small-web.org/tutorials/kitten-s-interactive-shell-repl/

Data portability is a bit of a niche topic, but I'm happy to contribute to this compendium of pieces on "The Present and Future of #DataPortability" assembled by the Data Transfer Initiative: https://dtinit.org/assets/DTI-Data-Portability-Compendium.pdf

New Video – Kitten features introduced this week:

• Interactive Shell (REPL)
• Multi-page Settings
• Backup and restore (data portability)

With examples that cover components and Kitten’s built-in JavaScript database (JSDB).

https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/

Find out why you can't move your bookmarks on mobile from one browser to another and what Vivaldi is doing about data portability on Desktop.

https://vivaldi.com/blog/why-you-cant-move-bookmarks-from-one-browser-to-another-on-ios-android/

Currently: tuned in to the @DTinitiative livestream for their DC policy summit today. #DataPortability https://dtinit.org/docs/feb29summitagenda

Ever think 'Data Portability' could be about more than just exporting data? What if we could use data portability as a way to curate what companies know about us?

In my latest post, I argue that it's time to rethink and reframe data portability for our dynamic digital lives. https://careylening.substack.com/p/the-right-to-data-portability-is

After all, we are not static creatures; our likes, dislikes, names and even our identities evolve. So should our digital profiles. What if GDPR’s data portability right also allowed for easy data curation?

I argue that it's time to actually empower users by giving them the tools to easily and selectively modify their digital records to reflect who they truly are. If we extend the power of data portability to data (im)portability, this could make controlling our digital narratives as simple as a few mouse clicks. No more deadnaming. No more permanent awkward, painful memories.

The ability to curate what companies know about us, easily and painlessly may make it easier to reshape our relationship with Big Tech. Instead of hostility, we could aim for trust and accuracy. If this intrigues you, check out my latest. https://careylening.substack.com/p/the-right-to-data-portability-is