LoqiIndieWebCamps are brainstorming and building events where IndieWeb creators gather regularly in person to share ideas and collaborate on IndieWeb design, UX, & code for their own sites https://indieweb.org/iwc
LoqiIt looks like we don't have a page for "protected post" yet. Would you like to create it? (Or just say "protected post is ____", a sentence describing the term)
Loqiprivate posts refer to posts or portions of posts which are private to either the author or to a limited audience chosen or previously approved by the author (like close friends), the latter also known as friends-only posts https://indieweb.org/private_post
[tantek]I’m thinking it may be worth creating a page on protected posts since we have a few active indieweb examples and it's different enough from private posts
[tantek]Technically you already have "private" posts since WordPress has a notion of "unpublished" posts which are effectively private posts since only you can see them
GWG[tantek]: Private visibility in WordPress is not only you..it is only logged in admins. You can change who sees them. That's what I'm trying to tweak. I could make any logged in user see them, but only specific ones is a pain. I might have to create a groups feature that could allow viewing by group.
Loqiunlisted are publicly visible posts that are not included in a homepage or feed(s), and are typically excluded from site search features and broader web search services https://indieweb.org/unlisted
sp1ff, jeremy, gRegorLove_ and [marksuth] joined the channel
gRegorDefinitely some ambiguous usage of terms out there though, like people would make their Twitter account "private" which means only followers they approve, but all of those followers can see the posts
LoqiA private account is a silo account where all posts on its profile are private, and only approved followers (or friends) can see posts https://indieweb.org/private-account
GWGMicropub's extension defines visibility, with public, unlisted, or private and defines private as not accessible unless viewed by an authenticated user(see audience).
[jacky]whenever a new post is made with an audience that's non-public (or at least to an audience that doesn't signify that authorization is required), send out tickets to everyone in that list and make that list accessible by a URL (for my own use of re-use and to give people a place to request access for things on-demand)
[jacky]but whatever that last URL resolves to and however it's determined for sending tickets would be up to the implementation (which I think we could find the list of rep h-cards on that page and look for ticket endpoints for each of them)
Loqi[preview] [gRegor Morrill] I now have the building blocks for Ticketing for IndieAuth set up.
On my staging site, the metadata endpoint now advertises the ticket_endpoint. That endpoint is accepting POST requests with parameters: ticket, resource, and subject. If the request ...
[jacky] How does tickets look in a space where you're using something like http://indieauth.com?
Loqi IndieWebCamps are brainstorming and building events where IndieWeb creators gather regularly in person to share ideas and collaborate on IndieWeb design, UX, & code for their own sites https://indieweb.org/iwc
GWG [tantek]: Private visibility in WordPress is not only you..it is only logged in admins. You can change who sees them. That's what I'm trying to tweak. I could make any logged in user see them, but only specific ones is a pain. I might have to create a groups feature that could allow viewing by group.
gRegor Also from the See Also, this is wild: https://connortumbleson.com/2022/09/19/someone-is-pretending-to-be-me/