logue.is

logue.is

@logue.is

Reinventing social media on https://logue.is Built on #atproto

33 followers38 following19 posts

The Open Graph Protocol is effectively dead for new players who want to access it. With every major website building fortresses to protect themselves from scraping you have no choice but to use paid services. Putting social metadata in a web page html was a mistake

It affects us as well, the problem is real and frustrating

Matteo Marjanovic@matteomarjanovic.com

Is there a way we can get any answer on this? @jimray.bsky.team are you the person I should ping for this kind of stuff? Currents users that are on Bluesky PDS aren't able to save anything atm for this reason

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?

Update for the record: – the alpha (text-only) version is live and running smoothly, but before releasing it publicly we want to make a strong case study on what we are building and why it matters – Still a long way to go before the launch: PDS, media, social features, subscriptions, etc.

One of the many use cases for logue.is - an open, standardized way to get notified about new show episodes and season announcements as soon as they are released.

Who will post the updates? Ideally, publishers themselves would adopt the tool and publish updates directly, making it easier for viewers to stay informed. Until that happens, community-driven logues (along with automated scraping from open sources) can fill the gap and keep updates flowing

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

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...

.. Create automated posts on our PDS instead! To keep things tidy and ensure clear attribution, each user will get their own doppelganger: {atproto-handle}.logue.bot And posts from the bot will remain editable and deletable from the app interface, proxied and authenticated by our server

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

We’re building Logue because there’s still no humane, standard way to follow important events and topics without getting dragged into attention-farming machines.

What makes Logue different from social media like Bluesky or X is simple: the focus shifts from people and companies to topics. Follow news without following a newsroom. Follow a creator without following their entire life. Follow an event only while it's happening.

Applying this idea to all kinds of information streams is eye-opening. Every day we filter through huge amounts of information just to find the small pieces we actually care about. Why can’t we simply subscribe to what matters to us?

You are up to date.