Web client crashing Chrome frequently when adding tags

Filed an Issue Hypothesis (GitHub)
Annotate with anyone, anywhere. https://hypothes.is/ Contribute to hypothesis/h development by creating an account on GitHub.
I’m currently using Chrome Version 79.0.3945.117 (Official Build) (64-bit) via the chrome extension on Windows 10 (v1809) and I’m noticing just within the last two weeks that as I’m typing within the H interface that Chrome suddenly crashes.

All of the crashes have occurred as I’m adding one or more tags to an annotation/highlight. I haven’t experienced a crash while creating annotation text.

The crash is immediate and complete and doesn’t just take out the individual tab, but the entirety of the Chrome processes. While it’s possible that this could be a Chrome issue, I’ve not experienced any crashes with any other websites in ages. I also know that there has been some new code and UI work around the interface and the way that tags are displayed in the public H product.

My initial guess is that something may be happening within the memory/caching as H tries to pull past tags from the server to guess what I’m typing.

I’ve alternated with using Firefox and the bookmarklet and have yet to see an issue with crashes there.

Replied to Sending Webmentions More Intelligently by Jamie Tanna (jvt.me)
You mentioned that you tweaked things a few weeks back and fixed the issue, but I noticed today that your site is hitting http://mention-tech.appspot.com/ pretty regularly and still automatically sending what appear to be hundreds of old webmentions. I’m not sure what you were using to send them on your behalf or what your tweak was, but thought I’d mention it if you had previously used Kevin’s service and either forgot to turn it off/disconnect it or something else odd was going on.
Filed an Issue [Narwhal Microblog] Support (wordpress.org)
Using v2.1 of Narwhal Microblog on WordPress 5.2.4 and PHP v7.2 I get the following error:

Warning: Use of undefined constant posthasteForm - assumed 'posthasteForm' (this will throw an Error in a future version of PHP) in /home/public_html/wp-content/plugins/narwhal-microblog/narwhal-microblog.php on line 265

Knowing that Posthaste was the underlying code, I suspect it’s an issue with php and the version in use. Apparently we’ve gotten to the version where posthasteForm is throwing the expected errors. 🙂

I’m not seeing any specific funcionality issues with the plugin, but it is throwing this error on the pages where Narwhal appears.

Manually reconstructed Bridgy URLs redirect to silos

Filed an Issue snarfed/bridgy (GitHub)
Bridgy pulls comments and likes from social networks back to your web site. You can also use it to publish your posts to those networks.
It’s mentioned in the documentation that one can reconstruct URLs to allow manually resending webmentions for missed backfeed. However, it appears this may no longer work(?) as these reconstructed URLs, which used to be static are now automatically redirecting to their siloed instances.

Example: https://brid.gy/post/twitter/schnarfed/476408043819659264
redirects to https://twitter.com/schnarfed/status/476408043819659264

Separately, though related, the example in the documentation for Instagram no longer seems to exist and could be replaced and the example for Google+ could be removed as the service no longer exists.

No webmentions to original URLs that include emojis

Filed an Issue snarfed/bridgy (GitHub)
Bridgy pulls comments and likes from social networks back to your web site. You can also use it to publish your posts to those networks.
I’ve found a few instances in which Brid.gy will apparently fail to send a webmention (and/or fail to find a target) when the original URL contains an emoji(s). I’d suspect it’s a quirky encoding issue of some sort. I’m sure I’ve seen this issue before on Instagram where it’s probably more likely as the result of emojis in Instagram “titles” when using PESOS methods.

When I subsequently remove the emoji from the permalink, and reprocess Bridgy then has no problem finding the URL and sending the webmention. So at least there’s a “fix” on the user’s side for those experiencing this issue, but only if they’re aware it exists and have the means of executing it.

Example of failed webmention:

