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
@nicolas_gatien @ArtemKRSV @lanewatson @ChrisAldrich @ScottScheper @NickMilo @AllossoDan @iameddyhood @ArchLeucoryx
Nicolas, I broadly agree with you that many of these factors of reading and writing for understanding and retention are at play and the research in memory and spaced repetition underlines a lot of this. However in practice, one needs to be revisiting and actively using their notes for some particular project to remember them better. The card search may help to create both visual and physical paths that assist in memory too.
Reliance solely on a physical zettelkasten however may not be enough without active use over time, particularly for the majority of users. It's unlikely that all or even many may undertake this long term practice. Saying that this is either the "best", "optimum", or "only" way would be disingenuous to the diversity of learners and thinkers.
Those who want to add additional strength to these effects might also use mnemonic methods from indigenous cultures that rely on primary orality. These could include color, images, doodles (drolleries anyone?), sketchnotes, or other associative methods, many of which could be easily built into an (antinet) zettelkasten or other note taking platforms. Lynne Kelly's work in this area can be highly illuminating. For pure practical application and diversity of potential methods, I recommend her book "Memory Craft" (https:/
With this background on orality and memory in mind we might all broadly view wood and stone circles (Stonehenge), menhir, standing stones, songlines, and other mnemonic devices in the archaeological and sociological records as zettelkasten which one keeps entirely in their memory rather than writing them down. We might also consider, based on this and the historical record concerning Druids and their association with trees that the trees served a zettelkasten-like function for those ancient societies. This continues to extend to lots of other cultural and societal practices throughout history. Knowledge from Duane Hamacher et al's book *[The First Astronomers](https:/
Thanks again @leppert for all those years of running and supporting @reading! 👋🏼😘🙏🏼🥰
https:/
@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.
@reading @leppert First, let me say a resounding THANK YOU for all your work and dedication to @Reading! Congratulations on a long run of a fantastic and flexible little service. I know I and many others will miss it desperately.
https:/
Are you joining us for @AllossoDan's next book club iteration? We're going to be reading Thomas Piketty's newest book A Brief History of Equality. Details for joining can be found here:
https:/
@brunowinck Generally I read a work and make my own annotations/observations first before reading/interacting with others for this very reason. I was just struck that I'd run across an article with so many annotators that I happened to know, an event which doesn't happen to me often.
This particular piece makes some astute and useful observations, but does throw the baby out with the bathwater without a keener eye on the history and point of much of the endeavor. Lack of history and experience kills him here, but it's the same thing that is causing a lot of the problem he's seeing in the space as well. I've sprinkled my thoughts into those margins now. Perhaps I'll write a more coherent rejoinder to it shortly?
This looks like some early history of #SocialAnnotation?! I'm in!
Apr. 18: Andrew Stauffer (UVA) & Amanda Licastro (Penn Libraries): "Book Traces: Library History and the Marks of Collaborative Reading"
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!
Wait... What?! There's a reading plugin for @WithKnown? It appears to be based on Jonathan LaCour's Food plugin, but portends some interesting new "read" post functionality within the IndieWeb community.
https:/
@mrkrndvs This link may also be somewhat relevant to some of your recent questions if you haven't come across it: http:/
Read posts are somewhat like bookmarks, just for things that I've read. I suspect you could use this for Radio3/Diigo as well.
I recall reading somewhere that Fanny Farmer and her eponymous and illustrious (read:nefarious if you're a baker) cookbook heavily influenced American (home) bakers to move from measuring flour by weight to measuring by volume instead. It's done such a disservice to the bread world here in the states. I suspect this is where the need to sift has stemmed as the amount of sifted flour in one cup can be drastically different from a packed cup.
I definitely ignore any cookbooks (with bread and pastry) that measure flour by volume over weight. It's just sacrilege.
@BookExamination It's nicer if you actually linked directly to original and didn't misrepresent the intention: http:/
@khurtwilliams POSSE for WordPress can be tricky in part because, compared to most other IndieWeb pieces for WordPress, there are multiple different and varying ways to do it. Using one method could potentially conflict with another depending on how you set things up, though I think these are relatively few.
Your best bet is to hop into the #WordPress channel of the IndieWeb chat https:/
In general, the more control and flexibility you want over the display of your POSSE posts, the more set up and work you have to put into it (e.g. SNAP), while the less control you have the more simple the set up (e.g. JetPack Publicize).
Things like Brid.gy publish functionality (or via the Brid.gy Publish plugin) can be more finicky for POSSE copies to silos because Brid.gy is parsing your site for the proper data to publish. (It does have a preview button built in to do manual tests if you need to.) This means that if your WordPress theme doesn't have the correct microformats markup (and often they don't), then you can get spurious results, particularly when it comes to crossposting photos.
Most of the main POSSE plugins and tech are very stable in fact, but they do require that you do a bit of reading and understanding what they do and don't do and what you can and can't control with them. Most all of them have GitHub repositories that you can post issues to and almost all the devs, maintainers, and community are happy to help you out and/or make changes to make the UI and documentation better.
As for backfeed from Brid.gy, it generally requires that the URLs of your post and the syndicated post have matching permalinks to be able to match the two up to send you the webmentions properly. You may have changed your settings, but one piece you appear to be missing is the Syndication Links Plugin which allows you to add u-syndication links to your posts so that Brid.gy knows which ones to send your responses to. Much of this is documented at https:/
I'm sure I've got a few odd posts from ages ago when I tested things out, but when you say "I can also see from some of the failed posts on your website that you may experience the same issues." I'm curious which particular posts you mean? To my knowledge things I intend to syndicate out are currently working as I expect them to (aside from one quirk that occasionally spams the Indieweb chat with micropubbed posts which continually redirect, but that's specific only to me because of some experimental code I've been running). It is the case that I don't always syndicate everything to each and every silo target I could. I do very much pick and choose which things to syndicate to particular networks.
We'll help you get there yet!
I'm guessing that 190 degrees is the target vessel temperature then? The way I was reading it was that you were shooting for an internal meat temperature of 190 since you were already over 170 on the meat. Pork is usually well-done at 170 and a further increase in temperature (and or time) tends to shorten the muscle fibers which begins to dry out the meat and make it tougher, rather than more tender.
Knowing that it was a high collagen cut helps, since you're relying on the succulence of the gelatinized collagen (160-180 degrees) to cover up for the effect of dried out meat which begins happening above 140. A good way to protect against the drying out factor above 140 is to brine the meat prior to cooking.
I'll have to go back to Harold McGee to see what temperature he recommends for slow roasting pig, but I can't imagine that he would go over 180 on internal meat temperature.
Hope it was good!
For me there are various post types that essentially all boil down to being bookmarks, but the sub-category adds a slightly different shade of intent to it. As an example I've got a "read" post type on my primary site. It takes the bookmark concept ("I want to read this") and adds the additional piece of semantic information that I physically spent some time to actually read it. To an audience, this gives that read-post some additional value over a simple bookmark. Even further, did I bother to make a comment or highlight a piece of material from it? Did I go another step and write a reply to it? Each of these things indicates a higher level of engagement on my part which signals to an audience reading my site, what value I may have placed on a thing.
When it comes to a reader, it would be awesome to have the ability to filter through some of these increasing types within a value chain. People are sharing or bookmarking lots of crap, but what are they spending the time to actually read rather than sharing after only reading a headline? What did they bother to really react to? What motivated them to not only read a piece, but write a 10 paragraph response to? When it comes to finding things in my feeds that are really valuable from friends, family, and colleagues, it's these articles that are usually the most valuable.
You're definitely right that readers are the next big piece. I can't wait for some more competition in the space: http:/