Replied to a post by Ryan RandallRyan Randall (hcommons.social)
Slowly customizing my site layout enough to get it to validate h-entry info according to this nifty tool: https://indiewebify.me Wow, do I teach myself best by exploring other examples. #blogging #indieWeb
@ryanrandall @natalie I’m seeing more HCommons folx looking at , so I’ll mention that I’ve got several IndieWeb friendly sites including on as does @KFitz, who I think has also been experimenting with static sites lately. If you need support, there’s a great and helpful community you’ll find at https://chat.indieweb.org for all your questions. You might find some useful tidbits and examples at https://indieweb.org/Indieweb_for_Education as well.
Read IndieWeb, Revisited by Evan StonerEvan Stoner (evanstoner.com)
A couple of years ago I started building an IndieWeb website. Then I got painfully busy at work, stopped improving it, and basically ran out of free time to even post to it. Fast forward a couple of years, and I've got a new job that's somewhat more manageable, and during the holiday break I'm tryin...

It’s interesting to see the growing pains people are having on the internet as they add new functionality to their websites. Even WordPress has at least half a dozen plugins to enable a lot of the functionality that is de facto within social media. Slowly though, both technologists and small to medium sized companies will begin offering these features as standard pieces that won’t require this sort of overhead or configuration. Well eventually see a sea-change in the environment as the technological hurdles come down. It would be nice to see things like Netlify and WordPress offer IndieWeb-in-a-box for their customers.

Replied to a tweet by @fourierfiend (Twitter)
Hello fellow mathematician!

There are lots of ways to syndicate content, some dependent on which platform(s) you’re using and where you’re syndicating to/from. Your best bet is to swing by the IndieWeb Dev chat and ask that very question.

Theorem: Syndication is easy.

Proof: “It’s easy to show” (I’m waving my hands here) that there are a lot of assumptions and baggage that go with the word “easiest.”   ∎

I’ve personally found there’s generally an inverse relationship between ease/simplicity of syndication and control over exact display for most platforms. You could go low-fi and pipe your feed into something like IFTTT/Zapier  for cross-posting all the way up to customized integration with available APIs for each platform. Many take a middle-of-the-road approach that I notice Jeremy recommended as I’m writing this.

The cross-posting wiki page will give you some useful terminology and definitions which may help you decide on how to syndicate what/where. Based on the context of the URL in your Twitter profile, the IndieWeb wiki pages for static site generator and syndication will give you some ideas and options to think about and explore. 

Some of the pages about specific static site generators will give you some code and ideas for how to implement syndication. For example Max Böck has an article Indieweb pt1: Syndicating Content to Twitter, which is Eleventy and Twitter specific, but which could likely be modified for your purposes. SSGs may have some specific peculiarities for syndication that I’m not as familiar with coming from the more dynamic side of the fence.

Since you indicate a language preference for your current site, there’s also a page for Flask with a few users noted there. You might ask Fluffy (usually around in chat) for some advice as I know she syndicates to a few platforms and may have some ideas or even tools/code to share from the Flask perspective.

Q.E.D., right!?

(p.s.: Great Twitter handle!)