I’m biased, but the indieweb chat is a good place to keep up with things people are doing on their personal sites and get inspired! https://indieweb.org/discuss
@nicopolitan Whereabouts are you in LA? I’m going to a concert at Anaheim House of Blues this Saturday. If you’re not too far away, maybe we could grab a bite beforehand.
I was reminded of ICQ today and tried logging in. I remembered my ID and the password I used from the late ’90s. Good jorb, brain.
4611084 if anyone wants to say hi.
[god creating mushrooms]
god: some go on pizzas
angel: you ok buddy?
@thetwilightsown Hey Mark, I just got an email confirmation about the album shipping (awesome!) but unfortunately my address has changed. I replied to the email but wasn't sure if a human would see it. Should I email someone else?
Oops, thought I had @contrapoints in there. Recommend her YouTube as well.
Recommended follows: @prisonculture @some_qualia @ZoeJardiniere @HappySonship @MaryNumair @ExistentialEnso @MuslimIQ
Mmm, I miss Bdubs. And you.
Want to read: Theft of Swords by (ISBN 9780316187749)
Finished reading: Finding God in the Waves by (ISBN 9781101906040)
Tantek and I were discussing the
read-status properties and the process of standardizing them in the h-entry specification. I realized
read-status may be an overly-specific property name, since the same concept might apply to listen, watch, and exercise posts. Since these are experimental properties, ideally they should be published with the x prefix:
p-x-read-status. I noted this in the brainstorming for read posts.
I’m trying to decide if/how I should update the indiebookclub Micropub request to reflect this. I know of three Micropub servers processing both properties when publishing:
The WordPress Semantic Linkbacks plugin consumes the
read-of property from webmentions to display a separate reading facepile.
The seemingly correct thing would be for indiebookclub to send these properties as
x-read-of. My first reaction is: I don’t want to break the servers above (especially micro.blog) by changing it. My second reaction is: if I do change them now and eventually read properties get standardized, changing at that point will break servers a second time. Is it better to break things once or twice? I wonder if the “best” thing to do is leave the request as-is and only update it later, once the properties are standardized. This could have the negative effect of encouraging people to keep publishing
read-of, giving the impression they’re standard.
I could make different versions of the Micropub request and let users toggle them on their settings page. To prevent micro.blog from breaking immediately, I could default micro.blog users to the legacy version. Everyone else would default to v2. Whenever the properties are standardized, v3 would be setup and become the default.
This solution feels a bit unfriendly to Micropub server implementers, so I keep coming back to wondering if I should keep it as-is and only change when it’s standardized.
I feel a bit stuck, so I’m definitely open to suggestions. Help me, Micropub masters! :]
@planetvoss Just saw your girlfriend in Ant-Man and the Wasp. Better watch out; she’s getting friendly with Paul Rudd.
@judicialnetwork Why are you sending me spam text messages?
Ahh, I think I forgot the response lines. Was it “exclamation point” and then “MOVE, LADY!”?
I’m attending “
Thanks, gee-FM. :]
Thanks, friend. Part of me feels it’s a bit self-indulgent. Like, I realize I am privileged; what am I actually doing to make the world better?
I also realize that I’m not alone in these feelings and it can be good to share, so ultimately I decided to.