mrcoles
GoFullPage was temporarily taken down from the Chrome Web Store because of a copyright-related issue. This was not a security issue with the extension.
We are working closely with Google on resolving this. We are feeling positive about the situation and see a clear path forward toward restoring the official GoFullPage extension. We unfortunately don’t have a firm timeline, yet.
In the meantime, there are now several ways to continue using it and any paid functionality:
1. Re-enable GoFullPage: If Chrome disabled the extension, rather than removing it entirely, you may still be able to re-enable it at chrome://extensions. Whether you re-enable it or not, we recommend you leave it on Chrome, so you can recover it when it is restored.
2. Chrome beta: We have a beta version of GoFullPage available in the Chrome Web Store, providing users the newest functionality and another way to use GoFullPage while the official version is being restored. Both extensions can be installed simultaneously. Official link: https://chrome.google.com/webstore/detail/kehafhfdnkhdgbnpeo....
3. Microsoft Edge: GoFullPage continues to work normally on Edge. Official link: https://microsoftedge.microsoft.com/addons/detail/gofullpage....
4. Firefox: We are also working on a Firefox version.
We know this has been disruptive, but things are moving in the right direction. We’re actively working on this from multiple directions. You can track updates from any of our official communication channels:
- https://blog.gofullpage.com/
- https://twitter.com/gofullpage
- https://www.linkedin.com/company/gofullpage
- https://www.facebook.com/GoFullPageOfficial
Edit: formatting
Also, are there any unexpected positive or negative outcomes so far? For example, do people feel pressured to smile or anything else like that?
My goal was to not have to dig around for the unique documentation for whatever language/library I was using the moment to format a datetime string.
By unifying the codes across different languages, I was able to make a universal translator that could convert between any of the ones I had supported (and provide a structured autocomplete search too).
It’s not perfect, but hopefully makes some other folks’ lives easier!
I also made a convenience library on top of cheeriojs that supports all of their traversing methods via pseudo-classes in the query string: https://github.com/mrcoles/pseudo-cheerio
Show HN: DateKnight a datetime string formatting reference and translator
Also, your first sentence is asking the wrong question ;P
Here are some other things I’ve built in the past because the code and/or the idea was interesting to me: http://mrcoles.com/failed-projects/ | http://mrcoles.com/dragondrop/ | http://mrcoles.com/tetris/ | http://mrcoles.com/low-res-paint/ | http://mrcoles.com/piano/ — don’t bother asking for a usecase ;)
Also, what does it say if I do `git help ship`?
https://chrome.google.com/webstore/detail/full-page-screen-c...
https://github.com/mrcoles/full-page-screen-capture-chrome-e...
https://github.com/mrcoles/full-page-screen-capture-chrome-e...
It’s malware & spyware free. I built the extension to take a screen cap of a seating chart that I built as a web page for my wedding—since all the other extensions at the time were broken. Why a web page for my seating chart? IDK, I wanted to play with CSS3 columns, alas I should have used photoshop…
I have been contacted by people who want to buy the extension, but it seems too dangerous, since they could easily install their own malware—I wonder if anything like this happened to “Awesome Screenshot”? My own conscience and, more importantly, my personal brand is too important to me to sell it.
In terms of the permissions, when I built it, I had to ask for those permissions in order to make it work. If you find any changes to chrome permissions that let me ask for fewer, please let me know or, better, submit a pull request.
Also, instead of PhantomJS, if you have a Mac, try out `webkit2png`, which works great as long as you don't need to login or interact with a page before the screenshot:
If you click the square in the upper right, you'll get options to change the waveform and volume response. There are some other options too, like shifting by an octave or changing the color of the piano :)
Better things could be done by using the web audio APIs, but I explicitly started this project wanting to build audio using data URIs.
There are lots of things that make actual QWERTY piano difficult, e.g., fewer keys than notes on a piano, hitting complex chords would be very difficult (regular typing doesn't train you to type entire words in a single combined press of keys), computer keyboards have no benefits of weighted keys—but perhaps at least one note a time melodies could be played pretty proficiently by non-musicians with a QWERTY player?
I wrote this web app in May 2012—I don’t think iOS was there yet? I’m open to a pull request though https://github.com/mrcoles/javascript-piano but since the project was mainly a test for generating different wave files as dataURIs (and the piano was an afterthought that was actually spawned from this half-baked idea http://mrcoles.com/media/test/guy/ ), idk if the dataURI approach is any easier on iOS yet (or ever will be)?
I assume the audio APIs would make less click-y sounds (and don't suggest manually created wave files as a solid way to create perfect sounds), but I also sort of like the clicks. When I presented this at Hack and Tell NYC, I claimed that you had to play it in Firefox 12 to get hear the exact clicks that were originally intended in the product ;?j
Feel free to ask any questions or suggest any changes. As @danso pointed out, this is the repo https://github.com/mrcoles/javascript-piano
It also seems like a lot of amateur t-shirt sites have tons of custom i <3 shirts.