Mefiquote for Chrome/Tampermonkey?

July 22, 2014 11:30 AM

Does Mefiquote work for any Chrome users out there? How did you get it running?
posted by IAmBroom to MetaFilter-Related at 11:30 AM (13 comments total)

IAmBroom: "Does Mefiquote work for any Chrome users out there? How did you get it running?"

My modified version of the script works fine in Tampermonkey. What's the issue you're running into?
posted by zamboni at 11:41 AM on July 22, 2014

Tampermonkey is the goto extension for userscripts in chrome now.
posted by boo_radley at 12:48 PM on July 22, 2014

I use it without modification in Ninjakit.
posted by mkultra at 1:03 PM on July 22, 2014

I've also got it going with Tampermonkey. Works like a charm.

If you're not afraid to play with the settings, you can do fun stuff like block quoting:

mkultra:

I use it without modification in Ninjakit.

And creating your own "reply" button!
posted by charred husk at 1:07 PM on July 22, 2014 [2 favorites]

OK, it's a weirdness of my computer installation. I have it listed as installed, and it was enabled (but it wasn't working). I disabled it, and since then I can't touch it - can't remove it, even.

Weird.
posted by IAmBroom at 1:51 PM on July 22, 2014

charred husk: And creating your own "reply" button!

I use a quotation mark. It goes nicely with the [+] and [!].
posted by Rock Steady at 2:03 PM on July 22, 2014

Rebooted, removed it, and installed it manually through the editor. It even asked if I wanted to enable it!

And.... nothing.
posted by IAmBroom at 2:04 PM on July 22, 2014

Do you have secure browsing enabled? That often breaks user scripts.
posted by pb (staff) at 2:17 PM on July 22, 2014 [1 favorite]

Do you have secure browsing enabled? That often breaks user scripts.

Ah, that just solved a problem with my MeFi Greasemonkey scripts I was having today. Thanks!

Please forgive my ignorance, but why does secure browsing break scripts?
posted by His thoughts were red thoughts at 5:23 PM on July 22, 2014

why does secure browsing break scripts?

Because most scripts were written before we implemented secure browsing as an option. (We added it about a year ago.) So the script authors weren't expecting the site to operate in the more secure context. Sometimes adding support for secure browsing is as simple as telling the script to run at https URLs in addition to http URLs. Other times there are more complicated things going that simply won't work due to the browser's different security rules on secure pages.
posted by pb (staff) at 6:41 PM on July 22, 2014 [1 favorite]

Thanks for that.
posted by His thoughts were red thoughts at 9:14 PM on July 22, 2014

pb: Do you have secure browsing enabled? That often breaks user scripts.

WHOOHOO! Thanks, pb!!!
posted by IAmBroom at 10:33 AM on July 23, 2014

pb: "Sometimes adding support for secure browsing is as simple as telling the script to run at https URLs in addition to http URLs."

Holy crap, this just made my day. I've missed this script.
posted by brundlefly at 2:56 PM on July 23, 2014