Peter Molnar (petermolnar.net)I spent a lot of time trying centralising my online activities, including adding bookmarks and imports from social networks. Lately my site looked bloated and unmaintainable. I started questioning what data is my data, what data should or could I own - it was time to rethink some ideas.
Somewhat like him, I’m bookmarking things I’d like to read privately on the back end of my site, and then only selectively posting them as read posts when I’ve done that. Archiving them to the Internet Archive has been useful for cutting down on the data I’m keeping, but saving them does allow me to browse through my commonplace book frequently when I need to find something and couldn’t find it otherwise.
Some of this reminds me of the way I use the “star” functionality on Twitter (I still think of it as a star and not a heart). I don’t typically use it to mean anything in particular on Twitter itself. Instead I’m using that functionality in conjunction with an IFTTT recipe to bookmark things I’d like to read later. So in a larger sense, I’m using Twitter as a headline feed reader and marking all the things I’d like to come back and read at a later time.
Once in a blue moon, during a chat with others on Twitter, I may use the heart as an indicator to the other party that I’ve seen/read their post, particularly when I don’t intend to reply to the last in a chain of conversation. This type of ephemera or digital exhaust generally isn’t something I find useful for keeping in the long term, so like Peter I typically don’t keep/archive them on my site.
For those who haven’t read them yet, Sebastiaan Andewe has a recent article covering similar ground: Thinking about bookmarks and likes on the IndieWeb.
I find these discussions useful for thinking through what I’m doing on my own site and refining how I use it as well.​​​​
Chris, your website is the only site where webmentions from my website fail.
It works on every website I have tried.
https://islandinthenet.com/google-amp/
https://islandinthenet.com/ai-natural-selection/
https://islandinthenet.com/veil-ignorance/
Here’s the link to the post: https://islandinthenet.com/testing-webmentions/
@khurtwilliams Kudos for your tenacity! I just saw your notes on my site. The first http://boffosocko.com/2017/10/28/content-bloat-privacy-archives-peter-molnar/#comment-37986 appears to have been sent first as the webmention. The second two (http://boffosocko.com/2017/10/28/content-bloat-privacy-archives-peter-molnar/#comment-37984 and http://boffosocko.com/2017/10/28/content-bloat-privacy-archives-peter-molnar/#comment-37985) appear to have been input manually in the comment section of my site.
I’m guessing you didn’t see (or possibly get the webmention–unless you’re careful WordPress can often put webmentions into your spam queue) my other reply the other day that explained the issue. You can find it here (http://stream.boffosocko.com/2017/kh%C3%BCrt-ive-figured-it-out-then-id-seen-the-issue or here threaded into the commentary http://boffosocko.com/2017/10/25/your-licenses-frankly-my-dear-cogdogblog/#comment-37780), but I’ll also manually syndicate my replies to you as well. Hopefully the explanation will solve your mystery.
By the way, once you fixed the URL on your first original webmention, it did come through and is listed in the Mentions subsection at the bottom of the comments: http://boffosocko.com/2017/10/25/your-licenses-frankly-my-dear-cogdogblog/#comments It shows up as a mention instead of a reply, because the URL that fed through was the raw one (i.e. without a class in the body of your response). If you fix the emoji portion and click save that URL will have a u-in-reply-to which should cause your response to show up and be parsed properly as a reply instead of just a vanilla mention).
If you’d like to discuss the subtleties of any of this in person, feel free to catch me on my phone number on my homepage. 🙂
Syndicated copies:
@khurtwilliams Kudos for your tenacity! I just saw your notes on my site. The first boffosocko.com/2017/10/28/con…… stream.boffosocko.com/2017/khurtwill…