Indie Microblogging
book.micro.blog
book.micro.blog
Longform posting allows you to establish your credibility and put your point forward.
Maybe this is why Twitter is such a miserable experience. Way too many opinions from the vulgar mass
I'd rather stare at the sky than use TikTok, by the way.
Long form posting is dead as a door nail.
An enormous number of people have established themselves as known experts on a given topic via "microblogging" channels, which for nearly everyone means Twitter and Facebook. Hopefully, open/federated microblogging will break out of its niche.
Just one example of this is the many thousands of virologists, epidemiologists, public health scholars, and statisticians who built huge followings (effectively from zero) during the COVID-19 pandemic.
> Longform posting allows you to establish your credibility and put your point forward.
Microblogging is a great channel for this too. These are not either/or choices, and any good strategy for establishing yourself as an expert — or whatever your goal is — will include both of these communications channels and more.
My approach is to self host and keep all my blogposts backed up in markdown format. Any images I have are backed up too. Also if you are running a blog, make sure you have the funds needed to keep it up for as long as possible. You may even need a paid CDN if you are serving a lot of images. Cloudflare helps with their free CDN but it’s nice to get away from centralised monopolies such as Cloudflare. Their recent outage has me looking for alternatives.
But if you have your own domain pointing to other people's land, then it's easy to switch.
To be perfectly clear: the only reason anyone should use RSS in new development is podcasts.
I'm personally a little unconvinced by jsonfeed too which is mentioned in later chapters, but I have to say I'd go all in on it iff it allowed us to free ourselves of RSS.
I disagree with the reasoning, because Atom is every bit as widely supported outside podcasting, and RSS is more painful to generate, requiring special-purpose date formatting rather than using the standard format that your library already supports, and requiring foolish duplication (things like description versus content:encoded) to obtain almost reliable results due to some of its underspecified or unspecified areas causing genuine pain for authors and clients alike, and simply not representing the right semantics. Atom is much more dependable and harder to mess up, and the sensible choice to implement as a feed producer, except (as mentioned) in podcasting where Apple froze it out.
For just about any other purpose, I’d say you want RSS or Atom anyway, and supporting multiple formats is actively undesirable because it complicates feed selection, so don’t even touch JSON Feed.
I think they're just using a channel, as described. You got to squint a bit until you recognize it as a blogging platform, but all the functionality is technically there.
I followed a friend's semester abroad in Japan through one and it was pretty good. A bunch of OnlyFans creators have set up a Telegram channel to notify about new content etc.
[1] https://bwaycer.github.io/hugo_tutorial.hugo/tutorials/mathj...
I don't know how Manton made that site, specifically, but focusing too much on the terminology here may lead you astray a little in this context. :)