👓 JSON Feed for WordPress updated | Manton Reece

Read JSON Feed for WordPress updated by Manton ReeceManton Reece (manton.org)
It has been over a year since JSON Feed was announced. There have been a bunch of discussions about expanding the specification, but we are very happy with how well the initial version has worked. It powers all Micro.blog-hosted blogs by default and is also used on many WordPress blogs, home-grown s...

Some ideas about tags, categories, and metadata for online commonplace books and search

Earlier this morning I was reading The Difference Between Good and Bad Tags and the discussion of topics versus objects got me thinking about semantics on my website in general.

People often ask why WordPress has both a Category and a Tag functionality, and to some extent it would seem to be just for this thing–differentiating between topics and objects–or at least it’s how I have used it and perceived others doing so as well. (Incidentally from a functionality perspective categories in the WordPress taxonomy also have a hierarchy while tags do not.) I find that I don’t always do a great job at differentiating between them nor do I do so cleanly every time. Typically it’s more apparent when I go searching for something and have a difficult time in finding it as a result. Usually the problem is getting back too many results instead of a smaller desired subset. In some sense I also look at categories as things which might be more interesting for others to subscribe to or follow via RSS from my site, though I also have RSS feeds for tags as well as for post types/kinds as well.

I also find that I have a subtle differentiation using singular versus plural tags which I think I’m generally using to differentiate between the idea of “mine” versus “others”. Thus the (singular) tag for “commonplace book” should be a reference to my particular commonplace book versus the (plural) tag “commonplace books” which I use to reference either the generic idea or the specific commonplace books of others. Sadly I don’t think I apply this “rule” consistently either, but hope to do so in the future.

I’ve also been playing around with some more technical tags like math.NT (standing for number theory), following the lead of arXiv.org. While I would generally have used a tag “number theory”, I’ve been toying around with the idea of using the math.XX format for more technical related research on my site and the more human readable “number theory” for the more generic popular press related material. I still have some more playing around with the idea to see what shakes out. I’ve noticed in passing that Terence Tao uses these same designations on his site, but he does them at the category level rather than the tag level.

Now that I’m several years into such a system, I should probably spend some time going back and broadening out the topic categories (I arbitrarily attempt to keep the list small–in part for public display/vanity reasons, but it’s relatively easy to limit what shows to the public in my category list view.) Then I ought to do a bit of clean up within the tags themselves which have gotten unwieldy and often have spelling mistakes which cause searches to potentially fail. I also find that some of my auto-tagging processes by importing tags from the original sources’ pages could be cleaned up as well, though those are generally stored in a different location on my website, so it’s not as big a deal to me.

Naturally I find myself also thinking about the ontogeny/phylogeny problems of how I do these things versus how others at large do them as well, so feel free to chime in with your ideas, especially if you take tags/categories for your commonplace book/website seriously. I’d like to ultimately circle back around on this with regard to the more generic tagging done from a web-standards perspective within the IndieWeb and Microformats communities. I notice almost immediately that the “tag” and “category” pages on the IndieWeb wiki redirect to the same page yet there are various microformats including u-tag-of and u-category which are related but have slightly different meanings on first blush. (There is in fact an example on the IndieWeb “tag” page which includes both of these classes neither of which seems to be counter-documented at the Microformats site.) I should also dig around to see what Kevin Marks or the crew at Technorati must surely have written a decade or more ago on the topic.


cc: Greg McVerry, Aaron Davis, Ian O’Byrne, Kathleen Fitzpatrick, Jeremy Cherfas

Reply to Geolocating your travel blog posts by Mark Grabe

Replied to Geolocating your travel blog posts by Mark GrabeMark Grabe (Learning Aloud)
A travel blog by definition describes experiences at many specific places. The location is part of the context for each post. I use Blogger for this particular blog and after several years of writing posts about traveling, I finally noticed that Google allows the author to associate a location with each post. I am guessing few Blogger bloggers use this feature, but I thought it might be worth exploring.
For those using WordPress, there’s a simple plugin called Simple Location that has some similar functionality. It has settings for a number of map providers that can be used to display maps as well as weather conditions.

Many people use it specifically for creating checkins, but it could also be used by travel bloggers. It’s also got a widget to show one’s last known location in a sidebar or footer.

Refback from IndieWeb Chat

It took me a moment to realize what it was exactly since I hadn’t yet added a field to indicate it, but since the IndieWeb chat doesn’t send webmentions by itself, I’m glad I support refbacks to be aware of comments on my posts. The avatar didn’t come through quite like it should, but it’s nice to be able to treat refbacks like any other type of mention.

Thanks David Shanske for the Refbacks plugin. Thanks Tantek for what I think is my first incoming “mention” from chat.

The chat has some reasonable microformats markup, so I suppose the parser could do a more solid job, but this is a pretty great start. Sadly, Refback isn’t as real-time as Webmention, but it’s better than nothing.

My first mention (aka refback) from the IndieWeb chat. Click on the photo to see the UI display on my site.

I suppose we could all be posting chats on our own sites and syndicating into places like IRC to own our two directional conversations, but until I get around to the other half… (or at least for WordPress, I recall having gotten syndication to IRC for WithKnown working a while back via plugin.)

Reply to WordCamp: Publishers

Replied to a tweet by WordCamp: PublishersWordCamp: Publishers (Twitter)
Leo [@postphotos] are you thinking what I’m thinking?
#Route66 #FromChicagotoLA

