Hi Robin, anything you've previously posted/shared re: project "Kill PDF"?
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.
today we had a class of young students (12-14 yr old) came to visit the @aial.ie on campus. they were so keen to learn about AI and most importantly I was blown away by the type of questions they asked us: water consumption of data centers, how openai makes money, why RAM prices keep going up, ...
screenshot of the "contributors" tab of a semble collection page showing who's contributed and how many cards they've added
little redesign of the collection page π
easily find out who's contributed and how many cards they've added π±
...and a sneak peak of collection following π€«
Tired of AI hype posts? You might like my sober assessment of whether AI-generated summaries are suitable for studying and research. Spoiler alert, they are not.
The text is primarily aimed at students and researchers, but has much broader relevance. So share freely!: www.tue.nl/en/our-unive...
Becoming risky taking a *quick* look @semble.so of a morning...so many inviting rabbit holes to get drawn down!
I bought my remote ticket to #ATmosphereConf - join me online March 2026 (well, maybe not from the get-go... a 2:30am start Down Under! π΄)
atmosphereconf.org
Community privacy is one of our top priorities at @transrights.northsky.social which isn't possible out of the box with any ATproto implementation today that doesn't just hide an entire PDS.
We're developing in the open and so I've published a proposal on it, feedback as always is we
The Solidarity Stack
"Constructing the solidarity stack will take time & involve developing a set of concrete interventions across distinct layers. However, several early efforts by communities, cooperatives, & public institutions are already reclaiming control"
ssir.org/articles/ent...
New blog post is up! When we talk about controlled data on ATProtocol, we focus on users and who they grant access to. But there's always a third party: the applications that store, relay, and render the data.
ah, that's right! I remember skim reading about this (on lexicon garden?) a while back but have yet to go through the process of formally publishing a lexicon.
thanks Wes π
weave lexicon records - pdsls.dev/at://did:plc...
collectionInterest lexicon records - pdsls.dev/at://did:plc...
Here's something I'm not sure about re: atproto/lexicon conventions - would it have been appropriate for me to create these new lexicons for Semble under the "network.cosmik" namespace?
a little demo showing how the "weave" and "collection interest" creation works (the latter pre-dates Semble's open collections, and was/is intended to cluster people around shared interests to help identify potential collaborators) 1/2
π
quick sketch of architecture...basically a case of crudely slapping together pieces as I learnt how they all worked/integrated!