Oh.. ha, gotcha. Thanks for explaining. Incidentally, glad uuid's computed on the fly (as opposed to pre-computed) as I think the site would require a very (impossibly?) large database.
Creator of Radiant Player here. Performance and memory issues were a problem in the past and unfortunately have resurfaced in the latest release (1.4.0), but I am looking into them!
I can understand how this might be legally contentious, but the only thing it could be reported for is the name, I would think? The Google Play logo there is not me embedding it into the app, since it's displaying the webpage itself. Correct me if I'm wrong?
You want to avoid making it look like it's actually "endorsed" by Google, or a product of Google's, despite interop with one of Google's products. The name can be an issue here, so you might want to come up with something spiffier and original, and point out that it works with Google's service elsewhere.
If it doesn't let you launch, you may need to find the app in Finder and open it from the right click menu. Seems that OS X requires you to do this so that it knows you explicitly want to launch it. It remembers this after the first launch so you can use it normally afterwards.
Thanks! When I initially forked the repository, I hadn't planned on including features like the theme or the notifications, but once I realized how much I liked the product and wanted to continue to develop it, I figured I should ask the original creator for permission to keep the fork independent and he agreed. Very generous of him!
Outside of implementing the notifications this offers nothing for me that the original one, from James Fator, doesn't already do. I dislike the table display and the attempt at making the appearance be more Cocoa-esque in favor of the Google web design. You might also want to think of changing the app name and icon also as it is misleading.
Does Last.fm support mean just scrobbling, or are there other features you might like? I'm not a Last.fm user but I'd be willing to take a look into including support down the road!
Last.fm scrobbling was the first thing I looked for as well. It's pretty much a necessity for me at this point that any software-based music player I use needs to support last.fm scrobbling. There's several Chrome extensions that take care of it for the in-browser player as people below have mentioned.
I just fired this up, it looks and works great! If you did implement last.fm scrobbling (currently I just use a tampermonkey script that works well) I'd start using it primarily.
I had this same textbook for the Crypto course I just completed this semester. It's a very good textbook, in my opinion, as the descriptions and examples are really informative. Usually if I couldn't get the material through my professor's lectures, it was sufficient to look it up in the book. However, we did only briefly touch on cryptographic hashes and only a little on Legendre and Jacobi symbols, and not at all on the elliptic curve and other special topics towards the end of the text, so I can't comment on those.
The book does very good job of talking about different algorithms and concepts, often times with a very brief historical introduction, and includes thorough descriptions of various popular/important attacks of those concepts. In general it's a book I'd recommend for an introduction to cryptography. You also learn a fair introductory bit of number theory which I really enjoyed.
I also met Dr. Washington, one of the co-authors of this book, who was a very pleasant and energetic person who really enjoys the topic of cryptography.
Thanks everyone for their reviews. Glad to hear this isn't a POS text.
I'm taking this at Millersville University as a once-a-week, 3 hour evening course. I'm a Physics and CS major, and am taking it as an elective to get a Math minor.
With all the NSA and crypto news these days, it sounds like a great time to learn about the fundamentals of crypto. And I'm curious if there will be actual programming involved because to my knowledge, there aren't any prereqs for it, not even an intro to programming course.
I can see the benefits of using @extend to clean up the HTML, but wouldn't this pull the .container, .row, .span*, etc. CSS rules into each and every rule that extend from those? Wouldn't that have a hit on performance and file size?
I'm not sure how LESS handles it, but it adds your class to the selectors for that ruleset. If you do .myclass { @extend .container; }, you end up with .container, .myclass { // container styles }. It only adds minimal overhead.