Microblog

Reading People, Power, and Profits: Progressive Capitalism for an Age of Discontent by Joseph E. Stiglitz.

In reply to https://boffosocko.com/2020/12/24/55784090/.

Apparently, a similar “share button” for Mastodon did exist before it got removed again (https://github.com/tootsuite/mastodon/pull/8127). It’s Mastodon’s decentralized nature that makes things so complicated: there simply isn’t a single URL to point to. That said, there seems to be this alternative JS library (https://aly-ve.github.io/Mastodon-share-button/) that may just work.

Turns out https://uglyduck.ca’s Atom feed had disappeared. Looks like the site got moved to WordPress. Good thing my feed reader now tells me! (Hint: this is why HTTP redirects exist.)

Bookmarked https://blog.futtta.be/2020/12/23/ao-not-lazyloading-the-sequel/.

[Tell] Autoptimize not to lazyload the logo and featured image.

Bookmarked https://calendartricks.com/a-calendar-in-three-lines-of-css/.

“A Calendar in Three Lines of CSS”

Bookmarked https://boffosocko.com/2020/12/20/non-technical-indieweb-fun-creativity-community-and-content/.

It’s your site, do what you want with it. Don’t make it a single topic.

In reply to https://jan.boddez.net/notes/dab3b7cdb4.

Added basic Microsub support (channels, timeline, mark as read/unread) instead. Might look into other APIs (Fever?) later. Although I really like Miniflux’s approach—a proper responsive web client = no need for apps—too.

Note to self: use press_this_suggested_html to add in “bookmark” Microformats. That way, there’s Indigenous on mobile and Press This on the desktop (and I no longer need Micropub baked into my reader, except maybe for “likes”).

Did I already mention I brought back figure and figcaption support to my “soon-to-be-social” reader? Makes posts look so much better!

Bookmarked https://wptavern.com/jump-start-block-based-theme-development-with-the-fse-theme-generator.

[I]t feels refreshing to see the untangling of theme development. Traditional theming today has created behemoth codebases in an attempt to keep up with features that users want.

Exported the 100-something feeds I had in my “Aperture” instance—thank God for OPML—and imported them into the new reader just fine. Pros: consume and manage feeds all in one place; runs on a dead-simple shared hosting account. Cons: no Micropub, yet.

Bookmarked https://colly.com/stream/kirby-3-5-and-release-party.

When you love your personal site, you’re always gardening.

In reply to https://jan.boddez.net/notes/8e51abb6b4.

And another such example, with (originally relative) “jump links” inside (or right after) the headings. As readers often strip id attributes, breaking the in-page links, it does make sense to link back to the original article instead. https://stefanzweifel.io/rss.xml

In reply to https://jan.boddez.net/notes/7797d076e3.

The otherwise awesome Lynn Fisher’s latest post – right at the top at https://lynnandtonic.com/atom.xml – is one such example. Regardless, with this change, my Aperture fork and upcoming RSS reader will finally behave much more like the various other readers out there.

PicoFeed turns relative links in RSS feeds absolute by prepending them with either the site or feed URL, but a whole lot of feeds—incorrectly, kind of—contain in-page (“jump”) links that are relative to feed items. While feeds that are meant to be read on “off-site” domains should probably not contain relative URLs at all, the latter seems much more common than the (more technically correct) former. Forked and “fixed.”