Chris Aldrich

Using the most recent update:
For public, it shows the expected location name with a link, a map, and machine readable gps coords.
For protected, it shows just the location name and the page source shows the machine readable gps coords
For private, it's still not saving properly and defaults back to public when the post is published.

@estellevw @perfmattersconf In case you missed the update from @benotist, this might help your import/export issues:
https://twitter.com/benotist/status/957987758685016069

@steveivy @sivy@toot.cafe By the way, if this webmention works, you'll probably want to update your now outdated Comments footer...

Khürt, I can feel your pain. I know that SNAP just made a recent major release that changed a lot of it's code base, so I've been half purposely waiting to update while they work out some of the kinks. I'm just about to download the most recent and test it out on a server before I upgrade to the latest version on my production site, since the old version is still doing a relatively good job and it's a lot of overhead to update/upgrade going into the holidays.

There's a frequent phrase that many in the chat will use: #ManualUntilItHurts by which they mean try doing everything manually to work on getting the output and workflow to work the way you want it to and only then try automating things based on your manual experience.

There are many ways of doing syndication, so before settling on one, try doing things by hand for a bit while you're testing out other potential options. I often find that even though I've got automated means of doing things very quickly, I actually often prefer the manual methods sometimes, particularly when it means I know exactly what the output will be. With POSSE you'll find that with some of the automated means, the easier it is to set up, the less options you'll have for control, while the more control you get means a much more difficult set up.

Try a few options and then go with what works for your needs until it drives you so crazy you have to change it. In the meanwhile, documenting the issues and problems either on your site or in issue queues will slowly help things get better.

In the end it can't be much worse than people who are syndicating their Facebook content to Twitter that simply shows up as just the raw https://fb.me/123456789 URLs and nothing else. ;)

Aaron, I finally just made the jump into microcasting myself over the holidays in as low-tech a manner as possible.
http://boffosocko.com/category/microcast/

I'll have to write up the details, but they're so scant as to make doing so more like a status update than an article. My advice, think of an idea, pull out your phone and set a 10 minute timer, hit record on the simplest recorder app you've got, and go. Post to your site and you're done. It's very liberating in comparison to all the grander plans I'd had to do something larger. And even better when you know you've only got an audience of one or two, you don't feel like you've spent thousands of hours for such a meager launch!

I do like John's idea about a slow-podcast, though I worry that the effort and time may be both painful and take some of the spontaneity and flow out of a conversation. Perhaps stringing together pieces of various microcasts using webmentions into a longer "playlist" of sorts to create a longer podcast could be an interesting idea?

Jeremy, I think this was a known issue with the WordPress Semantic Linkbacks pluin and thought it got address/fixed in a recent update. If not, do file a bug at https://github.com/pfefferle/wordpress-semantic-linkbacks

Also interesting, it looks like Independent Publisher (theme) isn't outputting a permalink for the comments on Among The Stones either. If they're webmentions, all the URLs point to the locations of of comment originals, which makes it harder to target individual comments with fragmentions.

@mattmaldre Maybe time to update https://en.gravatar.com/mattmaldre to point at the new site? :)

I'm in roughly the same situation and as a result have been posting more photos and details/status update material to my checkins.

@billbennettnz @davewiner I think I mentioned to you that @Chronotope was mulling something over along these lines:
https://twitter.com/Chronotope/status/830097158665801728

I'm curious if there's a middle ground? The way that @davewiner does his blog with updating hashes throughout the day would be interesting within news distribution, that way the URL changes, but at the same time it doesn't really. Example: http://scripting.com/2017/08/17.html#a094957 (Naturally the ability to update RSS feeds over time would be useful---as he describes in this particular post--, but it would also depend heavily on how users are subscribing to their news.) In his case, the updates are categorized by day/date rather than topic or category which is what an unfolding story would more likely do in a digital news publication.

In some sense, these hashes are related to the IndieWeb concept of fragmentions: https://indieweb.org/fragmention, though in their original use case, they're meant to highlight pieces within a whole. This doesn't mean they couldn't be bent sideways a little to serve a more news-specific piece that includes a river of updates as a story unfolds--especially since they're supported by most browsers. It would be much easier to syndicate the updates of the originals out to social media locations like Twitter or Facebook this way too. Readers on Twitter, for example, could see and be directed to the latest, but still have easy access to "the rest of the story" as Paul Harvey would say.

Depending on implementation, news sites could offer a tl;dr toggle button that gives a quick multi-graph synopsis. As I recall USA Today and Digiday used to do something like this on longer pieces:
https://twitter.com/ChrisAldrich/status/632063182811467776
Here's a version of the functionality via the WayBackMachine that still works: https://web.archive.org/web/20150818075138/http://digiday.com:80/publishers/mics-social-approach-distributing-first-obama-interview/

Imagine how powerful a long running story could be with all of these features? Or even snippets of inter-related stories which could be plugged into larger wholes? Eg: The Trump Administration's handling of North Korea seen in fact snippets over time spanning months while pieces of this could be integrated into a larger Trump Administration mega-story going back to January or even the beginning of his campaign. Someone who hasn't been following along could jump back months or years to catch up relatively quickly, but still have access to more context that is often missing from bigger pieces which need to stand on their own relatively.

#journalism #indieweb #fragmentions

The sound of your original post and the reply are making me think that you're manually opening up your site in a browser, clicking on the "Status Update" piece of the UI, then manually clicking on the "Reply to a site" button, and then manually cutting and pasting the URL in for replies every time. Does this mean you're not using the browser bookmarklet to generate all of your responses?!!

If this is the case, then hie thee to https://stream.jeremycherfas.net/account/settings/tools/ and drag the bookmarklet button (which likely has your name on it) to your browser bar! Then when you're on a web page you'd like to respond to, click on the bookmarklet to pull up a slightly more sophisticated UI (pictured in link) that will allow you to share, reply, bookmark, RSVP, like, and repost as you prefer (depending on your plugin collection). When you choose the "reply" tab, the UI should have the "reply to a site" URL pre-filled for your convenience! Type your reply, choose syndication destinations, and click "publish".

http://stream.boffosocko.com/file/7c7d5dfebbb14f620d5595395e42ef1d/bookmarklet+UI.PNG

In some sense this will make your replies only replies, your status updates only updates, and your posts articles that can only mention other articles (unless you manually do what I'd done before). In the initial case I outlined above, you're manually creating statuses which technically get turned into replies by manually adding the reply URL. The difference can be seen in visiting/comparing the URLs http://stream.jeremycherfas.net/content/statusupdates/ and http://stream.jeremycherfas.net/content/replies/.

I pray that you've known this all along, you'll forgive my "indiesplain", and that I'm not catching the subtlety of your original post. The Known bookmarklet is 90% of the beauty of the system and drastically cuts back on the manual 'til it hurts portion of the program. And of course if it doesn't make sense, let me know and I'll make a video of the process or we can do a screen share if necessary. I'm addicted to bookmarklets of all kinds, but realize that not everyone uses them the way (or to the extreme) that I do.

If not, I'm not sure I fully understand your original issue or why you'd want to create a new post (with a title) to do replies to others' content, and I'll have to revisit the issue you're having.