(I’ll note that it’s also got a fragment # in the URL, but don’t think this is a part of the issue)

Original: https://boffosocko.com/2019/04/29/%F0%9F%93%85-virtual-homebrew-website-club-meetup-on-may-15-2019/?replytocom=262215#respond

Syndicated copy that was liked: https://twitter.com/ChrisAldrich/status/1129124049068498944#favorited-by-14591484

Bridgy Log: https://brid.gy/log?start_time=1558056830&key=aglzfmJyaWQtZ3lyTAsSCFJlc3BvbnNlIj50YWc6dHdpdHRlci5jb20sMjAxMzoxMTI5MTI0MDQ5MDY4NDk4OTQ0X2Zhdm9yaXRlZF9ieV8xNDU5MTQ4NAw

Example of previously failed webmention that ultimately went through following emoji removal:

Original: https://boffosocko.com/2019/04/29/%F0%9F%93%85-virtual-homebrew-website-club-meetup-on-may-15-2019/?replytocom=262215#respond

Syndicated copy: https://twitter.com/ChrisAldrich/status/1129124049068498944#favorited-by-19844672

Bridgy Log: https://brid.gy/log?start_time=1558714459&key=aglzfmJyaWQtZ3lyTAsSCFJlc3BvbnNlIj50YWc6dHdpdHRlci5jb20sMjAxMzoxMTI5MTI0MDQ5MDY4NDk4OTQ0X2Zhdm9yaXRlZF9ieV8xOTg0NDY3Mgw

Another potential example from Instagram

Done via PESOS from Instagram which I’m sure missed webmentions (though too far back to find the specific logs):
https://boffosocko.com/2017/10/15/docteur-jerry-et-mister-love-%E2%9D%A4%EF%B8%8F%E2%9A%97%EF%B8%8F%F0%9F%91%93%F0%9F%8E%ACi-found-this-original-french-one-sheet-47-x-63-after-the-move-will-have-to-get-it-mounted-and-fram/

Scrolling error on Annual Site Stats page

Filed an Issue Automattic/jetpack (GitHub)
Increase your traffic, view your stats, speed up your site, and protect yourself from hackers with Jetpack. - Automattic/jetpack
Perhaps this is a native WP.com issue, but I suspect it’s JetPack functionality as it occurs both with a .org connected account as well as an example.wordpress.com domain both of which have a “Powered by JetPack” logo on the bottom of the page.

Steps to reproduce the issue

  1. Go to https://wordpress.com/stats/day/annualstats/example.com
  2. Scroll down the page (zoom in if necessary so that the table fills the entire screen; the error isn’t as or won’t be obvious on a new account or if one doesn’t have several years worth of data to view)

What I expected

I expected the entire chart and page to scroll down.

What happened instead

The Year column stayed fixed and the remainder of the chart scrolls down the page instead. Without zooming in/out on the entire page, one can’t visualize the data or have it align properly.

Screenshots
Here’s a shot of the misaligned static year column versus the remainder of the chart which scrolls up/down.
On a multi-column display the year column doesn't scroll in alignment with the remainder of the chart

PubMed parsing

Filed an Issue Parse This Parsing Library for WordPress (GitHub)
Can Act as a Standalone Plugin - dshanske/parse-this
I would think that a major information hub like PubMed would have better metadata given its position in the research space but apparently not. It returns very little data, but could be way better.

Example page: https://www.ncbi.nlm.nih.gov/pubmed/17083004

Proper tagging on upper case vs lower case

Filed an Issue ActivityPub for WordPress. (GitHub)
Contribute to pfefferle/wordpress-activitypub development by creating an account on GitHub.
Not quite sure what may be causing it, but I’ve noticed on my site that I get a properly tagged but don’t get it properly tagged when I use lower case . Is this to be expected or something in the line of a regex issue?

Examples: [1] [2]

Improve instructions for use

Filed an Issue Automatically send mentions to IndieNews. (GitHub)
Contribute to pfefferle/wordpress-indienews development by creating an account on GitHub.
Some who come across the plugin who are relatively IndieWeb-aware don’t know how to use the plugin:
eg: https://islandinthenet.com/saturday-16-february-2019-1017am/ which has resulted in some unintended spam in the IndieNews feed.

What exactly are the triggers for syndicating to IndieWeb News and Indieweb.xyz? Is it just having a tag indienews, indieweb, or even indie* where * is a wildcard? Are there others I may be missing?

Can one target other subs within indieweb.xyz (examples: /en/longreads or /en/games/) or just the /language/indieweb/ sub with the plugin? How is differentiating them done from the user’s perspective? I do see a reference to the /hottubs/ sub in the code, but I’m not following all the logic there.

I suspect it would also be nice to have some details about the dashboard widget and news feeds as well as listing a requirement for the Webmention plugin which some might not know about.

I’m happy to modify the readme’s with better instructions if I can be a bit more clear on some of what the code is doing with regard to the above.

A few display quirks in the Syndication Links plugin

Filed an Issue Add and Display Syndication Links. (GitHub)
Contribute to dshanske/syndication-links development by creating an account on GitHub.
With the most recent update I’m noticing a few small edge case quirks that seem to have popped up:

For syndication to indieweb.xyz the displayed result (set for icon only) is giving a relatively interesting “info” icon,which is a reasonable proxy, but sadly the hover text is also “info” instead of a more useful or expected “indieweb.xyz”.

For syndications to reading.am (which I’m guessing still doesn’t have a service specific icon) instead of giving the old default image of a globe icon, it’s not displaying anything at all. I haven’t tested specifically, but are unmapped urls still given that old default icon?

I’m still seeing issues with my chrisaldrich.wordpress.com URL. Previously it displayed a blank space (presumably not able to understand the inpub), but the newer version is displaying the word “WordPress” even when I’m using icons only. (Example: https://boffosocko.com/2019/02/14/a-sketch-for-an-indieweb-bullet-journal/#Syndicated%20copies) My initial inclination is that the two instances of “WordPress” at https://github.com/dshanske/syndication-links/blob/057733d921b485cf8f0eb98b28b104ccb708bd21/includes/class-syn-meta.php#L333 are both CamelCase when all the other examples around/near that segment of code are all lower case.

Default avatars for refbacks

Filed an Issue Refbacks for WordPress by David ShanskeDavid Shanske (GitHub)
Contribute to dshanske/wordpress-refback development by creating an account on GitHub.
Refbacks in conjunction with the Webmention plugin and Semantic Linkbacks plugin don’t have as solid a parity with webmentions as they show up in the comments section as text instead of as an avatar. Perhaps it would be prettier if refbacks were given a default system avatar (possibly modifiable) for display?

Setting to discard self-refbacks

Filed an Issue Refbacks for WordPress. by David ShanskeDavid Shanske (GitHub)
Contribute to dshanske/wordpress-refback development by creating an account on GitHub.
Given the tremendous number of self-refbacks, it would be nice to have a setting that would allow the plugin to silently discard refbacks to one’s own website. Since adding the plugin I’d estimate that 99.9% of the refbacks I get are from people clicking links on my own website rather than external links others.

This should be separate from preventing self-webmentions as I (and I suspect others may) want to have those show up to cross link or cross reference posts on their own sites.

UI suggestion: Admin drop down filter for refbacks

Filed an Issue Refbacks for WordPress (GitHub)
Contribute to dshanske/wordpress-refback development by creating an account on GitHub.
Similar to the design set up for other comment types, it would be nice to have a filter for refbacks in the dropdown menu at /wp-admin/edit-comments.php. With the Webmentions plugin enabled, one is presented with the options to filter for “All Comment Types”, “Comments”, “Pings”, and “Webmentions”. Adding a filter for “Refbacks” would be incredibly helpful as well.

Simple Location’s Last Seen widget is revealing private locations

Filed an Issue Simple Location Plugin for WordPress (GitHub)
Adds Basic Location Support to Wordpress. Contribute to dshanske/simple-location development by creating an account on GitHub.
Using the version 3.5.2 of Simple Location, I’m most recently checked into a location that is marked as private, but the location widget indicates “Private” followed by the exact street address to the private location to which I’m checked in. Previously the widget showed the most recent public location, but now it’s explicitly uncovering private locations.

Perhaps it’s related to the recent fix that was causing private posts to be marked public?

Simple Location’s “Last Seen” widget is revealing private locations.

Space separated tags not appropriate for WordPress multi-word tags

Filed an Issue Omnibear (GitHub)
A Micropub browser extension. Contribute to keithjgrant/omnibear development by creating an account on GitHub.
WordPress installs will frequently use multi-word tags/categories, thus there is no way to send those tags when Omnibear defaults to space separated tags. Comma, semi-colon, or other separators may be better in these situations.