IndieWeb post types

Folks posting to their own websites and owning their content, but syndicating it to sites such as https://dev.to, https://lobste.rs or https://news.ycombinator.com for better discoverability

Sorry! Hope it didn't cause too much of an issue.

I wonder if these b issues you and Aaron have seen could be related and put into the spec for implementers?

As I've gone all in on the #IndieWeb technologies, I've been using @AaronPK's service https://aperture.p3k.io which supports the open https://indieweb.org/Microsub standard, which supports RSS among other formats - may be worth looking into as it's a great protocol for building better readers, even if it's not solving your need right now. Drop me or the folks at https://indieweb.org/discuss a line if you want to talk more about it!

I've disabled that for now - I actually didn't mean to do that and have since removed it, especially as those pages are paginated so you'll effectively get webmention'd forever as I add more content to that tag

Sorry to anyone who's just received a tonne of webmentions from me - I'm tweaking the way the sending works so there are a few new places you may see them come from

I wonder what a reply on Twitter looks like?

This post has been published by my Micropub endpoint (code in https://gitlab.com/jamietanna/www-api ) and syndicated to Twitter via https://brid.gy 🙌 #IndieWeb - I'm able to own my tweets from my personal website at https://www.jvt.me and you can too by joining the folks at https://indieweb.org/discuss

Just been shown this by a colleague - it's a great way to learn shortcuts for the thing you just did and how you can do that task with a handy keystroke in the future!

An interesting idea, but surely you'd not want to break existing links to your articles, and instead have it update the article to say "this may be outdated, we're reviewing this"?

Some interesting ones in here I'll look at using - escaping things is one of my biggest gripes with every language, so this is pretty nice

I had a look at this last night and unfortunately it doesn't provide that much good data.

There's a year of listening history which may give a similar outcome, but it's not perfect

An interesting read, especially since I keep a watch on these by https://www.jvt.me/posts/2019/10/27/owning-step-count/

From me it's a no - I see why some people want it, but would rather prefer they stay out of the already limited space in the commit message title, and there's a level of arguable subjectivity of what an emoji means especially as different teams, projects and cultures have views on it.

But then again, so does written language, but I feel that is at least more known?