Keep Comments Open! by Dan Allosso

Some thoughts about the ability to turn off public comments on Substack posts, which may diminish the conversation.

https://sparkles.sploot.com/

https://www.zylstra.org/blog/2022/08/added-hypothes-is-annotations-link-to-posts/

Also... just to show the functionality. (aka: First!)

I love that you've got a comments heading for Hypothes.is annotations on your post @tonz! This is awesome.

https://cathieleblanc.com/2022/06/21/photo-sharing-work-flow/

Spencer's example of user interface below his posts to indicate how readers might comment on his website.

https://spencergreenhalgh.com/myself/embedding-hypothesis-as-a-commenting-system-on-hugo-static-sites/

Social annotation at it's deepest and finest!

@spgreenhalgh, Are you checking for comments manually only?

I've seen a few doing this pattern before:<br /> - https://boffosocko.com/2021/03/25/hypothes-is-as-a-comment-system-receiving-mentions-and-notifications-for-your-website/<br /> - https://boffosocko.com/2020/05/26/55771462/

I use an RSS feed through IFTTT to trigger email notifications to help out and @judell's facet tool can be useful: https://jonudell.info/h/facet/?max=10000&exactTagSearch=true&expanded=true&addQuoteContext=true&wildcard_uri=https%3A%2F%2Fspencergreenhalgh.com%2F*

https://spencergreenhalgh.com/hypothesis/

Someone else using Hypothes.is as a commenting system in the wild.

retweeting as a bookmarking behavior

https://notiz.blog/2022/04/27/custom-post-type-comment/

https://blog.flickr.net/en/2022/03/17/flickr-forever-2022/

Flickr is creating space for restricted and moderate content. Free users can only have 50 non-public photos.

@pratik Mastodon caps at 500 as a default. The information density of the particular language/character set is certainly part of the calculus.

Here's a few to start (and see their related references): - https://www.semanticscholar.org/paper/How-Constraints-Affect-Content%3A-The-Case-of-Switch-Gligoric-Anderson/de77e2b6abae20a728d472744557d722499efef5 - https://www.nature.com/articles/s41599-019-0280-3

https://github.com/tegon/traktflix

Code for making a Trakt.tv scrobbler for Netflix.

Another potential method (or an additional filter) for finding posts with photos, or more specifically posts whose main purpose is a photo or image is to use use the post type discovery algorithm. Given that Micro.blog is built on a variety of IndieWeb building blocks, most photos could/should have a class of u-photo on their img tags, so you could search for these instead or in addition to. I believe there are a set of parsers and tools out there that do this in a few languages already and someone in the IndieWeb Dev chat can direct you to them if they’re not linked to the page above.

https://privatter.net/u/ChrisAldrich

https://collect.readwriterespond.com/antennapod/

I feel your pain here Aaron.

Perhaps it helps, perhaps not, but I've been using AntennaPod for a few years now. In particular I love it on Android because I can use the share functionality to share to a custom email address which posts to reading.am for an account that aggregates everything I'm listening to. Then I port the RSS feed of that back into my site. It's a stupid amount of manual work, but it mostly works.

Alternately you could share material you listen to to Huffduffer and pull data out that way as well. My problem here is that Huffduffer is more of a bookmark service than a "listened to this" sort of service, though you could always add a "listened" tag to the things you've heard in the past.

The tougher part of all this is that podcasts have "canonical" links for the podcast episodes (sometimes) and an entirely different link for the audio file which has no meta data attached to it (presuming you can even find the URL for the audio file to begin with.)

AntennaPod allows you to pick and choose what you want to share, so usually I default to the audio file to get that in to the workflow and finding/adding the data for the particular episode is a bit easier.

I will say that this is one of the ugliest and most labor intensive workflows I've got for social posts, so I'm usually only doing it and posting publicly for things that I really think are worth the time that make for interesting notes/observations that go along with the post.

I'm curious to see what others come up with for this workflow.

https://blog.remark.as/introducing-private-letters

https://jamesg.blog/2021/09/13/new-social-pages

Some awesome looking progress here.

https://www.hivedigital.com/2019/12/09/guest-post-emails/

