pk
https://toot.cat/@pk
•
Jul 2
toot
WeChat ID
aaronpk_tv
-
tootback! -
tootback
-
Manton Reece
http://www.manton.org/
•
Jul 2
Oh yeah, if whatever is checking for link tags doesn't mind it being anywhere on the page, that should work!
Give it a shot! I think most things are parsing the whole page for the rel values. -
James R. Hull 🎬
http://narrativefirst.com
•
Jul 2
Yes, hosted but no, I don’t think you can do that. They added some new IndieAuth stuff over the weekend but I don’t it covers this yet
@manton2 *just* posted that you can add custom HTML to the footer now! http://www.manton.org/2018/07/micro-blog-hosted-footer-html-and-redirects.html so I think you can add a link to a microsub server there now! -
oh no me too!
-
Did I ever end up talking to you about this? IndieAuth is a solution to this exact problem, as it replaces the need for client registration with making client IDs be the URL of the app and omitting the secret. (You can't use a secret on mobile apps anyway.) IndieAuth means apps don't need a prior relationship with the server.
-
dpdp
https://mastodon.xyz/@donpdonp
•
Jun 18
I was reminded today that http://24hoursofhappy.com/ is still going and is still a lot of fun to watch.
I never knew that was a thing, but I am glad I do now! -
always coming home
https://cybre.space/@nightpool
•
Jun 14
i have 78 tabs open.
i should.... probably do something about that
I have... 60 tabs open: https://aaronparecki.com/now/ -
tootreply
-
Good point! I should have mentioned that. Also there's http://sendawebmention.com (Telegraph)
-
toot?
-
ahhhh I had to stop 30 minutes before the end last night! Can't wait to finish!
-
Yep! For comments from Twitter, Bridgy creates the web page and sends the HTTP request so that you can receive a webmention from a tweet just like you can receive a webmention from a normal web page. Bridgy doesn't help with sending webmentions tho.
-
whoa that eye
-
UI feedback Ian a great idea. I would suggest the app turn the button a different color while the Micropub request is pending, then changing to the confirmed state after it gets the Micropub success response. If the Micropub request fails for some reason then it could turn the button into yet another state to indicate the error. It also sounds like maybe the app could at least maintain its own cache of posts that it has created likes for in order to be able to show whether a post has been liked before. I think there's also an open issue on Microsub to return that info in the post data as well.
-
manton
https://micro.blog/manton
•
Jun 29
@trevorstinson @Scotty @macgenie I'll look into the email delays. There are other things we could do in addition to email (like push notifications) to improve the experience. Also, if there's a reason you are signing in often, maybe that's the root issue that we should address.
I'm a big fan of push notifications for login! I have that set up on my own website right now! https://aaronparecki.com/2017/10/04/23/passwordless-logins #passwordless -
cheesemaker
https://micro.blog/cheesemaker
•
Jun 28
@TheDimPause yes. I’m guessing a number of people here follow him. 🤪
Wait haha what'd I do? -
Aaron Parecki
https://aaronparecki.com/
•
Jun 28
Thanks so much to everyone who participated in #IndieWebSummit this year, both in person and remotely! It was really inspiring to see so many people who care about owning their online presence together! #indieweb
-
I actually have an open issue on Aperture which would help in this situation. The idea I had was to treat every Aperture channel as its own IndieAuth identity, so that you could log in to Micropub apps and they'd end up posting into the Aperture channel. The cool part of that is the apps wouldn't even know that they're posting into an Aperture channel, they just see it as a Micropub endpoint.
Your idea of just treating some channels as writable is also interesting though. The only trick is I can't picture the user flow of how to actually have the app request and get the permissions for that. Definitely worth further thought though!
-
In order to continue the OAuth compatibility, this would also mean that the code exchange (token request) step would need to work without the
meparameter as well.This breaks the ability to use a shared token endpoint between users, since the token endpoint wouldn't know how to verify the authorization code without the
meURL at that point. The workaround for shared token endpoints is to have a per-user token endpoint URL, liketokens.indieauth.com/user.example.com/tokenkind of like how I have per-user webmention endpoints on webmention.io. I'm not sure I'm super happy about this though.
