Daily Journal 📓 December 2023

Using Obsidian to edit my Jekyll-based site. I want to add journals back in, and maybe move to Eleventy, and maybe add IndieKit.

What are the latest Micropub Client apps?

• If your domains / email are with NetNation, that is actually Hostway, and these #email settings are what you need to set up your IMAP and SMTP https://support.hostway.com/hc/en-us/articles/115000368264-How-do-I-configure-my-email-client-General-Instructions-#imap-settings
  • Webmail is available at https://webmail.netnation.com/appsuite
  • If your MX records are mx.siteprotect.com for a domain (use dnsrecords.io to check), this should work
• For Mattermost on #Cloudron, you can go into /app/data/config.json and change settings #Commons Computer
  • In this case, I have my first user that never confirmed email and so can’t login, so turned off email confirmation
• Also learned that for #Cloudron, outbound email settings are per domain
  • So setup #Mailgun for #DWebYVR MediaWiki
  • I had made changes to this for Ghost #Cloudron setup, and that had likely messed up email for other things there

• Examining crypto’s product-market fit by polynya #crypto

  • A primer, first. Public blockchains are centralised, unfair, and inefficient. For almost everything, they are useless, if not outrightly dangerous. Humans and our societies are extremely complex and nuanced, and expressing subjectivity is simply not possible with blockchains. However, for a couple of things, they are invaluable, and the only way to achieve them. Broadly, these are usecases that require strict global consensus, something objective money and objective identity require. With that said, let’s get right into the usecases

• The platformisation of software development: Connective coding and platform vernaculars on GitHub #Github #opensource
  • I’m still tracking down Open Source 2.0 as a concept. This mention of “post-F/OSS” is perhaps one example

  • They propose the concept of post-F/OSS to describe a platform culture that co-exists alongside F/OSS and proprietary coding. This comprises widespread practices of publicly posting mundane code projects without a licence and with little to no documentation to help users understand these projects. According to Fuller et al., this ‘general indifference to the discussions of and loyalty to certain kinds of licences and the sense of ethics (GPL) or business models (Open Source) that these drew upon’ (2017: 58), marks a departure from the F/OSS movement’s practices.

• How could open licensing protect democracy? #licensing #EUPL
  • The EUPL is new to me, a good read

• Ben Yoskovitz writes about Venture Studios #future of venture on LinkedIn
  • Venture studios are emerging as a legitimate asset class. It’s an interesting way of thinking about it, because it warrants further clarity and definitions, without being overly prescriptive.
  • Created Venture Studio Checklist, a GSheet working through different models
    • 1. Internal Company Structure and Methodology: This covers how you’ll structure your studio, how you’ll work (including the framework/playbook/process you’ll use for validating startups) and the makeup of your team.
    • 2. The Founders: Next, you deep dive into the founders you’ll recruit: who they are, how you find them, compensation, etc.
    • 3. Startup Structures: This section focuses on how you’ll structure new startups emerging from your venture studio. This is a complicated section because it focuses on investment and equity, two hot button topics.
    • 4. Venture Studio Business Model: The final section covers the studio’s finances and business model, with different options for raising capital into the studio entity or a fund (or both). This is also complicated because studios don’t survive on management fees alone (or at all). The Venture Studio Checklist is free to use — just make a copy (it’s a Google Sheet) and start filling it in. I hope it helps people understand all the components of designing, building & launching a studio.