indieweb/indiewebify-me

Tools to help you get the best out of your indieweb site

indiewebify-me's Issues

Check for rel-syndication on a non-post-permalink (e.g. an h-feed)

Described here http://indiewebcamp.com/irc/2015-03-06#t1425670273229

rel-syndication is page-scoped, so including them on an h-feed with multiple h-entrys causes problems.

This of course depends on #13 -- tests for h-feed in general

Detect likely missing or bad p-name markup and provide a warning

Here's a really simple heuristic for detecting whether the p-name of an h-entry is "bad" in some way, i.e. either missing and thus implied (could check for that in the markup explicitly), or errantly exceedingly big:

if (content && (strlen(name) >= strlen(content)) { /* warn about bad or missing name property, likely same as content or includes of content and UI beyond it */ }

Would be great if indiewebify.me validate-h-entry could detect this and provide a warning, e.g. here is a real world test case:

http://indiewebify.me/validate-h-entry/?url=http%3A%2F%2Fwerd.io%2F2014%2Fegg-brooklyn

Note how big the p-name property on the h-entry is here (bigger than the content)

Add Next and Back/Home links after tests

After clicking on a [Test] button, there is no link to get back to the frontpage or to the next test for that matter. Both should be added.

Dead End: 2. Set up Web Sign In

After we ran the test on this step, the rest of the page disappeared and we were not able to proceed directly to step 3

Indiewebify.me - a Guide to Getting You on the Indieweb

In light of recent comments for individuals trying to get started with Indieweb, suggesting the copy/text on this page be reviewed.

The best way to do this is to present it to an individual at an HWC and see what confuses them.

Testing webmention sends me to a blank page

I entered my domain name into the box and hit the Send Mentions button. It sent me to a blank page with this URL: http://indiewebify.me/send-webmentions/?url=http%3A%2F%2Fdougmckown.com

JS errors on page load

cweiske reported following errors:

in opera, directly on loading: Uncaught exception: TypeError: Cannot convert 'result' to objectEvent thread: readystatechangeindiewebify.me/:284

Uncaught exception: TypeError: Cannot convert 'result' to objectEvent thread: readystatechangeindiewebify.me/:287

in chromium: Uncaught TypeError: Cannot read property 'items' of null :284

Sites that link to an http URL that later gets upgraded to https give 400

eg
http://indiewebify.me/rel-me-links/?url1=http%3A%2F%2Ftantek.com%2F&url2=http%3A%2F%2Fflickr.com%2Ftantek%2F

http://indiewebify.me/rel-me-links/?url1=http%3A%2F%2Ftantek.com%2F&url2=http%3A%2F%2Fwww.facebook.com%2Ftantek.celik

http://indiewebify.me/rel-me-links/?url1=http%3A%2F%2Ftantek.com%2F&url2=http%3A%2F%2Ffoursquare.com%2Ft

Provide more useful information about webmention sending

Given a URL:

• Look for h-entry markup, if none found point to previous stage
• If h-entry markup found, find all links in summary and content as well as in-reply-to links
  • Maybe also look for rel-in-reply-to
• Return HTML page listing found links, in JS fire off calls to send webmentions
• Next to links, return whether or not they support webmention/pingback, what the discovered endpoint is, whether or not the webmention succeeded

Some of this is probably unnecessary to begin with, e.g. the async part (which would also require the endpoint to be split up into find-links and send-webmention), so this is not high priority.

Improve h-card validator

The h-card validator emphatically tells users "Add an email!" or "Add a note/bio!" Instead, it should encourage a core set of h-card properties (probably name: url, photo?) and list additional property options. The language should encourage them to add mf2 markup for any existing contact info without implying they need to add new contact methods they don't list currently.

https://chat.indieweb.org/2017-07-05#t1499298160281000

Instagram test

The Level1 test does not seem to work with Instagram.
I've tested with my own page: http://xuv.be
And the Instagram account related to it is: https://instagram.com/xuvgram

Don't know if it's because the page is actually rendered in javascript.
Before render: the data is in a long JSON like this (removed most of it for clarity):

[…]
"user":{
   "username":"xuvgram",
   "bio":"Collecting laptops covered with stickers #laptopstickers",
   "website":"http:\/\/xuv.be",
[…]

and once rendered:
<a data-reactid=".0.0.2.0.0:0:2.0.2.4.0" href="http://xuv.be" rel="nofollow me">http://xuv.be</a>

(Sorry for the post and re-edit, my fingers slipped on the keyboard)

CSS needs fixing - text cut-off (negative margins?) on left edge when you resize window narrow

h-card validator doesn't check address

The h-card validator appears not to check for address properties (p-locality, etc; see indiewebifyme's view of my h-card vs. glenn jones' parser's). @tantek told me in #indiewebcamp that it just checks the bare minimum for indeweb; I think it'd be great if it checked everything but if not a note explaining what it does check would prevent confusion.

Add checks for in-reply-to, like-of, repost-of to h-entry validator

The h-entry validator should also check to see if an h-entry is:

• a reply with in-reply-to, and if so, to what URL(s)
• a like with a like-of property, and if so, of what URL
• a repost with a repost-of property, and if so, of what URL

Checkmention problems

Checkmention seems to get stuck in an endless loop and there's been no activity there. Might be worth removing it from indiewebify.me

Just completely whitescreen error-ing out on a conversation

The following URL which validates h-entry just fine

http://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fbrennannovak.com%2Fnotes%2F412

But when sending a webmention with IndieWebify me it fails with a blank white screen

http://indiewebify.me/send-webmentions/?url=https%3A%2F%2Fbrennannovak.com%2Fnotes%2F412

validate-h-card failing with “can not read property ‘href’ of null” error

reported in IRC earlier ...
#20:23 [number5] hey guys, http://indiewebify.me/validate-h-card/ seems broken right now, give me “can not read property ‘href’ of null” error, I’m using Chrome for Mac 46.0.2490.71

http://indiewebcamp.com/irc/2015-10-15/line/1444965824529

I just tried it with my own h-card and it worked

URL not correctly found while validating h-entry

When testing my site, here:

http://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fdirkjan.ochtman.nl%2F

The u-url class used in the title links is not found for some reason. Spec problem, or validator problem?

trying to send webmentions hangs with a 500

I put in http://arstechnica.com/information-technology/2015/11/googles-amp-an-internet-giant-tackles-the-old-myth-of-the-web-is-too-slow/ to send webmentions to the indieweb posts linked, and it took a while then showed a 500

Set up a Campaign?

You might want to set up an https://www.iWouldDo.it Campaign to create a movement for the IndyWeb.

(I write this here since there was no email address on http://indiewebify.me)

rel="me" verification fails on http://www.lifewithalacrity.com/

The rel="me" links are on twitter and github, and indieauth sees them correctly. Is there some case sensitivity or other anomaly?

link to source on indiewebify.me

Add draggable bookmarklets for each of the validators

h-entry validator should check for obsolete rels, suggest class

The indiewebify.me h-entry validator should check to see if there are any rel="in-reply-to" or any other old rel values (see indiewebcamp wiki) or odd variants of responses, and suggest the equivalent class instead, e.g.
rel=in-reply-to/u-in-reply-to -> class=u-in-reply-to
rel=like/like-of/u-like-of -> class=u-like-of
etc.

Real world example: https://chat.indieweb.org/dev/2016-09-05#t1473095803155000

Allow unknown X.509 certs and CA

People who use self-signed certs and independent CAs like CACert can not use the various check tools provided by indiewebify.me, all of them fail with the following error:

[curl] 60: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

This should be downgraded to a simple warning, or overridable with a checkbox. What do you think?

Implement canonical h-card parsing

indiewebify.me seems to be assuming the first h-card on the page is the canonical h-card, which is often not the case.

On aaronparecki.com, the first h-card is usually the location of a recent photo.

Validate reciprocal rel=me URLs

Currently indiewebify.me just spits out a list of rel=me URLs found on the given page.

It should be:

• listing all the URLs
• checking to see if they’re reciprocated (mirrored)
• picking up on common fixes like protocol differences

Add test for feed/index/homepage with h-entries

Auto-detect lack of microformat property-nested scoping and warn

E.G. if someone has a h-entry with p-comments without a mf root classname, all of their properties will attach themselves to the parent h-entry and the p-comments will be strings.

Add a webmentions test

It would be cool if one could test his/her own webmentions implementation.

Twitter verification doesn't work

Is most likely the same problem as aaronpk/IndieAuth.com#108

Show names for named posts

Auto-detecting when the name has been implied from a non-named post and not showing it then.

<link rel="author"...> in <head> not detected as authorship claim

The h-entry validator states:

There should also be some way to discover the author of the post — either link to your homepage (which should have your h-card on)from anywhere on the page with rel=author, or optionally embed a p-author h-card in the h-entry.

I have <link rel="author" href="https://skippy.net/"> in the <head> section of my pages. The validator does not detect this, and instead keeps encouraging me to add an author.

I also tried adding <a rel="author" class="h-card" href="https://skippy.net/"></a> to each entry, but the validator didn't detect that, either.

As I am the only author on this domain, it seems extraneous to me to explicitly declare within each h-entry that I am the author.

Detect rel=canonical for url on permalink pages

…possibly suggesting that adding u-url might be a good idea as well for consistency

Check published/updated datetimes for ISO 8601 compliance

With the usual markup demos, how to do human-readable + machine readable, maybe even PHP/Python/etc. demo formatting strings?

Could also try to parse the human-readable date with new DateTime() and print the ISO8601-compliant equivalent if it parses successfully.

Twitter Test

Twitter encodes all URLs in profiles now with t.co shortlinks. Thus the test does not interpret them correctly and says they aren't valid.

Auto-discover software usage and display appropriate tips

E.G. when we fetch someone’s homepage for the rel-me testing, figure out if they’re using wordpress and link to indiewebcamp.com/wordpress for a listing of useful plugins.

We could also detect silo subdomains like *.tumblr.com, *.wordpress.com, *.github.io *.deviantart.com etc. and nudge the owner towards getting a domain that they actually control.

Identify h-entry content marked up with p-content, suggest e-content

List reasons why, provide markup example, etc.

Indieweb comment XSS security testing utility

A tool could be made which, given the URL of a post, sends it a webmention with a bunch of XSS attacks in. Each attack, if successful, does a console.log call with the name of the vulnerability and a URL with instructions on how to prevent it.

Site broken

Parse error: syntax error, unexpected '[' in /web/sites/indiewebify.me/templates/validate-rel-me.html.php on line 35

A simple version that checks all parts in one step

A simple regex-check with a link to the full-check might be enough.

in-reply-to with h-cite validator

The h-entry validator should validate nested in-reply-to h-cites (or not, as the case may be).

Twitter rel=me verification not working

for http://eddiehinkle.com/

https://indiewebify.me/validate-rel-me/?url=http%3A%2F%2Feddiehinkle.com

Only use [rel=me] links with http/https scheme

[rel=me] URLs with other schemes like 'mailto:', 'tel:' raise the error "doesn’t link back", therefore indiewebify.me should limit checking to links with the http/https scheme or no scheme (assuming http in this case, e.g. "//example.com/foo").

Implement /authorship

Currently /validate-h-card only looks for an author property on the discovered h-card.

It needs to implement the algorithm at http://indiewebcamp.com/authorship to find author data.

h-entry validator should check for valid RSVP values!

h-entry validator should detect if an h-entry is an RSVP (e.g. has p-rsvp property) and make sure the value provided is valid (yes,no,maybe,interested).

Maybe suggest markup if an invalid value is provided e.g. if someone says

<span class="p-rsvp">I'm attending</span>

perhaps suggest instead

<data class="p-rsvp" value="yes">I'm attending</data>

cc @aaronpk (who discovered invalid RSVP values received by webmention.io)

"2. Add the ability to send a WebMentions to other IndieWeb sites"

Should read "WebMention", not the plural.

Add non-technical "Getting Started" header

When I had the idea & registered the domain name for indiewebify.me the idea was to make an easy tool to achieve the following:

• More step by step interactive documentation on crucial components
• Allow people developing Indie Web capable applications to test their site/code

It seems I picked a domain name that's too user friendly, as those above goals assume a certain technical baseline. At the Berlin camp multiple people who are non-technical and wanting to "get on the IndieWeb" seemed confused by IndieWebifyMe.

I suggest we had a small header and links that explain this and offer links to Getting Started or something slightly more user friendly that even.

Use [form] elements for return key support

Markup all form submissions with [form] elements so a form submit works without JS and with a return in an [input] element by default.

Detect and call out imprecise datetimes, or ones without timezones