👓 Announcing WP-Lens a new, simple WordPress Theme for Photographers | Alan Levine

Read Announcing WP-Lens a new, simple WordPress Theme for Photographers by Alan Levine (CogDogBlog)
Here is another new experimenting in porting a Creative Commons licensed HTML5 Up template into a WordPress theme, say hello to WP-Lens. This joins my three previous HTML5 Up to WordPress themes, I…
Replied to a tweet by Bridget WillardBridget Willard (Twitter)
Has anyone tried out Micropub clients like Quill, OwnYourSwarm, OwnYourGram, Omnibear, Micropublish, or others as alternatives to Gutenberg as a posting interface? There’s a nice WordPress-based Micropub endpoint available.

I’ve been using Micropub more and more over the past couple of years and I love the convenience and simplicity for a huge variety of posting needs including custom apps like Teacup and Screech for audio/podcasting.

An Indieweb Podcast: Episode 10 The Thrilla in Manilla

Episode 10: The Thrilla in Manilla

Running time: 1h 28m 36s | Download (27.0MB) | Subscribe by RSS | Huffduff

Shownotes

October 1st will be the 43 anniversary of the Ali/Frazer fight, so this week’s title is apropos after David spent a month in Manila working on many IndieWeb related projects including the Micropub plugin, client discovery in IndieAuth, Post Kinds, etc.

In this week’s episode, we discuss new developments in WordPress and what David has wanted to accomplish for all these years in the IndieWeb community: the ability to read something on his phone, store it on his website to either share or just save, as appropriate.

👓 Trying Mastodon | Gary Pendergast

Replied to Trying Mastodon by Gary PendergastGary Pendergast (Gary Pendergast)
It’s no secret that Twitter is red hot garbage fire, so I’ve signed up for a Mastodon account to give them a try. Because I’m super vain, I decided to create my own Mastodon instance, with a custom domain.
I know of a few folks in the IndieWeb and WordPress communities like Ryan Barrett (with FedBridgy) and Mathias Pfefferle (with OStatus plugin) who are actively working on helping bridge the technology between websites and the Fediverse so that one could use their WordPress install as a stand-alone “instance” of Mastodon.

It already seems somewhat obvious that moving from Twitter to Mastodon is bringing along some of the problems and issues that Twitter users are facing, so being able to use your current WordPress (or other) website to interact with other instances, sounds like a very solid idea. In practice, it’s the way I’ve been using my website with Twitter 1 2 (as well as Google+, Instagram, Facebook and other social silos) for some time, so I can certainly indicate it’s been a better experience for me. Naturally, both of their efforts fall underneath the broader umbrella of the web standards solutions generally pushed by the IndieWeb community, so I’m also already using my WordPress-based site to communicate back and forth in a social media-like way with others on the web already using Webmention, Micropub, WebSub, and (soon) Microsub.

These federation efforts have got a way to go to offer a clean user experience without a tremendous amount of set up, but for those technically inclined, they are efforts certainly worth looking at so one needn’t manage multiple sites/social media and they can still own all the data for themselves.

 

References

1.
Aldrich C. @Mentions from Twitter to My Website. BoffoSocko. https://boffosocko.com/2017/04/15/mentions-from-twitter-to-my-website/. Published April 15, 2017. Accessed September 11, 2018.
2.
Aldrich C. Threaded conversations between WordPress and Twitter. BoffoSocko. https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/. Published July 2, 2018. Accessed September 11, 2018.

👓 Forking is a Feature | Gary Pendergast

Read Forking is a Feature by Gary Pendergast (Gary Pendergast)
There’s a new WordPress fork called ClassicPress that’s been making some waves recently, with various members of the Twitterati swinging between decrying it as an attempt to fracture the WordPress community, to it being an unnecessary over-reaction, to it being a death knell for WordPress. Pers...
Again, here, I’m reminded of some of the benefits that the BackDrop fork of Drupal is providing not only to itself, but to the larger Drupal community. Naturally there’s a better way of doing these things, but it takes foresight and work–a lot of work.

👓 Foxland products for free | Foxland

Read Foxland products for free by Sami Keijonen (Foxland)
All my themes and plugins are now free. At the moment I feel that’s a permanent decision but you’ll never know. I want to thank all who have supported my journey. Either by purchasing, helping, or sharing ideas. I’ll do my best to answer some of the questions you might have. Why free? I don’...

👓 ClassicPress: Gutenberg Not Included | WordPress Tavern

Read ClassicPress: Gutenberg Not Included (WordPress Tavern)
Depending on how far and deep you look, there is not a lot of positive sentiment surrounding Gutenberg. For Scott Bowler, the notion of merging Gutenberg into WordPress 5.0 represents a shift so de…

👓 WordPress to Support Classic Editor for “Many Years to Come,” Plugin and Theme Markets Expected to Drive Gutenberg Adoption | WordPress Tavern

Read WordPress to Support Classic Editor for “Many Years to Come,” Plugin and Theme Markets Expected to Drive Gutenberg Adoption (WordPress Tavern)
During the 2017 State of the Word address, Matt Mullenweg announced the availability of the Classic Editor plugin for site owners who are not ready to adopt Gutenberg when it makes its debut in Wor…

👓 Our Mission Statement | ClassicPress

Read Our Mission Statement (ClassicPress)
1. If it isn’t broken, we won’t fix it
2. Major decisions will be made by the community
3. We will facilitate democratic discussion and decision making
4. We will make people’s lives better
5. We will invest in the future of ClassicPress