WeChat ID
aaronpk_tv
-
I don't see this IndieAuth plugin installed on pfefferle.org: https://pfefferle.org/wp-login.php There's only an OpenID option there. Can you clarify exactly what you are expecting to happen? -
@pfefferle Yes, that's what the built-in authorization server is for. You can log in to indieweb.org using your domain, where you authenticate at your own wordpress.
Authenticating *into* your wordpress using Twitter/GitHub/other-rel-me things is a totally separate thing, which is why I'm suggesting pulling that out into a separate plugin. -
Not sure what you mean, how does that change anything?
-
I'm not really sure how to solve the UI around this. tbh I think it would make sense to pull out the "log in to your wordpress" feature into a separate plugin, preferably called RelMeAuth or IndieLogin (to match the upcoming indielogin.com that I'm working on), since logging in to wordpress with your domain isn't actually doing IndieAuth.
I'm worried that having both in the same plugin is going to continue to confuse people. -
Yeah I don't think that makes any sense, since you'd have to be logged in before you can log in. It only makes sense to sign in to wordpress using your domain if you're using an external authorization server.
-
@pfefferle what authorization server is it set to use in that case?
-
It worked for me, but of course I had to set the authorization endpoint in the settings back to
https://indieauth.com/auth.If you have the authorization endpoint set to the built-in one, then it would be kind of stuck in a weird state. Which brings me to another point. How do I know what the URL for the built-in authorization endpoint is? Right now if I change it to indieauth.com, then I have no way of knowing what to change it to to make it go back. Blanking out the value just stores a blank value which breaks it. Can you make it revert to the default built-in URL if a blank value is saved?
-
Hey Portland-area friends of The Credentialed: Join us for an intimate event May 9 w/ our sister @XRAYfm podcast @OhMyDollar for a chat about #digital/#tech & #personalfinance #privacy with @PrivacyForum at the awesome @The_Red_E Coffee! https://www.eventbrite.com/e/a-privacy-chat-with-xrayfms-oh-my-dollar-the-credentialed-and-world-privacy-forum-tickets-44904704179 #pdx @pdxevents
-
-
Joschi Kuphal 吉
https://jkphl.is
•
Apr 5
Aaron, you should check out @colloq_io if you haven't done so already. Aspiring service by some awesome guys with a great mindset (you could've met them already). Forget @Meetup ...
@colloq_io looks great, but unfortunately it's a matter of convincing local meetups to switch off Meetup.com. Meetup.com has all the users, so it's a hard sell. -
Randall Degges
https://www.rdegges.com
•
Apr 4
I just discovered the amazing beauty of CSS' `object-fit: cover;` Wow. So incredibly useful for like... Every single one of my projects: https://buff.ly/2Jh21nc
CSS has gotten pretty great lately, it's nice to not feel like I'm fighting it all the time now! -
wow @meetup, classy. Removing a group's list of sponsors that you used to show on the meetup page, then charging them $30/month to add the sponsor section back? Yeah I'm not gonna play this game.
-
Allow the user to set a default category for posts created by the application
A common feature request I hear from people using Wordpress with Micropub apps all the time is they want certain apps posts to appear in certain wordpress categories by default. For example, all posts from OwnYourGram should be added to the "Photos" category, all posts from OwnYourSwarm should be added to the "Checkins" category, but posts from Quill or Micro.blog should be "Uncategorized" or set to "Microblog". With the built-in authorization server, there is a great opportunity to have the wordpress plugin handle this now. It will take coordination with the Micropub plugin as well.continue reading... -
return get_option( 'micropub_default_post_status', MICROPUB_DRAFT_MODE ? 'draft' : 'publish' );This doesn't work because the problem is not that
micropub_default_post_statusdoesn't exist, it's that it does exist in the database and the value is blank. -
Was able to reproduce this after carefully reading the other thread. The key is this: https://github.com/snarfed/wordpress-micropub/issues/104#issuecomment-359267767
If you save the writing settings page, it writes a blank value for
micropub_default_post_statusto the database, so then theget_optioncall later will return the blank value instead of the default. -
Can confirm that this problem does not exist on a clean wordpress install with the current 1.3 release. I'm trying to track down what causes the error to surface.
-
Hillsboro, Oregon • Tue, April 3, 2018 9:18pmBack for the afterparty
