[chrisaldrich][hollie] Your application to my Known install was accepted. (I still haven't figured out the error it threw, but at least it's not wholly broken after all this time.) Hopefully there's enough there to give you an idea of some of how it works without having to spin up your own version.
aaronpkTIL my posse code fails if I try to reply to someone who limited who can reply to the tweet: "The original Tweet author restricted who can reply to this Tweet."
[jeremycherfas][hollie] I use Known as my main micro blogging stream and I get that error all the time. It is a meaningless error, because in fact I am always logged in after I get it. Known is not easy to tweak to get precisely the look you want. The templating system is pretty arcane.
BlackPirateX, Hollie, [fluffy], [chrisaldrich], [echo], [schmarty], [James_Van_Dyne], [Scott_Jack], [aimee] and IWDiscordGateway joined the channel
capjamesgThe poll vote contents is sent in a ?contents= query string or something like that. It translates to whatever micropublish.net uses (I don't know why I can't remember this haha.)
[CrowderSoup]I wrote more details ^ about the proof-of-concept I built w/ a serverless function in Vercel. I’m excited it worked as I expected. Now I “just” need to start implementing on my site 😄
[tantek][hollie] see the message above from [manton]. You can use micro.blog for all your posts, and have people not on micro.blog comment on your posts via Twitter, which seems reasonably accessible, and a 280char limit also seems reasonable for comments
[hollie]That's a great feature for sure, but that makes it accessible for Twitter users. The vast majority of crafters, sewists, and artists I know aren't on Twitter. The same reasons that I want to own my stuff, to feel like I have a little house on the internet where I can share all my hobbies and interests, are also why I want that house accessible to everyone who might want to comment. It feels incongruent for me to say, "I'm doing all
[hollie]this to stay off silos, and maybe inspire you to stay off silos, but you have to be a member of one of those silos to participate in a discussion here."
[hollie]I was playing around with my micro blog last night and I really love the design, but even when I'm logged in, I can't figure out how to respond to people if I'm just looking at an individual's site. There are no "reply" links at the bottom of posts unless I'm viewing a post from my own feed, logged into my account. If I am still logged in but view someone else's micro blog via their domain (so for instance www.choosendomain.com vs.
[hollie]micro.blog/username), then I don't see any way to comment at all. One user I really like, Miraz, she has an email link at the bottom of her posts, which is cool! But then when I click that, it of course auto-opens my Mail app, which I loathe and don't use. And even then, I don't see any comments on any of her posts (I assume they're only available if you're inside your feed, viewing her posts? or do the email comments show up at all?
[tantek]interesting re: no "reply" links. [manton] I wonder if there's an opportunity here to explore using web action links/buttons on micro.blog to help encourage peer-to-peer replies?
[snarfed][Chris_Lott] we're big micro.blog fans here, but not many of us are deep users. maybe check out https://help.micro.blog/ or ask on m.b itself!
[manton]Yeah, this reply confusion is a longstanding issue… There is a Micro.blog plug-in called “Conversation on Micro.blog” that adds a link back to Micro.blog from your blog post. I have plans to make something like that built in, with a way to reply directly from a blog post.
[manton]I think in the early days I was worried about putting Micro.blog links all of your own blog, because it’s your space, but having a simple option for this would make things easier and more comparable to WordPress comments.
[manton][hollie] To clarify for Miraz’s site, the email link is really just sending a private email, it isn’t automatically tied back into Micro.blog at all. Definitely room for improvement here, so I appreciate the feedback!
@brianleroux↩️ IndieAuth is pretty slick. Feels very right to use my own domain as my identity. I spread the functionality over 8 or so cloud functions but none where more than 50 LOC. They'll scale forever up, and down. More than likely always within free tier. Pretty big upside over WP. (twitter.com/_/status/1532798974955880448)
[hollie][manton] Oh you're so welcome, thank you so much for doing all this work! Micro.blog is so cool! On Miraz's site, I feel like the email option is a legit option by itself. As in, I could see wanting a site where I made it easy for people to quickly send me a comment privately, a note in email, but not want comments fed back to the post. I see that as "private blogging" in a way - like maybe I want to connect with people individually,
[tantek][manton] I think your concerns about putting links on people's blogs are spot on. I think the key here it make it opt-in in some fairly "easy" way to at least put a "Reply ↩" link if people want to make it easier for other micro.blog folks (or other IndieWeb folks) to reply to their posts.
@brianlerouxIndieAuth is pretty slick. Feels very right to use my own domain as my identity. I spread the functionality over 8 or so cloud functions but none where more than 50 LOC. They'll scale forever up, and down. More than likely always within free tier. Pretty big upside over WP. (twitter.com/_/status/1532798974955880448)
[manton][tantek] Nope. We get a lot of spam blogs created, so the total number of blogs is not very meaningful right now… Working on some new tools to better clean things out.
[manton]Yeah. One change I made this year is to not allow Google to index free trial blogs, which I’m hoping will negate any benefit these folks think they’ll get by creating a 1-page spammy blog of links.
[manton]I’m curious how Tumblr and WordPress.com handle this. I expect at their scale they don’t have a complete handle on this kind of issue either. It’s a little more manageable for us but still not perfect.
[tantek]I mean, the whole notion of open security protocols is based on the opposite assumption, that documenting the protocols openly helps *strengthen* them against bad actors