Social Network User Data Storage
An entire Social Network in 1.6GB (GraphD Part 2)
Roaring Bitmaps offer an even more efficient way to store and query an entire social graph, fitting the entire network of 5.5M users and 164M+ follows into a ~1.6GB SQLite DB on disk.
Personal data storage is an idea whose time has come
Data Ownership as a conversation changes when data resides primarily with people-governed institutions rather than corporations.
Multi-Homed Personal Data for Education
This blogpost is part of a 20-day project I'm doing for the SURF/NPuls EduWallet Incubator this year, exploring what Personal Data Stores (PDSs) like the Solid Project can add to Wallets.
Who Even Cares About Data Ownership Anyway? - What The Function!?
Taking a look at a concept that's been talked a lot over the last few years, especially in the context of social media
Simplify sharing with built-in APIs and progressive enhancement
Instead of leaning into heavy social sharing widgets, you can create a truly user-friendly social sharing component that works for everyone, using built-in APIs and progressive enhancement.
Permissioned Data Diary 2: Buckets - Daniel's Leaflets
The second in a series of posts building up a solution to permissioned data on atproto. We introduce buckets: a new protocol primitive for creating a shared social context.
Social apps | at-store
Social-layer apps focused on posting, discovery, conversation, and relationship-building across the network.
Blog
For quite some time now, i have been working on and off on a fully self-hosted search engine, in hope to make it easier to search across Personal data in an end to end manner. Even as individuals, we are hoarding and generating more and more data with no end in sight. Such "personal" data is being stored from local hard-disks to corporate controlled cloud-centers which makes it distributed in nature. So for following discussion, "Personal" meaning would be flexible enough to accommodate resources on a remote server and/or on different devices, as long the user could prove authentication and/or authorization to that data. Current implementation supports only "images", but eventual goal is also to support other modalities like video, text and audio, some code would be shared, while some new code would be required to better extract Features for each modality.
[Proposal] Shared private Data for social posting
seconding a sidecar private PDS endpoint attached to the DID document as a good approach in the general case (in an implementation of private data I did which never saw the light of day, this was the approach I took), though obviously it imposes additional constraints on a first mover building this out.
I know I’ve said this before and recently, but I’m over the skeuomorphic UX of Bluesky that makes it look and feel like a 20 year old social media app. I’m ready for new experiences for this kind of media/data. This information architecture is played out. Let’s try some new ideas with other clients.
Once again looking at bring your own user-data storage options (for my malleable software experiment this time). What do people think are some user friendly options that don't require any OAuth apps to be created on the server? ie. no Dropbox, Google Drive, One Drive & other services like that.
