"The tyranny of the quantifiable"
....probably the most eloquently titled collection I've come across yet on @semble.so !
(and wasn't the least bit surprised to learn the phrase was sourced from a Rebecca Solnit article)
good stuff Ethan - energised by what you've already described in some detail, the hints re: tackling some of the harder challenges, and especially the closing remarks around values-based motivations.
Look forward to the next episode!
Check out my first blog! As the ATmosphere moves towards permissioned data, how do we make sure privacy is really preserved? Can we build a permissioned data app today? All that and more in the post 👀📅
The week-end is over so I'm pressing ⏸️ on my custom PDS project for now. Here's part 2 of my dev journal.
I've learned a lot already and so far I feel like it might actually be worth finishing.
It's really cool to get a more intimate understanding of ATProtocol and it's implementation.
the "thing" I wrote yesterday is now here in a publication...
#atproto
at-wayfinding.leaflet.pub/3mgsx6o3trc27
I will be joining online...hopefully you're session is being streamed? (and not too early in the day as I will still be 🛌 down here in Australia!)
The articles that people are bookmarking on @semble.so are high quality. It's quickly becoming my go to place to consume dev content
The first at://news weather report is here, learn about what happened across the atmosphere this week and how we are exploring how to collectively-source future newsletters with your help!
My week-end side-project: make a PDS, maybe.
So far I've skimmed the spec, and started playing with @rivet.gg.
I'll be using existing libraries wherever possible, so it's not like an independent reimplementation. I'm going more for a customizable repackaging of the reference PDS if possible.
"Currently we're building pear: a permission-enforcing ATProtocol repository, tied to your ATProtocol identity through a service, as defined in the DID document (for now)."
this is great Arushi 👏👏👏
recently been pulling together the range of perspectives re: possible approaches to permissioned data, so really nice to now have something tangible to play with 🙂
if you feel the urge that would be great
Hi Robin, anything you've previously posted/shared re: project "Kill PDF"?
Slide titled "The Scientific ATmosphere" with subheading "Open, interoperable tools spanning the entire research lifecycle". Shows a 3x4 grid of 12 platforms, each with logo, name, brief description, and URL. Top row: Bluesky (microblogging network), Curvenote (scientific writing and publishing), Chive (decentralised preprint archive), and Lanyards (researcher profiles). Middle row: Hypgen Infinity (AI science platform), Layers (linguistic annotation), Margin (annotation layer), and Octosphere (publication syncing). Bottom row: Semble (research trails), Seams (web annotation), Standard Site (publishing schemas), and Viewsift (discussion platform). At bottom, dark banner reading "The AT Protocol Foundation" with four pillars: Identity (one researcher profile works across every platform), Activity (contributions compound across tools), Content (posts and works flow seamlessly across ecosystem), and Connections (professional networks persist in every tool researchers choose).
Drafting a pitch deck for Lanyards. It just hit me that #ATscience 🧪 in the #ATmosphere 🌀 is very real now.
@atproto.science → @curvenote.com @chive.pub @lanyards.app @hypgen.bsky.social @layers.pub @margin.at @andreasthinks.me @sealight.xyz @semble.so @standard.site @viewsift.com 😻
#ATproto 🪿
February updates for @cosmik.network & @semble.so !
Including @central.comind.network @funferall.bsky.social @uppy-hacker.bsky.social @tgoerke.bsky.social @o.simardcasanova.net @hacdias.com @bmann.ca @caleb.jasik.xyz @atproto.science
I can save bookmarks with @margin.at, file them in collections created with @semble.so, and both bookmarks and collections are visible in Margin and in Semble
Oh, and if either Margin or Semble shut down, this wouldn't impact my data
All of this dark magic is only possible thanks to AT Proto
I have a Private & Permissioned Data collection on @semble.so using the new “open” feature that I added this link to - feel free to add relevant links of your own semble.so/profile/bman...
It uses #atproto link sharing docs @margin.at and @semble.so and grabs them via the official atproto js sdk, and rehosts them in a list on my site.
You can see the code here: gist.github.com/jasikpark/41...
The agenda for #ATScience is up! Check out the speaker list and full schedule below 👇
The range and quality of proposals we received really exceeded our expectations - thanks to everyone who submitted something!
March 27, Vancouver - can't wait to see you there ✨
Sessions include >
For those that missed here's a Semble collection for links shared today: semble.so/profile/did:...
💯 Joel, and from a @cairos.network perspective, perhaps only a short hop from a "living document" to a "living discourse graph"!? 🤩
Thanks to @chrisshank.com for pointing out @pfrazee.com's short post with the backstory to this...
"The name AppView came from a database processing ETL mindset, like a materialized view in postgres."
www.pfrazee.com/leaflets/3ly...
..then an api call to retrieve all those records directly from user repo's is NOT going to return a result in just a few seconds!
Still, Paul's simplified diagram and explanation...
"...just call it an App and then explain that the data gets stored in the PDS"
...overlooks the fact that if you don't store the "slice" of data you want to show in your app (ie network.cosmik.*)
🎯🎯🎯 - thanks Chris
Makes sense with this additional context/history attached....
"The name AppView came from a database processing ETL mindset, like a materialized view in postgres."
Given the above is my only significant "even better if" feedback from a first-time builder, then I'd say the protocol team have done a great job in design, implementation and docs! 👏👏👏
I would prefer something like
"...produces aggregations and *filters* to a subset of all the *data* available on the network"
And, to cater for (my!) naivety re: distributed systems, it would also have been helpful to be more explicit about likely needing to persistently store that subset of data
IME "view" is normally a term relating to UI, and it takes some recalibration when it is being used like this
"...produces aggregations across the network and *views* over some subset of the network."
Mulling this over for the last few weeks whilst building/learning around #atproto and now just going to say it...
not a fan of the "AppView" term for the first-time builder.
