Not-so-pro tip: in your #IndieWeb RSS feeds, do not name titleless notes “No Title,” but leave out the `title` tag altogether.
TL;DR: Use (and extend) league/commonmark.
Oops. Well, f—k it.
Recently watched the Fear Street trilogy, Turbo Kid, and La Gomera (The Whistlers), and now I’m wondering if I should revisit, or clarify, my “rating system,” which goes up to four stars. One star would be “interesting,” two stars “entertaining,” three stars very good and four almost impossibly awesome. As for the films above, I’d probably give them ~~one or~~ two stars each, like so: ★★☆☆. ~~(Should probably drop that fourth star, too, and not be such an a—hole.)~~
Switching between the Parsedown Extra and Markdown Extra libraries for PHP. One doesn’t convert `> ` to `blockquote` inside `
` and the other doesn’t support `~~` for strikethrough text.
> There’s no technical reason you couldn’t stay in touch with Facebook friends without being [a] Facebook user. You can switch phone companies or email providers without walking away from the family, community and customers you’re connected to.
> [B]eing banned for something as dumb as this would make a good story.
"Why are hyperlinks blue?" by Elise Blanchard https://blog.mozilla.org/en/internet-culture/deep-dives/why-are-hyperlinks-blue/
Incredibly thorough history. I love stuff like this.
Because Zeldman had made the switch.
> Why did you start using WordPress?
In my own "notes," I'll sometimes have a `u-photo` sit next to `e-content`, and this way it'll still be shown okay. Posts where a `u-photo` is part of `e-content`, though, will be shown exactly as on the web page itself.
Think I may have found something. Currently _not_ stripping any images or video, i.e., leaving photo posts intact and displaying them as such. Then underneath, in a separate gallery of sorts, I display only those (`u-*`) images that aren't already in the post.
Argh, next one. Would love to find out what goes wrong here. https://xray.p3k.app/parse?url=https%3A%2F%2Fmelanie-richards.com%2Ffeed.xml&pretty=true
Should require only a minor change to a library like X-Ray, which I've already (quite extensively), uhm, "refactored," anyway.
"Your client doesn't support photo posts? Reviews? Replies? Location posts? No worries, we'll make sure it can still show them as simple notes/articles! Same way we treat RSS/Atom entries!"
Now _that_ I would like, but it's not how microformats parsers/Microsub aggregators work.
One thing I really like is implicit post types. We don't hardcode one, it is implied by the (meta)data. What I don't like is how we then go and treat posts completely differently based on their type instead of establish a consistent "baseline behavior." Might as well have set an explicit post type then.
Thing is, I _can't_ just _not_ strip images and pretend `h-entry`s are no different from, e.g., RSS items, because it is possible and quite common to have `u-photo`s adjacent to, rather than in, `e-content`. (What I could do, I suppose, is again check if images are in `e-content`, and only display, separately, I mean, those that aren't.)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!