Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation
@hypothes_is @CarlosGoller @mbiotech Carlos, thanks for sharing your experience this morning. Based on some of your comments in #LiquidMargins (live and in chat), if you've not come across it, you and *especially your students* may appreciate Sönke Ahrens' book "How to Take Smart Notes: One Simple Technique to Boost Writing, Learning and Thinking - for Students, Academics and Nonfiction Book Writers". The techniques there can readily be implemented with Hypothesis in much the way you mentioned your students are already naturally doing for their own research. The book may help encourage them to extend their practice (in addition to a built in, but broadly unsung happiness/fun/quality of life component, which is always welcome in my book). There's also some research cited in it about how the ideas relate to learning research as well for those in the pedagogy related spaces.
https:/
I'm curious to hear what you, students, and others think about these ideas, particularly after using them for a while.
@benwerd @benwerd@mastodon.social It would be cool if they could easily expose numbers of interactions (reads, replies, bookmarks, etc.) as a signal in a way such that social readers could filter using this data along with tags/categories for prioritizing what we might want to read.
Selfishly they could use these signals internally for better measuring engagement with articles and particular writers. Is it high quality engagement (useful comments, reads) versus lower quality engagement (bookmarks which might indicate "I read the headline and might be interested").
Highly enterprising publications, and especially "local" publications/newspapers, might consider offering IndieWeb as a Service to allow their readers the ability to have their "own platform" within the publisher's platform/stack. This could be done on a co-op basis or potentially even bundled into subscription prices. Something along the lines of Kinja perhaps, but with more ownership/control/ability to move. Or perhaps a white-labeled version of something like micro.blog, but run/managed by the NYT, WSJ, other?
A well tummeled version of the Hometown fork of Mastodon with "local only posting" could be an engaging thing for a sophisticated newspaper or magazine to create. The publication could have closer control/moderation of the local posting for article related conversations, but people could still communicate with others outside of that "home" server. Alternately, in the standard Mastodon model, the "public timeline" could be filtered for posts about or commenting on the outlet's own content and all other content goes into the federated timeline.
Publications offering their own microsub social reader interfaces could be fun and clever. It could be an interesting way to have a more streamlined reading experience for paid subscribers among other potential options. This could be an interesting interface for helping people build a truly custom reading experience specifically for them, particularly for larger newspapers with large amounts of content that could be better filtered and personalized to individuals.
@Cambridgeport90 I don't worry about them stepping on each other, I simply make sure they're cross-linked so that if I go looking for something, I'll be able to find it. Webmention definitely helps in this respect.
As an example you'll notice that my earlier response (http:/
@finiteeyes Congratulations on what appears to be a new site. As you think about public/private and provide an example to others, I'm curious if your comments are avatar-less on purpose or if you've just not come across Gravatar yet?
https:/
@jgmac1106 If you're as poor a theme tinkerer as I am but about to embark on adding microformats to a theme, I might recommend taking a look at the individual commit changes that David Shanske goes through in converting the base Twenty Sixteen Theme into a more IndieWeb friendly theme. The list of commits with useful labels can be found here: https:/
I would recommend starting at the bottom and then slowly reading your way to the top to try to understand what he's doing in each section. Note that there are one or two places where he splits a particular change up between a few commits or occasionally backtracks. There's also a section in which he "rips" out the WP core functionality of Post Formats in favor of using the Post Kinds Plugin--I'd recommend you don't do this to make your resultant theme the most flexible. I believe there's also a section in which he adds a "comment walker" and later removes it because the experimentaly functionality was later merged into the Webmentions/Semantic Linkbacks plugin to better handle comments, so you can safely ignore may of those chunks which are now stable.
I suspect that between this and the code models for SemPress and Independent Publisher (which should also have some David Shanske specific commits and related discussion that you can look up) you may be somewhat better off.
Good luck! We're all cheering for you!
@noahread @madebydusk @manton2 @m_ott @CraftCMS
It depends on what data you want back into Craft. Most just want the replies/comments. Micro.blog does this via webmentions, thus the reason for having the webmention plugin set up to collect those replies.
@dajbelshaw Noterlive is primarily a posting interface to Twitter (mostly for livetweeting though it could continue to add some of that functionality in the future) that gives you back your data. You would still want to pay some attention to your account for side conversations and replies as well as other conference activity. In many cases I use it primarily as a note taking tool to keep content for archival purposes after the fact.
For additional two-way interaction you could use WordPress plugins like Webmention and Brid.gy Publish to get the comments, likes, etc. back to your website. I've outlined a piece of that type of workflow here: http:/
Otherwise, you might also consider going full IndieWeb, in which case you could post everything directly from your website and syndicate to Twitter and then getting all the responses directly back to your site. Some of this depends on how much work you want to do to get the moving pieces working properly. You'll notice this is roughly what I'm doing on my own site with you now. Example: http:/
@sadlerjw You've certainly found a few of the remaining pain points within the broader community and specifically with WordPress. There are obviously some UI bits like properly threaded conversations across multiple syndicated silos that could be better. I've written a tad about how threaded comments work between sites using WordPress, though didn't touch on the idea of doing so also using Twitter or micro.blog: http:/
Ideally in the end, everything would support Webmention and needing to syndicate to outside services would be somewhat moot.
As long as the conversation for something on micro.blog starts on your own site, the replies that occur there will generally flow back to your site via Webmention, but sadly one needs to use some manual chicanery to get a similar back and forth effect with other services like Twitter.
I suspect that in the coming months/year(s) things on this end will improve as the community marches forward.
Either way, congratulations on what you've done with you're site! Hope to see you around either via reader or micro.blog.
@spigot They should be in one of your comments "folders" and once approved they appear in the comments section of the particular post.
@huby And now the bigger reveal! Since you've liked my tweet, you'll notice that I'm backfeeding reactions and comments from my tweets, so your "like" also lives on my website at the original post which was syndicated to Twitter. http:/
RSVP invited · Issue #156 · pfefferle/wordpress-semantic-linkbacks https:/
When Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to "invite" instead of "rsvp:invited".
Manually effecting the change in the database provides the expected display. See: http:/
@mrkrndvs I'm curious if you manually cut & paste your replies for others' sites (who may not support webmention or even pingback/trackback) into their old-school comments sections?
I often worry that without that, or without replying to versions on Twitter if they syndicated, they won't see my response via pingback/trackback or other means. Instead my reply sits all alone on my site and they don't have the benefit of seeing it at all unless they come across it organically otherwise.
Generally when I manually cut and paste replies, I'll often use the comment's "website" field to include the permalink for my comment and then I'll take the permalink for my comment and add it to my syndication links since I've manually syndicated it.
Sometimes I notice that including multiple links in a reply can also run afoul of spam filters.
One of my favorite set of machinations occurred recently when I wrote this reply to Jon Udell: http:/
Jon came back to his original post and appended his own comment to document my comment in the most circuitous of manners which included using his annotation tool Hypothes.is: https:/
Interestingly we both used WordPress, Hypothes.is, and Twitter to carry on the conversation. I was quite impressed that he took the time to circle back around and document my end of the conversation since he must have missed my pingback (he doesn't have webmentions) and my manual cut & paste, but did manage to see the notification on Twitter.
It all just goes to show that you've got to keep your eye on the tech that you and everyone else is using until it's broadly and evenly distributed. One day perhaps...
I suspect that next, with a tad bit of parsing using microformats, you can add some display elements to your webmentions to indicate the author, their url, date/time, and actually include the reply text to have a better UI for them. Then they'll look a bit more like the traditional comments you may have envisioned. (Something along the lines seen in my comments at http:/
@frank Webmentions are an extra generation or two beyond the traditional pingbacks/trackbacks. The receiver actually verifies that the sender is displaying the permalink on a physical page before accepting it, thereby cutting down on spam (there have been no reports of webmention spam in the wild yet.) Webmentions and their structure are also set up to allow the receiving site to better handle display which often includes the name, avatar, and either excerpts, or complete comment. I use them in WordPress and there's generally little if any difference in the display of Webmention replies and comments natively put into the system manually. Webmention also allows additonal types of mentions including likes, bookmarks, reads, listens, etc. to distinguish for context.