111–120 of 132 posts
A side note, browsers are making bookmarklets harder to use in the name of security. Making it possible for web sites to block bookmarklets via Content-Security-Policy.
I hate this. I rely on bookmarklets heavily in my workflow, and this really bothers me.
Author here — really happy that a joke project I did 7.5 years ago (while working at a typical outsourcing company) finally got a spotlight on HN! Please feel free to contribute! I cleaned up and modernized the repo a little recently, but didn't revise the terms list properly in a very long time (except a few obvious additions like "autonomous" and "AI"), so it's a little outdated. There's so much new bullshit to add…
The dictionary it uses is even more entertaining: https://github.com/mourner/bullshit.js/blob/master/src/terms...
This is best of breed technology to make the world a better place.
Earlier quoted context omitted.
Cloud-to-Butt failed me when I clicked on a link for cloudflare, which had been rewritten for buttflare.com while I was at work.
Does that domain actually exist, and what does it host? (I don't want to check right now for obvious reasons).
If you're looking for that other site, stuff redirects there other than this page
(Cloud is striked through)
Earlier quoted context omitted.
a more general such tool: http://proselint.com/
Thanks, looks great. I need to get this hooked into Emacs!
(flycheck-define-checker proselint
"A linter for prose."
:command ("proselint" source-inplace)
:error-patterns
((warning line-start (file-name) ":" line ":" column ": "
(id (one-or-more (not (any " "))))
(message (one-or-more not-newline)
(zero-or-more "\n" (any " ") (one-or-more not-newline)))
line-end))
:modes (text-mode markdown-mode gfm-mode org-mode))
> SAP sets course for the future with bullshit bullshit
> HR and People bullshit
> Bullshit announcement
> Bullshit and digital core
> Future of bullshit has feelings
And finally:
> Intelligent Bullshit
As always with these bookmarklets that load additional JS from a remote source: Be sure you understand the possible security implications. You're essentially XSS attacking yourself if that JS source is turning hostile for any reason. One possible solution is to use SRI to ensure the linked JS doesn't load if it changes for any reason, but doesn't work in that case as the CDN (unpkg.com) doesn't add a CORS header.