aaronpk2 - developers of things like gitea usually want an email address for users so that they can send notifications from the system, which has always been a pain point with OpenID even going back to the beginning
[tantek]those are both good insights, except the part about mostly your fault - I think this is something we can share responsibility and help fix as a community, so if there are ways you can delegate pieces of it to help it along, please reach out!
[tantek]we have been using "send a webmention to someone's home page" as an adhoc way of "notify someone", but perhaps that deserves formal specification
[tantek]any service that wants to "send" notifications typically has a list of them that they are sending / have sent you on their own "notifications" page for you in particular
[tantek]that's a bit of a strawman as that's not really an interesting notification and I'd consider notification abuse (silos do that when you've ignored them a while)
[tantek]presumably if it's a service you actually like / want to keep using they have some way to configure your notification references, i.e. what you see when you view your notifications page on that service
aaronpkalso from a practical standpoint, i don't want to require these developers to also understand and implement home page webmentions in order to use IndieAuth
LoqiIt looks like we don't have a page for "capability URL" yet. Would you like to create it? (Or just say "capability URL is ____", a sentence describing the term)
LoqiThe Private Webmention protocol is an extension to Webmention that supports sending and verifying Webmentions for posts that require access control https://indieweb.org/private-webmention
aaronpkWe've been through this one before. People don't always want to publish their email on their home page. Returning different content to authenticated requests ends up being a bit of work. At that point it's easier to return the email address as part of the IndieAuth response.
aaronpkIn fact openid connect already defines an OAuth scope apps can request in order to request the user's email address, which we should probably just reuse
aaronpk(The good news is as email deliverability becomes harder and harder, email becomes a less desirable notification channel, but we're a long way from it being irrelevant)
Ruxtonugh. move mailserver to new vps, upgrade mail server, something broken, no time for this, restore backup to new vps, still broke, change 2 host entres.. OH IT WORKS. shit, could of fixed that upgrade easily :(
[jeremycherfas]I like Fastmail, except for the inability to batch delete attachments but not the email they were attached to. Unless anyone knows differently.
[kevinmarks]On the "generated forms" discussion, inkstone is an illuminating example - it has a customisable way to ass multiple form elements to the ui, but they do end up a bit generic.
krychu, jjuran and [kevinmarks] joined the channel
[eddie]hmm aaronpk if I subscribe to two different feeds in the same channel, and one feed has truncated info and the other does not for the same post (same uid) do you know what will happen? Will I get two posts? will it be first come first serve or the one with more info?
aaronpki do want to solve it though, because right now i have a channel following a twitter search and also a twitter list, and i see duplicate tweets from a few accounts :)
aaronpkthe thing i want to avoid is having a situation where e.g. your website could claim to have a url that matches a post on tantek's website and override the content from that
[manton]Micropub media endpoint question for folks: Micro.blog automatically creates a poster frame when a video is uploaded. I'm thinking of returning that somewhere in the media endpoint response. Is there any precedent for doing that either in JSON or in an extra HTTP header, e.g. X-Poster-Frame or something like that?
[manton]The spec says the response is undefined, although I do include some JSON for convenience, so I could put it there too. That would platform-specific and outside the scope of Micropub, I think.
Loqi[Kickball] awesome-selfhosted: This is a list of Free Software network services and web applications which can be hosted locally. Selfhosting is the process of locally hosting and managing applications instead of renting from SaaS providers.
Loqi[Kickball] awesome-selfhosted: This is a list of Free Software network services and web applications which can be hosted locally. Selfhosting is the process of locally hosting and managing applications instead of renting from SaaS providers.