Aaron Parecki

Sent, thanks!

same same. I reset preferences and changed renderer. It still happened again. Pretty consistently after playing a dozen or so clips in the project window.

It's a honeycomb grid to reduce how much light spills off to the sides!

The text in the spec is "Clients that have credentials and their identity has been not been confirmed by the AS are designated as 'credentialed clients'", so that includes dynamic registration or the client bringing its own certificate, so yes :-)

Suggestions welcome, but I like that it's pretty descriptive: "credentialed clients are clients that have credentials"

ew what? I don't want anyone doing my laundry but me!

I've never enjoyed watching a channel trailer, and I hate that they autoplay

I have it set up to pull my YouTube videos back to my website as blog posts that embed the YouTube video. I mostly consider my YouTube content separate right now, mainly because I am actually trying to play the YouTube game.

https://aaronparecki.com/videos

I think I saw your first reply in my micro.blog feed. This one showed up as a webmention but there was no content in it.

Yeah! I've been giving sneak peeks on my livestreams, but once I get things a little more polished off I'll do a proper video on it! (Wait til you see what I have planned for the ceiling lights!)

Sold!

Yeah! The grey is a nice flat background which I can make look black if I light it right, or cast some color on it with LEDs. There's also that pink corner which I could use as a colored backdrop, or key out. The opposite wall is teal which is also easily keyable but also looks nice as a background!

tempting

oh dang!

wait what. I'm getting a 4K this week and I don't wanna break it.

the hell kind of decision is this lol. "custom domains not allowed"?? are they _trying_ to make sure only spammers sign up?

There are still a few OpenID 1 providers and consumers left! I run a provider and am still surprised that it gets traffic.

👏 you are #1! 👏

Twitter needs a dislike button

This is the worst timeline

To clarify, the idea is to simplify this plugin by making it rely on the IndieAuth plugin for access token generation and verification? Essentially this plugin would assume the IndieAuth plugin exists and use it to verify access tokens in the requests?

if the IndieAuth plugin has the ability to then rely on remote endpoints like indieauth.com (although I still don't understand why you'd want to do that), this plugin wouldn't even see the difference right? Assuming this plugin asks the IndieAuth plugin to verify access tokens, it's up to the IndieAuth plugin to decide how to verify them whether that's it checking the local database or asking a remote token endpoint.

That seems like the best of both worlds and would simplify this plugin a lot.

I would also like to emphasize that my personal interest in this is getting more people to install the IndieAuth plugin instead of relying on indieauth.com. It's easier to tell someone to install two plugins than it is to tell them how to set up rel=me links on their home page in order to use IndieAuth.com. Also I am planning on eventually shutting that service down.