In theory, these feeds should even function to follow work associated with particular venues (e.g. conferences or workshops) and institutions. Though, because we don't have any such venues or institutions on Chive yet, that functionality hasn't been stress-tested yet.
As noted in the post, there are still some kinks to work out (mainly around interoperability with @semble.so), but the main functionality is there, including feeds that automatically populate with papers, reviews, etc. based on the authors, fields, etc. in the collection.
Our second deep dive is on one of our newest features: collections.
We have a way of associating eprints with code repos at the moment, but we welcome any discussion of what a deeper integration with @tangled.org might look like on github.com/chive-pub/ch....
Sounds great!
That would be great! Thank you!
A note on the LingBuzz integration: we are limited to new posts on LingBuzz showing up on the RSS feed. We haven’t been able to get the LingBuzz admin to respond on a deeper integration, and the LingBuzz robots.txt is very restrictive.
We're ramping up our alpha, and we'd love for you to join at chive.pub!
Since we launched back in January, we've been adding a ton of fun features; and to introduce them, we're going to be doing a series of deep dives over the next couple weeks on chive.leaflet.pub.
Layers (v0.5.0) now has a pub.layers.changelog lexicon for targeted semantic versioning of all data and metadata components in the pub.layers namespace.
docs.layers.pub/lexicons/cha...
We've also documented plans for developing an AppView.
docs.layers.pub/appview/
Discussion welcome.
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 >
Layers (v0.4.0) now has a full set of XRPC queries with domain-specific filter parameters for every record type, and a major simplification to the way segmentation works.
Github: github.com/layers-pub/l...
Docs: docs.layers.pub
Been tinkering with schemas for sharing language data over ATProto (the technology that underlies bluesky). Trying to support everything from acceptability and inference judgments to interlinear glossing to syntactic parses to eye and neural recordings. Discussion and comments appreciated. 🐦️🐦️
Layers is a set of ATProto lexicons for representing and interlinking linguistic data across modalities. We're hoping to get feedback on a draft proposal for the lexicons.
docs.layers.pub
github.com/layers-pub/layers
The citations tab for an eprint on Chive showing automatically extracted citations.
The related tab for an eprint on Chive showing automated similarity scoring.
@chive.pub now has automated citation extraction and similarity scoring!
No support for DOI minting at the moment, but it’s on the list.
Shipping automated citation extraction and paper relatedness features.
Should only be brief as a new deployment runs.
We're staging application approvals to allow for bug fixes between stages. If you have already applied and are waiting on approval, thanks and we'll try to get you approved as soon as possible!
Thanks! Happy to receive issues or discussions around anything like this: github.com/chive-pub/ch...
Yes! We actually have a @semble.so backlinking service as one of our builtin plugins! Other integrations can be added using our plugin system.
Fixing it now!
We're fixing this issue now.
Right. It also has a knowledge graph stored in a centralized PDS that can be expanded by community proposal/voting, where proposals and votes live in user PDSes. Papers, authors, fields, and institutions are all nodes that can be typed against concepts imported from external graphs like Wikidata.
When the closed alpha goes live, we'd love you to join and hear your feedback on how best to do this.
Oops. Yup! @semble.so.
Closed alpha launching soon at chive.pub! Follow for details!
Everything is public at github.com/chive-pub/chive
The stack is TypeScript, Hono, PostgreSQL, Elasticsearch, Neo4j, and Next.js.
You use the same identity across Chive, @bsky.app, @semble.app, and @leaflet.pub. No new account needed.
You can also share eprints directly to Bluesky with rich previews.
