@andrewt was it #procrastination when you never expected to get to it? #pocket was a personal hope that someday you'd have the leisure time to read more deeply and ponder. Instead it became a reflexive permission to abandon items you once thought curious, alarming, important or useful.

Surprised #mozilla couldn't get @flipboard.com to adopt it. https://getpocket.com/export for #dataportability.

3/3 - @dave Our goal is to create a single SuperFeed. One that contains all of your podcast episodes, blog posts, podroll, events and merch. #dataportability

RSS Feeds have become pointers to files. Chapters & Transcripts point to external JSON files. A podroll & publisher feeds points to a series of Remote Items. LNAddress points to payment options. We have also created Event Feeds and Merch Feeds using remote items.

Our podcast portal page for creators will contain all these elements.

@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.

#mastodon #portability #dataportability #fediverse

Hello @Madeorsk aleph.land semble ne pas être référencé dans #dataportability, c'est normal ?
https://openportability.org/

@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...

#DataPortability #DigitalSovereignty

If only there was an easy way to import your Twitter followings to Mastodon… #dataportability

Data Portability Map: Articles about transferring data from a service to another service, like Wordpress to Squarespace or getting out of Facebook
https://portmap.dtinit.org/
#dataportability #dataliberation #socialmedia #download #data #+

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.

#fep_ef61 #NomadicIdentity #DataPortability

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.

#data #privacy #GDPR #BDSG #DSGVO #rightToExportData #DataPortability #ConsumerRichts #UserRights #InfoSec #Shitter #Xitter

🌍 #TheBrusselsEffect and #DataPortability: Why Technology-Neutral Laws

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

@juliewebgirl @thatkatharine Personally I wish @EUCommission would mandate #DataPortability and #DataExport between platforms.

• Even if that means they need to provide every #post as a seperate #HTML file and all attachments as well as a list of those in a #TSV file.

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.

#OpenSource #DataPortability

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.

• I was also intrigued to learn about some of the services that are starting to build on the protocol, including Smoke Signal (in fact, here’s the event listing for the talk this evening) – by contrast, I’ve been looking at similar services built on ActivityPub, such as Gathio2.
• Dan showed a web-based explorer for ATProto objects, which he described as an unofficial third party app. I thought that looked really nice, and useful, and had a nice fit with his description of the way that the data stores are organised.
  • On the ActivityPub side of things, last week I came across BrowserPub which is a similar sort of tool built by John Spurlock.

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 -

• Click to share on Mastodon (Opens in new window)
• Click to share on Threads (Opens in new window)
• Click to share on Bluesky (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• Click to email a link to a friend (Opens in new window)

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

#Blaugust2024 #100DaysToOffload #activitypub #atproto #bluesky #dataPortability #events #London #protocols #socialMedia #socialNetworks #talks #Technology #web

Don't get locked into your cloud provider. There are excessive fees for sending your data elsewhere, which you probably won't realize you have to pay until it's too late. https://colan.pro/blog/hidden-costs-of-cloud-egress-fees/
#CloudComputing #CloudCosts #DataManagement #CloudStrategy #ITBudget #egress #dataportability #bandwidthalliance @cloudflare #scaleway #vendorlockin

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

#SmallWeb #Kitten #Domain #dataPortability #interoperability

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:💕

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

#SmallWeb #Kitten #Domain #domains #dataPortability #FOSS #web #dev

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