[manton]We launched a bunch of Micro.blog improvements this week in a “2.0” update, and it also includes some recent Micropub and IndieAuth changes. Support for the Micropub “channels” proposal, IndieAuth “profile” responses, and other tweaks to the token endpoint based on recent discussions.
[manton][snarfed] No changes recently… In theory everything should be working well. Every once in a while I hear from someone who doesn’t see webmentions on their site, but not sure if that’s a Micro.blog bug or something else.
[snarfed](“The one caveat is webmentions to/from external sites. As of 2019-02-01, they’re still in progress, particularly sending outbound webmentions from original posts.“)
[manton][snarfed] Reviewing that… Yes, I think that disclaimer is out of date now. The only limitation I’m aware of is that Micro.blog still doesn’t support Bridgy because Micro.blog doesn’t have a way to show Twitter/Instagram users in the timeline.
[snarfed]re bridgy, interesting. bridgy tries hard not to be a “normal” webmention sender and not need any special cased support. do you mean that you want to special case it for silo users?
[manton]Yeah, the problem is everything in Micro.blog has a “username”. For incoming Webmentions, the username is the domain name, e.g. @manton.org instead of [manton]. But for Twitter users, using @twitter.com for everyone wouldn’t really make sense. So I have that disabled until I have a better solution.
[snarfed]the naive approach is to special case twitter and IG and include the first element after the path. but i’m sure you’ve thought about it much more deeply. lmk if i can help!
[manton]Thanks! That is definitely one possibility. It’s a bit of a can of worms… If I show the real Twitter username, what happens if someone replies in Micro.blog to that post, etc. The nice thing about using domain names for usernames is that there is no conflict with existing Micro.blog usernames.
[manton]Yeah, that is partially a problem now with other sites… You can @-mention a domain name and it will attempt to send that reply via Webmention, but if the site doesn’t support Webmention, the reply goes into the avoid (but still appears on Micro.blog).
aaronpkit's a little more reasonable with websites because there's at least a chance it will work, and there's also a way for the person being mentioned to make it work if they wanted
[manton]For Twitter, in theory I could forward things to Twitter via the Twitter API too, but it starts to make Micro.blog like a weird Twitter client which I’d like to avoid.
sknebelapparently hacktoberfest recommends using an "invalid" or "spam" label (although I think you can delete PRs too?), in case that hits some of our repos
@ArtiChmaro Interesting W3C standard (recommendation state) that lets you send/receive notifications about any URL. Perfect fit for building open platforms
https://daily-dev-tips.com/posts/goodbye-comments-welcome-webmentions-%F0%9F%99%8B%F0%9F%8F%BC%E2%80%8D%E2%99%82%EF%B8%8F/ (twitter.com/_/status/1311191870786203648)
[snarfed] oh! that’s great news! sounds like we can drop the caveat on https://indieweb.org/web_hosting#Custom_domain_silos then?
[manton] Yeah, the problem is everything in Micro.blog has a “username”. For incoming Webmentions, the username is the domain name, e.g. @manton.org instead of [manton]. But for Twitter users, using @twitter.com for everyone wouldn’t really make sense. So I have that disabled until I have a better solution.
@russss Has anything changed with @hacktoberfest this year, because it seems like everyone is suddenly getting flooded with pointless, trivial pull requests and it's not even October yet. (twitter.com/_/status/1311378451769823237)
