GWGsknebel: Ticket Auth was based on the principle the publisher sends to a ticket auth endpoint, which is integrated in some way with the Microsub or other endpoints
GWGSo, if you have a public feed that includes private posts, that behavior doesn't require anything new, except maybe markup on the private posts that can indicate that in the reader. But like any new property...non-aware readers would still work.
[tonz]Is anyone here automatically adding archive.org links to links they mention in their posts, and if so have you documented somewhere what the steps were you took to get there?
[fluffy]1I’m guessing this has something to do with the IRC gateway? Maybe something caused the Slack gateway to decide that there was a collision that had to be fixed, and I lost out 😛
[fluffy]1Folks always talk about the “forcing function” requiring adoption and I think that is one of those situations where, like, most people here don’t have the forcing function of needing to post/share restricted-audience posts, and either nobody is aware of the private posts that are being made or don’t have enough interest in following them from a feed reader.
[fluffy]1It’s worth mentioning that I’ve been making restricted-audience posts for *years*, now, and as of maybe a year ago they’ve been accessible via TicketAuth as well.
[fluffy]1I’ve had a notion of maybe making a TicketAuth feed proxy thing to make it easier to use TicketAuth from a reader perspective without needing to add the entire protocol/flow/etc. to a reader. That would have the usual privacy issues with private-URL feeds though.
[fluffy]1Like if someone were to share an item from an Atom-based sharing feed (e.g. Feed-on-Feeds) that would broadcast the private feed URL along with it.
[fluffy]1Not really a concern for IndieWeb’s sharing model but still something I’d worry about because of whatever random feed readers are out there that still support Atom sharing feeds.