I like the design and set up for this feature. Perhaps something for the IndieWeb to pick up? In some sense the implementation of Webmention-based likes, bookmarks, and facepiled mentions on my site is just this sort of design.

The anecdotal evidence that there was little harassment is a positive sign for creating such a thing.

For @mentions on one's own website the feed https://hypothes.is/stream.rss?wildcard_uri=https://example.com/* should work for folks using Hypothes.is as a commenting system on their website.

To cover other cases when people don't use the @ symbol, one might also subscribe to https://hypothes.is/stream.rss?any=%22username%22

This is a clever and fun UI for implementing likes that seems on-brand for the website owner.

This is the first reference to Dispo I've come across.

Platforms specifically for communities could be an interesting new object on the Internet. What sorts of IndieWeb building blocks would one use to build them? Are there new functionalities that they might have that aren't in the list of building blocks yet?

I could see functionality like signing in with one's website using IndieAuth to access private content being a piece.

This seems like a cool potential way of doing all sorts of things in the IndieWeb space for WordPress. I'm curious what it looks like from other perspectives. I'll have to think this through a bit...

This is exactly the sort of thing that makes me happy about the IndieWeb!

One person tinkers around with an idea and posts about how they did it. Someone else sees it and thinks it's cool and wants it for themselves. They then modify it for their system, maybe with some changes or even improvements, and post the details on their site.

They've both syndicated copies to IndieWeb news or to the IndieWeb wiki, so that in the future, others looking for that sort of UI research or examples can find them and potentially modify them for their own personal use.

And the cycle begins anew...

My general heirarchy is that bookmarks are things I want to come back to (and usually read) later, reads are things that I've read, like are things I've read and want to send appreciation for, and replies are things that usually are both read, liked, and needed even a bit more.

Here's more on how I've thought about it before: https://boffosocko.com/2018/03/10/thoughts-on-linkblogs-bookmarks-reads-likes-favorites-follows-and-related-links/

In 2008, even before Twitter had become a thing at 180 characters, here's a great reason that people should be posting their commentary on their own blogs.

This example from 2008 is particularly rich as you'll find examples on this page of Derek Powazek and Jeff Jarvis posting comments with links to much richer content and commentary on their own websites.

We're a decade+ on and we still haven't managed to improve on this problem. In fact, we may have actually made it worse.

I'd love to see On the Media revisit this idea. (Of course their site doesn't have comments at all anymore either.)

Important!

Why can't there be more sites with solid commentary like this anymore? Do the existence of Twitter and Facebook mean whe can't have nice things anymore?

This may be the first time I've seen someone explicitly use Hypothes.is as the comment system on their personal website.

I wonder if Matthew actively monitors commentary on his site, and, if so, how he's accomplishing it?

The method I've used in the past as a quick and dirty method is Jon Udell's facet tool https://jonudell.info/h/facet/?wildcard_uri=https%3A%2F%2Fmatthewlincoln.net%2F*&max=100, though it only indicates just a few comments so far.

Use cases like this are another good reason why Hypothes.is ought to support the Webmention spec.

defined pretty well here: https://indieweb.org/quote_tweet

Here's the new link to the audio: https://www.wnycstudios.org/podcasts/otm/episodes/131068-july-25-2008

Here's the link to a version of the site in August 2008 with the commentary, which makes a fascinating rabbit hole to go down: https://web.archive.org/web/20080907233914/http://www.onthemedia.org/episodes/2008/07/25/segments/104537

Some great blue sky ideas here.

This gives me a hypothesis about why the chicken post came first within the IndieWeb.

The comments on this piece are interesting and illuminating, particularly all these years later.

This is sort of the fun, I think, in maintaining things like listen and read posts on my site. While they're a useful archive for me, in some part I hope they might speed some discovery for folks who find them or search them by category/tag as well.

I could post somewhere, "Hey I listen to this podcast," or retweet a headline, but invariably in the morass of content out there, there isn't actually an indication that I invested my finite amount of time actually listening to or reading that thing. Perhaps I was just doing some social signaling to make myself seem more interesting or worldly? To me this is a lot of the value of these types of posts.