#Loqimulti-factor authentication (commonly two-factor authentication, abbreviated 2FA or TFA) is an authentication process that requires at least a second component to a standard authentication method https://indieweb.org/two-factor_auth
#aaronpki keep ending up at dead ends from micro.blog because it prioritizes peoples' canonical URLs (a good thing)
#aaronpkbut then those URLs don't link to the micro.blog "conversation" link
#aaronpkso I can't reply to the conversation on micro.blog or see the conversation
#aaronpkbut the quick fix is that the micro.blog-hosted theme could include a link to the micro.blog permalink for the post as a u-syndication link
#aaronpkstill need a good fix for people (like me) who self-host but also pull their content into micro.blog, but at least this would solve a bunch of them
#Loqi[Zegnat] #23 Client Information Discovery without relying on microformats parsers.
digitalcold0 joined the channel
#tantek__looks like old Flickr monthly calendar view archive links don't work any more
#tantek__there used to be a way to show a calendar month grid view that showed you the most recent (and count of) photos for each in the square for each day of a month in a typical month view
snarfed and [eddie] joined the channel
#[eddie]aaronpk: the way that Micro.blog hosted sites are separated from the social network aspect I don’t know if that would be a “quick fix” or not
#ZegnatOn alternatives for mf2 h-app? web app manifests are looking like a good recommendation for the standard to make. I’ll do a run through and check for rel-icon (and related) places to look for logos in a bit
#ZegnatAlso toying with the idea of writing a proof of concept implementation where it extracts the info from a manifest file
[kevinmarks], mblaney and [jgmac1106] joined the channel
#[jgmac1106][tantek] much of the old flickr tools were built on flash, a lot of the old stuff doesn't work anymore
[jgarber], [stefp], KartikPrabhu and [manton] joined the channel
#[manton][aaronpk] [eddie] Yeah, it's not a quick fix to add u-syndication, but it would be a good change. I've been wanting to do that for Twitter links to improve compatibility with Bridgy and other apps too.
[aaronpk] joined the channel
#[aaronpk]My suggestion was that since micro.blog knows the micro.blog url it can at least add u-syndication to the hosted blogs that it's creating. I realize it's a harder problem for self hosted blogs but it would be a huge improvement
#[manton]Yep, I get it. The reason it's tricky with the current design is that Micro.blog publishes the blog as static files, then reads the feed, then builds the timeline from that. To add u-syndication it needs to feed that info back to the blog afterwards, since at the time of posting it doesn't know the syndication URLs.
#[manton]Basically, Micro.blog doesn't even know the URLs yet when the post goes through. This separation makes things as consistent as possible between different types of blogs, but there are some trade-offs.
#[tantek]Jgmac1106 huh? The calendar grid view of Flickr archives was just a url you could navigate to, share etc. zero use of flash. All backend, likely PHP IIRC
#ludovicchabantYeah I always found u-syndication weird too for the same reasons as [manton] (I have a static website)
#ludovicchabantWhat’s the use case for it? From the wiki, I’m not sure I understand... it sounds like the goal is to reply not only to the original post, but also to have the reply’s POSSE posts to reply to the original POSSE items?
#[eddie]There are other purposes ludovicchabant like for example, aaronpk mentioned that he is having a hard time being able to see a full conversation on micro.blog from a single individual response.
#[eddie]The only way to get to the conversation on Micro.blog is to have the syndicated url of the post on Micro.blog itself, in order to see the other posts in the conversation.
#Zegnatu-syndication links from a post point at places where you have posted a copy of the post. E.g. if you POSSE’d to Twitter, your website can have a u-syndication link to the Twitter copy of the post.
#ZegnatThis can help other people (or Bridgy?) to syndicate their replies correctly. If I write a reply to your blogpost on my site, and I POSSE my reply to Twitter, I can use the u-syndication link to find your Twitter copy so my Twitter copy can be a reply to that.
#ludovicchabant[eddie] can't seem to find aaron's original explanation of the problem, so by "see a full conversation", do you mean "from my website" or "from a Micro.blog client"?
#ludovicchabantthe Micro.blog UX still requires some improvement for conversations -- like for instance yeah, if I catch a conversation in the middle (via a single reply), I can't seem to see what other post this reply is directly replying to. Instead, I just get a seemingly unsorted (or probably just chronologically sorted) list of MB replies
#[eddie]We use Micro.blog from our own websites through webmention and JSON Feeds
#ludovicchabantbut that's probably just a UX problem, as all replies have a proper u-in-reply-to... so I assume Aaron's problem is when some of those replies happen to be POSSE'd stuff instead of original MB replies?
#ludovicchabantI just POSSE my original posts to MB/Twitter/Mastodon/etc, but handle all the replies natively in each silo individually, so I guess I'm sidestepping that problem
#[eddie]Correct. The issue is where there is POSSEd replies then you end up at the original posts (which is good) but no way to find the Micro.blog convo
#[eddie]And that’s not an issue if it doesn’t matter to you. [cleverdevil] for example tends to reply within M.b a lot as well
#ludovicchabant...which is one of the reasons I do what I do :) it prevents all these kinds of problems, plus problems with having silo-specific things showing up in other silos with weird formatting, etc. (like if you reply to a Tweet and POSSE that to MB or whatever)
#[eddie]Yeah it definitely makes things more complicated. aaronpk and I do it the harder way to continue to smooth those use cases out so eventually it’s smoother for people to do it that way
#[eddie]Plus with our Microsub readers, it’s convenient to have everything in one spot. I never open any native Twitter clients anymore
#ludovicchabantfor static websites, having to double-bake the HTML would be annoying, but any other solution would probably not feel consistent with other MF2 stuff ... :(
#[eddie]My website was static so I definitely understand the pain of having to deal with the html a second time
#[eddie]I haven’t kept up to date on the Twitter updates... I hope they don’t break my plans :crossed_fingers:
#ludovicchabantI see the appeal of Microsub stuff but I don't like the idea of having it "at my website". I haven't checked if it's friendly to having it at another URL/server though -- I would assume it would be fine.
#ludovicchabant[eddie] I think it the Twitter updates prevent you from being notified of likes/RTs anymore? (just replies?)
#[eddie]Yeah. Currently your website only has to have a rel=Microsub link on the homepage and support IndieAuth. The rest can take place in an external Microsub Server that you trust
#skippyif microsub could expand a micro.blog discussion, that would be cool, too.
[jgmac1106], jackjamieson and [manton] joined the channel
#[manton]@ludovicchabant Yeah, I want to improve the conversations UI. Micro.blog does keep track of the hierarchical details of a thread (which reply is being replied to) but it just shows them all flat currently.
[jgarber] and snarfed joined the channel
#@qubyte↩️ And if you're a web dev like me, it's extremely satisfying to roll a little static site generator and play with things like microformats and webmentions. (twitter.com/_/status/1031553113583493122)
KartikPrabhu, [cleverdevil], [deeden], leg and [jgmac1106] joined the channel
#[jgmac1106][manton] I am going to try and spend some time debugging why my @mentions don't work, when syndicating to WP...though I think the conversation UI long term will be supported by plugins trying to join the micro.blog conversation, I think what I am going to do is change my feed and just create a tag for posting to microblog rather than my entire feed...this way I can hop in and out of the network and avoid decontextual cross chatter from other
#[jgmac1106]but a micropub solution with a checkbox of publish to micro.blog would be awesome
#[eddie]jgmac1106: If Wordpress presents a "Micro.blog" syndication target, and then every post that comes in with that syndication url (your m.b profile url) ends up in an RSS feed and you give that RSS feed to Micro.blog service to consume, you create a more controlled Micro.blog syndication experience
#[eddie]That's what I do personally, and Indigenous for iOS and for Android should both support syndication target selection as well as Quill
#[eddie]Also jgmac1106 regarding @mentions, do you mean when you are attempting to send @mentions to people in Micro.blog? Currently each person's server is what generates the @ mentions, so being a Wordpress install, Wordpress will need to take any @name and make it into an html `<a href="https://micro.blog/name>@name</a>`. Micro.blog looks for that HTML markup in the RSS feed content and sends an @mention notification when it sees a link like that in
#[eddie]the fallback behavior allows me to @mention people on m.b that I don't want to add to my nicknames cache
#[eddie]I've thought about doing the same thing for Twitter but I just don't really use Twitter to @mention people anymore. Really I just use it to reply to people or syndicate generic posts
#Loqi[Bobby Moss] Friendly reminder: this isn't Twitter.If you're mad about something? Use a content warning.If you want to write a long post? Use a content warning.Don't share screenshots of toots that make you mad, and don't follow people that make you mad.You've le...
#[eddie]I think spoiler/cw can be helpful in some areas but it seems like Mastodon has gone over the deep end with those. Definitely something to be careful about as we think down a content warning/spoiler approach
[manton] joined the channel
#[manton]It's interesting that of all the possible places in the UI to innovate, Mastodon chose content warnings. I know some users love them, but I don't get it... They have 2 obvious drawbacks: they don't help with truly hateful or harassing posts because those people aren't going to use content warnings, and extra clicks, which goes against a goal with microblogging of making blogging more effortless and so approachable to more people.
#tantek__eddie, agree. "more..." is not the same as Content/Spoiler warning etc.
#Loqicontent warning is a feature of a post create UI where an author can hide by default some or all of the primary content of a post due to some concern about the nature of the content https://indieweb.org/content_warning
#[eddie]Yeah, that’s really what I want CW for in mf2 world is to be able to say post about Game of Thrones and just put “Game of Thrones CW” and then type about the latest episode
#Loqi[Bobby Moss] Friendly reminder: this isn't Twitter.If you're mad about something? Use a content warning.If you want to write a long post? Use a content warning.Don't share screenshots of toots that make you mad, and don't follow people that make you mad.You've le...
#tantek__eddie - yes! great example. Can you start a "Brainstorming" section on /content_warning and add exactly that? Makes total sense and the more we can document that as sensible use of CW, the better.
#[manton]If you'll let me push back on the spoilers example a little... 🙂 What if everyone wanted to write about the Game of Thrones finale. Hundreds of posts in your timeline over a few hours, all about Game of Thrones. Do you really want CW on all of them? That is a lot of clicking and will make the timeline nearly unusable.
#[eddie]That’s fair. I wonder if there is some way to group those
#[eddie]So when you “unlock one” you can unlock them all
#[manton]And out of 100 posts about Game of Thrones, if 99 have CW (unlikely) and only 1 has "the dragons eat everyone", all those CWs have introduced friction but you are still getting the spoiler.
#[eddie]True. Do you have other ideas about how to mitigate this? Should this be more about adding mute filters into readers?
#[eddie]So I can say “hide anything that says Game of Thrones or GOT”?
#tantek__manton your "What if everyone" is a slippery slope fallacy. that doesn't actually happen in practice.
#[manton]I think advanced muting could be really useful here, yes... But I don't have a lot of new ideas. (I'm mostly trying to think through CW, not just trying to be negative about it.)
#[manton][tantek] True, I shouldn't say "everyone" since that's an extreme version of this. (Although with GoT, who knows.)
#tantek__"still getting the spoiler" can / does happen, but in practice people unfollow those people (or give them stern warnings, or teach them how to use CW, and then unfollow upon 2nd or 3rd social violation like that ;) )
#tantek__yes in practice people will still misbehave in some way, so you can either unfollow them, or spend time talking with them to reduce future misbehaving, depending on how much time that relationship is worth to you
#[eddie]That’s true, you can unfollow the people. I guess the question is where should the prerogative be on this stuff? The people who write or the people who read?
#[eddie]CW is on the writer and Muting is on the reader.
#[manton]Also worth documenting here is Twitterrific's "muffle" feature, which is muting but with a CW-like interface. Instead of muted posts disappearing altogether, they are collapsed in the timeline.
#[eddie]That and syndicating tweets are the two most useful Bridgy functions for me right now
#snarfedlol. also github backfeed started as best effort only, from the beginning. low expectations and all
#[eddie]snarfed++ for taking the 1,000 cuts on our behalf
#Loqisnarfed has 65 karma in this channel over the last year (118 in all channels)
#[manton]muffle is a feature of Twitterrific for muting posts. Instead of hiding the posts in the timeline, matching posts are minimized and can be expanded to reveal the full post.
#tantek.comedited /SMS (+850) "IG with citation, their MFA makes your account *less* secure" (view diff)
[grantcodes] joined the channel
#[grantcodes]snarfed: I posse my instagram likes, and photos automatically. Dunno if I can help you much but the library I use probably would get like data
#Loqi[huttarichard] instagram-private-api: Instagram NODE.JS private API
#snarfed[grantcodes]: i'd actually love to hear if it can get the individual likes for arbitrary (public) photos. if you have a chance to try, i'd definitely appreciate it!
deathrow1|absnt and [iambismark] joined the channel
#aaronpk[eddie] how close are you getting to that push notification api for indigenous? I'm finding I want to experiment with notifications the less I use FB/TW/IG
#[eddie]My need for notifications has definitely been rising as well, so it’s pretty high priority for me. Not all Microsub servers will offer WebSub though, so I guess for basic functionality I should have a server that just periodically fetches the channels and sends a Push Notification
#[eddie]Then WebSub can be an upgrade if the Microsub server returns it
#sknebelhm. authenticated websub? guess adding a token to the registration and tying subscription lifetime to the token existing?
#[eddie]Ohhhh I hadn’t thought about that, authenticated websub may not have been done before?
[shaners] and [jgmac1106] joined the channel
#[jgmac1106][eddie] I wonder then if something is wrong with my rss feed, I am doing the mention to micro.blog correctly
#Loqi[Greg McVerry] @cleardevil asking @photomatt about WordPress and #IndieWeb
#[eddie]Because that @’s don’t see to have hyperlinks
#[jgmac1106]no bc that one was directed at twitter, hand coding every time for micro.blot too big a PITA
#[jgmac1106]I have to reserve it for when I am trying to link into a conversation there, one sec
#[eddie]Are you trying to mention people in REPLY to another post? Because that can happen automatically
#[eddie]So there are mentions where you are writing a post and just pinging someone in the post, and then there are mentions when you are replying to an existing post
#[jgmac1106]but have their @name linked...let me just publish a new example rather than try to find one
#LoqiA silo, or web content hosting silo, in the context of the IndieWeb, is a centralized web site typically owned by a for-profit corporation that stakes some claim to content contributed to it and restricts access in some way (has walls) https://indieweb.org/silo
#[eddie]So it’s not a silo, based on the fact that Micro.blog does *not* stake claim to the content and does not restrict access.
#Loqi[jgmac1106] @bradenslen Thanks for helping me connect on @microdotblog Also on:
#[eddie]Correct, jgmac1106 that’s because the RSS feed doesn’t link
#[eddie]There is no hyperlink in the RSS feed, even though there is on your permalink page
#[eddie]the description field on the RSS feed needs the <a href> that the permalink page has
snarfed joined the channel
#[eddie]Gotta head out to dinner, but if you can get your RSS feed’s description field to contain the <a href> from your permalink, Micro.blog will work just like you expect
#snarfedtantek__: no. IG started requiring an extra authenticated HTTP fetch to get likes on the web site, which bridgy scrapes. i worried that would mean the end of IG likes backfeed, but this ^ is an ugly workaround