0x1C3B00DA / Zachary

There are four people in 0x1C3B00DA’s collective.

Huffduffed (151)

  1. Decentralized Bookshelves - Personal Libraries - IndieWeb Popup 2022

    There are several new Goodreads-like services, but each service maintains their own API and bookshelf data: "Want to read", "Finished reading", etc. Micro.blog also has an API for creating and managing books and bookshelves, based on JSON Feed. Some people maintain these lists on their own blog manually. Can we standardize how apps get and set bookshelf data? Could this be a convention around feeds, or maybe an extension of Micropub channels?

    https://indieweb.org/2022/Pop-ups/Personal_Libraries#Bookshelves

    https://archive.org/details/decentralized-bookshelves-personal-libraries-indieweb-popup-2022

    —Huffduffed by 0x1C3B00DA

  2. Book Identifiers - Personal Libraries - IndieWeb Popup 2022

    If we were able to cross-reference book reviews and book pages, how would those books be identified? The state of the art of book identifiers (OLID, Goodreads ID, ISBN, WorldCat, LCCN, etc) is complicated. How are we supposed to interact with it? How do we cross-walk these IDs?

    https://indieweb.org/2022/Pop-ups/Personal_Libraries#Book_identifiers

    https://archive.org/details/book-identifiers-personal-libraries-indieweb-popup-2022

    —Huffduffed by 0x1C3B00DA

  3. Ad-Hoc Book Discussion Clubs - Personal Libraries - IndieWeb Popup 2022

    How can we use personal libraries published to the web to facilitate ad-hoc book clubs or one-off discussions with people who are already actively reading (or have just read) the same books as us? What are the key pieces of infrastructure that would help facilitate these groups? Save us from the eternal problem of starting book clubs with people, then struggling to agree on books. Flips the equation to start with the book, then find the people.

    https://indieweb.org/2022/Pop-ups/Personal_Libraries#Ad-hoc_Book_Discussion_Clubs.2FSessions

    https://archive.org/details/adhoc-book-discussion-clubs-personal-libraries-indieweb-2022

    —Huffduffed by 0x1C3B00DA

  4. Opting into the Composition API with Oscar Spencer

    https://enjoythevue.io/episodes/80

    With the release of Vue 3, developers now have access to the Composition API, a new way to write Vue components. This API allows features to be grouped together logically, rather than having to organize single-file components by function. Using the Composition API can lead to more readable code, and gives developers more flexibility and scalability when developing their applications, which signals a bright future for Vue. At least, this is what today’s guest believes! Today, we speak with Oscar Spencer, developer at Tidelift and co-author of the Grain programming language, about Vue’s Composition API and why he believes it represents great things for Vue. We touch on Options API, our opinions of a template-first approach, and why Composition API is infinitely better than Mixins, as well as how JavaScript can prepare developers for Options API and what to watch out for when you first start working with Composition API in Vue. All this plus this week’s picks and so much more when you tune in today!

    Key Points From This Episode: * An introduction to today’s guest, Oscar Spencer. * The panel shares what sound their Slack makes when they receive a new message. * Oscar shares his personal passion for the Vue Composition API. * Why he believes that Vue’s bright future includes the options API too. * Why Composition API represents great things for the future of Vue. * The panel discusses commit messages, interactive rebasing, and squashing. * What Oscar means when he says that the Composition API makes Vue more scalable. * Oscar and the panel weigh in on taking a template-first approach * Discover Oscar’s situational approach to composables when reusing business logic. * Composition API versus Mixins and why Oscar believes Composition API is superior. * Whether Options API or Composition API is easier to teach to a beginner developer. * How JavaScript prepares developers for Options API, which Oscar describes as ‘cozy’. * Oscar on how to know when to use Composition API versus Options API. * Why you would choose Composition API over simply using JavaScript: reactivity. * The panel shares some of the longest Vue components they have worked on. * Render functions in Vue and Oscar’s perspective on React versus Vue. * What to look out for if you’re new to Composition API; not understanding Vue’s reactivity. * Why the coolest thing Oscar has done in Vue is write a backend using the reactivity API. * This week’s picks: Only Murders in the Building, The Artful Escape, Dyson Sphere Program, The Great Ace Attorney Chronicles, and more!

    —Huffduffed by 0x1C3B00DA

  5. Enjoy the Petite Vue with Dave Rupert

    https://enjoythevue.io/episodes/77/

    Have you ever wished that Vue was smaller? We know we have. Petite-Vue is an astonishing 5.5KB, which is so small, it’s almost invisible. Dave Rupert, a developer at Paravel, joins us today to discuss all things Petite-Vue. We hear how this smaller version was released, and Dave shares what his experience of using it has been like. Often, when a framework is more compact, there are tradeoffs or sacrifices users have to make, but this does not seem to be the case with Petite-Vue. We talk about Alpine, how Petite-Vue is different, and we also get stuck into the use cases for Petite-Vue. Dave shares one of his totally wild ideas, which, naturally, Alex is all over. Our wide-ranging conversation also touches on interviews and what needs to change with them, templates and styles, and as usual, we wrap up with everyone’s picks for the week. Tune in to hear it all!

    Key Points From This Episode: * Get to know today’s guest, Dave Rupert. * Everyone’s take on how they would feel if Vue was five kilobytes. * The story of how Petite-Vue came to be released. * Dave’s experience of using Alpine and some of the challenges he had with this. * What the jump from Vue to Petite-Vue is like. * Hear about the idea that Dave runs past Alex. * Some other great use cases for Petite-Vue. * Unpacking the broken coding interview system; things need to change. * Questioning some obscure hiring requirements. * The framework Dave uses given that he works in an agency. * In business, frameworks can become politicized and sites for contention. * Things other people do that make everyone believe they are monsters. * Diving into the world of template style and script. * Where you can find Dave online to tell him how wrong he is about all his choices. * Everyone’s picks for this week; there are some great ones!

    —Huffduffed by 0x1C3B00DA

  6. Exploring Deno Land 🦕

    https://changelog.com/podcast/443

    This week we’re joined by Ryan Dahl, Node.js creator, and now the creator of Deno - a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.

    We talk with Ryan about the massive success of Node and how it impacted his life, and how he eventually created Deno and what he’s doing differently this time around. We also talk about The Deno Company and what’s in store for Deno Deploy.

    —Huffduffed by 0x1C3B00DA

  7. The Power of Black Cooperative Economics with Dr. Jessica Gordon-Nembhard

    https://pushblack.simplecast.com/episodes/the-power-of-black-cooperative-economics-with-dr-jessica-gordon-nembhard

    Credit unions, housing co-ops, CSAs… Black folks have been building and benefitting from cooperative economics for decades, particularly in parts of the economy where we’ve been cut out by the major institutions. As Dr. Jessica Gordon-Nembhard points out, we all participate in some form of cooperative economics when we use the informal economy. In this episode, we dig into the power that we could amass if we took cooperative economics to scale. BHY is produced by PushBlack, the nation’s largest non-profit Black media company - hit us up at BlackHistoryYear.com and share this with your people!

    —Huffduffed by 0x1C3B00DA

  8. hpr3102 :: RFC 5005 Part 2 – Webcomics, subscribers and feed readers

    An interview with two passionate RFC 5005 fans on how to handle big Atom feeds

    This conversation took almost an hour, so I split it into two shows:

    Part 1 talks mostly about the RFC itself, what it means and why. HPR 3082
    Part 2 goes into personal experiences with the RFC and with syndication in general, in particular in the context of web comics.
    

    This is part 2.

    In this show I’m talking to: fluffy

    Federated social web:
    <https://queer.party/@fluffy>
    Writes and makes things in several creative fields:
    <https://beesbuzz.biz/>
    Publ is like a static site generator, but dynamic. It produces RFC 5005 archive feeds, of course:
    <http://publ.beesbuzz.biz/>
    Thoughts on ephemeral content vs content worth archiving and how they relate to protocols:
    <https://beesbuzz.biz/blog/5709-Keeping-it-personal>
    

    Jamey

    Federated social web:
    <https://toot.cat/@jamey>
    Blog:
    <http://minilop.net/>
    Made a prototype full-history reader that follows RFC 5005 links:
    <http://reader.minilop.net/>
    Made a webcomic reader mostly mentioned in Part 2:
    <https://www.comic-rocket.com/>
    Made a WordPress plugin implementing RFC 5005:
    <https://github.com/jameysharp/wp-fullhistory>
    Made an RFC 5005 archive feed synthesizer for sites with a predictable post frequency and URL structure:
    <https://github.com/jameysharp/predictable/>
    Hosted at <https://fh.minilop.net/>
    Was on HPR 9 years ago, talking about X.Org!
    <http://hackerpublicradio.org/eps.php?id=0825>
    

    Conversation notes

    Back in 2002, Aaron Swartz published his joke MIME-header-based RSS 3:
    <http://www.aaronsw.com/weblog/000574>
    The cultural context at the time and the rivalry between RSS 0.91+, RSS 1.0, RSS 2.0 and Atom deserves a show of its own.
    

    —Huffduffed by 0x1C3B00DA

Page 1 of 16Older