logue.is
logue.is
@logue.is
Reinventing social media on https://logue.is Built on #atproto
33 followers38 following19 posts
How #atproto lexicons extended with custom union type can be reused without copy-pasting? Maybe we can have something like "lexicon flavors"? Installable like: `lex install pub.leaflet#site.standard.document` @standard.site interesting if this question was raised before?
@lexicon.garden is lexicon ownership transfer (and deletion them from previous owner) not implemented yet?
Why would a big publisher adopt it instead of keeping its own notification system? #atproto makes a strong case: openness, interoperability,data ownership. They can host and brand their own logue.is instance if they want. What matters is the protocol - updates flow everywhere while they keep control
"Readers are burning out" Great talk from @aendra.com on #AtmosphereConf, but algorithms and feeds are't the answer to everything You shouldn't rely on algorithm to deliver news on topics that are important for you. The whole idea of news delivery must be reshaped into targeted, focused streams
logue.is reposted
It's taken far longer than expected, but we are here, open beta! 🚀 ready for writers to start their journey on Offprint. Soon you all will be receiving an email notifying you that your invite request has been approved. Take a look around, we will be available for any questions you may have!
pdsls.dev/at://did:plc... First logue is out ... Not fancy, didn't expect it would work
Automated and secure posting to users’ PDSes is still an undeveloped feature in #atproto. OAuth sessions are currently valid for a maximum of two years, and there’s no “offline” scope available yet. Since automated posting from external sources is essential for logue.is, we had this idea...
Overall it will look like this for logues with automations enabled (e.g. cross-posting from RSS, bluesky, api, atproto, etc.). @github.com and its co-logger @github.com.logue.bot
You are up to date.