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
@chuckfrey Primarily for note taking (90%) to feed both a WordPress site and an Obsidian database presently, but also for some social annotation (10%) with respect to things I see via https:/
My Obsidian store serves variously as a zettelkasten, commonplace book, and wiki simultaneously though each of these are discretely fragmented. Of course I could do most of the work via Hypothesis really without any other tools at all, presuming that the data would always be there.
Large swaths of Hypothes.is use is hiding within LMSs or is geared more toward social annotation in classrooms. I'm more interested in people using that content for their future selves or their creative endeavors.
You can find my publicly available material here: https:/
@TerribleMia You've got your own site and control your URLs, so you're definitely on it! And you've got Webmentions for additional icing on the cake. Kudos! I'm glad you've managed to get things set up and working for yourself. It definitely helps to have small bite-sized pieces of technology to rely on to get it all going.
You're right that it's a lot of work on individuals, but there are some emerging platforms/providers attempting to make all of this technology easier on the general public who don't have the time, technical skills, or desire to maintain any of their own systems. Micro.blog is one of these options to be sure. A few others can be found here: https:/
Congratulations again!
@GingkoApp looks interesting, but is there a way to easily export cards/notes out of tools like @TiddlyWiki or @Obsdmd into it for arrangement and then writing?
Within the past month [it's guestimated that over 1 million webmentions](https:/
Mastodon already supports most microformats for webmention to be implemented more easily. https:/
There are already a number of open source tools that might also be bootstrapped for something like this as well: https:/
@Chronotope @acarvin Yet another reminder in a seemingly long and unending list of reasons for why journalists (and everyone really) should have their own websites and tools.
https:/
@kristenhare A growing group of journalists are joining the IndieWeb movement to better own their work and data within their own personal archives as well as using tools like Ben's to archive their work on larger institutional repositories. There's a stub page on the group's wiki dedicated to ideas like this for journalists at https:/
Coincident with these particular sites disappearing, there's now also news today that Peter Thiel may purchase Gawker in a bid to make it disappear from the internet, which makes these tools all the more relevant to the thousands who wrote for that outlet over the past decade.
For journalists and technologists who are deeply committed to these ideas, I'd recommend visiting the Reynolds Journalism Institute. They just finished a two day conference entitled "Dodging the Memory Hole" at the Internet Archive last week focused on saving/archiving digital news in various forms. (https:/
What makes it even more sad and painful is that it's one of the first as well as the longest lived services I ever had an account on or used to communicate with others on the web. It's just too bad they quit iterating on and improving it, though worse, its general feature set was still pretty rich given today's tools.
Jack, Your response (above on your site) is a good example of watching what is going on and knowing what your site can and can't do.
Because you put your response directly into the comment box on your site (ostensibly in a general sense to the main post rather than to my response), your site didn't send me a webmention for it and so I didn't know you had responded except that I happened to come back to your post. If you visit it, you'll see that your reply doesn't show up on http:/
The better method using Known would have been for you to have clicked the permalink on your site for my comment (the date of my comment or the name of my site) that would have gone to my original, you could then have used the bookmarklet for Known (found at https:/
Because I'm replying to both your post and mine, it should show up via webmention on both. The manual comment box on Known is really only for people whose sites don't support Webmention. Some people actually disable the comment box functionality and only receive Webmentions as a means of preventing spam comments.
In an ideal world, your comment box would send both Webmentions and salmentions to maintain the integrity of the comment thread. Since it doesn't (yet) then you need to do that manually, especially if you want me to see your reply.
Hopefully all this makes some sense...
Here's a photo post of some of the UI that may make it make a bit more sense: http:/
@twittkopp You might find @unpaywall or @mendeley_com to be useful tools depending on your needs. Esp as browser plugins/bookmarklets
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:/
http:/
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:/
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.
@andreweckford I'll wait to see what the "webmaster" posts later. :) Thanks for the live tweeting you're doing, particularly the linked stream. I know you're most of the way through, but next time you might give http:/
It will also save your entire tweet stream from the conference in a simple format so you can cut and paste your work into a blog post quickly after-the-fact for archiving into the conference website (or your own).
It's one of the best conference tools I've come across for this type of thing.
Instruction manual if you need it: https:/
#conferences #twitter #ITBio #noterlive
Manton, after having heard/seen your microcasts (and those of others) as well as your mention of podcasting tools above, I thought I'd point out that there's a micropub tool called Screech for podcasts: https:/
Some of the issue is that WordPress has a huge number of plugins which adds a lot of additional complexity (especially for Micropub clients) which isn't always going to be handled by every client.
As for webmentions, they're being bolted onto WordPress which doesn't have (or allow) a custom comment type, so they're jury-rigged in the best manner possible. There is still ongoing work, especially with the Semantic Linkbacks Plugin which does a lot of the heavy lifting here, if you've got thoughts/ideas, you should certainly weigh in on those Github issues as they are evolving.
I know there were a handful of quirks that have been changed in Known in the past months to fix some issues with microformats that were being parsed incorrectly, and thus caused other platforms like WordPress not to let them display as nicely when received. I think most have been merged and a new release of Known was pushed yesterday and should hopefully clear up some of these issues. I think the developers of the WordPress plugins and even the Known community are very responsive, so feel free to jump in with feedback, suggestions, or even pull requests on any of the pieces which are all on GitHub.
I'm sure there will be some remaining rough edges, but in general a lot of them have been smoothed over in the past year and most improvements now seem to be geared towards making the suite of tools more user friendly or to better extend the functionality.
@Mercy They seem like completely different products to me.
Known is a CMS which allows you to own your data, then publish and syndicate it to multiple platforms (including uploading to Anchor). It doesn't have any audio creation or editing functionality. I have seen people using this and WordPress lately for small personal microcast "channels" which can be subscribed to or syndicated out to other social platforms.
Anchor appears to have some production and publishing tools as well as a distribution platform of sorts. It looks like the material you publish to your own station can be listened to for 24 hours, but then disappears unless you archive it to your account privately. Fortunately you can export your audio with a little bit of gymnastics, but it's not intuitive. This seems more like an ephemeral audio version of snapchat to me.
I'm curious what you're looking for in a minipodcast? I'm considering something shortly myself and have been looking at Anchor as well as Opinion2, Spreaker Studio, audioBoom, tryca.st, and even others as simple as using my LiveScribe Echo pen to record and then distribute via my Known or WordPress sites.
It looks like you may be using the Post Kinds plugin, so you should be able to reply to other sites using that and putting the requisite URL into the interface under "Post Properties" and including your response. The plugin will include the necessary u-in-reply-to microformat class and your webmention plugin will handle sending the response. If you'd like, you can try responding directly to this post at its permalink.
An alternate method is to use the Indieweb Press This bookmarklet for replies (if you're using the Indieweb Plugin) . You can find the bookmarklets at your /wp-admin/tools.php page about halfway down. Then you can click the bookmarklet on the page you'd like to reply to and it will craft a part of the post to send the reply and then you just add what you wanted to say before publishing to send the webmention.