Hi #fediverse and #indieweb - is there a #microformats #activityPub (maybe via #rss?) bridge of some kind to push content to mastodon? Any link or advice that would work for https://hroy.eu/blog/ (not WordPress)?

Making sure my resume is a parseable #microformats [h-resume](https://microformats.org/wiki/h-resume) is my favorite way to #procrastinate about applying to new #jobs

I've been following the #indieweb / #microformats movement for a very long time. Every now and then (and today is one of those days) I feel the urge of investigating it all again, creating my own blog with h-card, h-entry, webmentions... But somehow I feel it's an all-or-nothing approach: either you use WordPress + plugins (which I don't want for `$reasons`) or you build the whole thing yourself.

I wish there was something just at the right level of abstraction, an HTML framework of sorts (1/2)

This here search results page shows a few likes and bookmarks (instances of the note CPT but with bookmark microformats) and regular notes: https://build.boddez.net/?s=note

No post content is shown. Just titles and (plain-text) excerpts. Still, the (relevant) #microformats get picked up OK.
https://xray.p3k.app/parse?url=https%3A%2F%2Fbuild.boddez.net%2F%3Fs%3Dnote&pretty=true

Tried to improve #IndieBlocks’ title block rendering a bit.

I.e., when enabled, the plugin’s microformats “module” will filter certain core blocks, add bits of HTML (“microformats”) to them. And I think I made the Post Title block just a little better.

Way more code, too, dangit. And I _still_ have to resync (or at least check if a resync is in order) with core’s render functions.

#WordPress #microformats

Always a good idea to check one’s #microformats

Hm… I don't do #Reddit but apparently a certain site set a bad example with it's API pricing: https://www.reddit.com/r/apolloapp/comments/13ws4w3/had_a_call_with_reddit_to_discuss_pricing_bad/

Not the first huge player clamping down on it's API killing off 3rd party apps and burning bridges. This seems to be the nature of silos (or so called walled gardens).

If only there would be a solution to this dilemma. Something interoperable. Ideally without an API at all.

Like #microformats and #Webmention|s or #RSS|json|atom feeds.

Ah well, #ActivityPub will do for now 🤓

@ayo now it just needs #microformats too so other #Webmention enabled sites can parse something useful of yours 🙃

Oggi tuning del mio sito...

[x] Aggiunta una manciata di #microformats ai post per migliorare l'indicizzazione.

[x] Risolto un problema che non faceva aggiornare a #Jekyll la data di ultima modifica sulla #sitemap

[x] Messa in evidenza la presenza del feed #RSS

[x] Aggiunto invito a offrirmi un caffé

[ ] Combattuto e perso contro le CSP (Content Security Policies) per impedire style-injection... rompe diverse estensioni dei browser che migliorano l'accessibilità, quindi mi sono arreso.

I've been updating my site at https://starbreaker.org/ with #IndieWeb #microformats.

#IndieAuth for starbreaker.org works.

h-card is implemented.

https://indiewebify.me/validate-h-card/?url=https%3A%2F%2Fstarbreaker.org%2F

h-entry validation still needs a bit of work.

https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fstarbreaker.org%2Fblog%2Fspiral-architect%2Fchapter-003%2F

And I haven't gotten around to #WebMentions yet, but there's a #npm package I can run on one of my machines at home as a cron job to check my #RSS feed and send them. Receiving them will entail some more work...

Added the most basic h-event, h-recipe, and h-review support to IndieBlocks. (Read: If it encounters, e.g., `dt-start` or `p-rating`—all of which you’d still have to enter by hand—it’ll add one of these as a post class, rather than “just” `h-entry`.)

#indieblocks #microformats #plugins #wordpress

(https://bddz.be/jrN)

@rasterweb
#metadata and #microformats could provide #AI #ImageProtection by clearly labeling the usage rights of the artwork being scraped or sampled. This won't prevent bad actors, but it will make it easy for people and companies to do the right thing.

Just ingest the microformat and see if it meets your use-case.

#Flickr has similar metadata on many images in its APIs, but the spec could use an update for the #AI age.

@rasterweb
#Cryptographic #AI #ImageProtection can work for a few reasons

1. declares an intent to protect
2. amplifies #copyright law around encrypted content
3. scrappers are usually simple, and this adds complexity at a different layer than the machine learning algorithm
4. #cryptography adds compute time to the process; how much depends on how dense the method is.

But #metadata and #microformats are also useful

@rasterweb I don't think this will work long-term.

#AI(s) are really good at learning complex patterns; this is just another complex, regular pattern.

There are really only two solutions that will work,
1. #cryptography
2. respecting #copyright restrictions via #metadata and #microformats

While IndieBlocks works "great" for "microformatting" bits of (mostly short) #WordPress posts, it would be _just wonderful_ if we could one day **simply add classes to inline links**.

Just encountered the dreaded "block validation error" after manually adding `class="u-bookmark-of"` to a Quote block's "cite" link.

Convert to "Custom HTML" it is. (Takes away _a lot_ of the block editor's "WYSIWYG appeal," though.)

#microformats

One of my goals on the site over the next few months is to support the right metadata standards to let articles be as shareable as possible across platforms. Every 19th article is already #microformats encoded, but we'll be adding #hfeed, and some other feed formats you may be familiar with.

@sturobson @tantek.com @tantek.com oh the #microformats IRC channel - those were the days 😂

Yep this stuff is deeply embedded. I've said as much to people that good semantic HTML is an excellent humans and machine readable interop for data.

We got old. #Microformats reached 19 years. Wow.
https://tantek.com/2023/047/t1/nineteen-years-microformats

I'm feeling like this will change search engine optimization forever. In the before-GPT world, #SEO experts manually determined keywords, descriptions, and #microformats. They had to create machine-parseable URLs and taxonomies. In the post-GPT world, so long as your pages are linked together and you have high-quality text (minimal ads, high subject relevance), the parser should be able to categorize your site accurately. Then you show up on the map of rewards.

The Opera/Presto browser was pretty close to being a “swiss army knife” for the web. Aside from the #browser with a solid and modern rendering engine with decent standard support (for the time), it also integrated (in the same UI!) a workable #email client, a decent #IRC client, and a competitive #RSS reader. The browser itself not only had better support for web standards than some of the competitors (including WebKit) in many areas, but it also put effort in supporting #microformats