adamcik
Joined 13 years ago
Karma
37
Submissions
22
Member since
Jul 27
Recent submissions
Comment · 1 year ago
A friend of mine would always put `<blink>` around his middle name as a quick and dirty way to test for missing escaping and possible xss. Back in the day this was surprisingly effective at uncovering problems :-)
Comment · 2 years ago
A friend of mine recently let the domain used for documentation of Pykka, a Python actor library, expire. Some of course registered the domain, resurected the content and injected ads/spam/SEO junk.
Since the documentation is Apache License 2.0 there isn't much one can do, other than complain to the hosting about misuse of the project name/branding. But so far we haven't heard back from the hosting provider's abuse contact point (https://github.com/jodal/pykka/issues/216 if anyone is interested).
Comment · 4 years ago
The plan for mopidy-spotify was to move towards web-api for everything we could to be on the official APIs where possible. So the end state would have been only streaming left on libspotify, then figure out how to get librespot and GStreamer to play well enough together (there is a plugin but it's missing at least one feature we need).
But as you can see in issue #110 this goal hasn't been reached yet.
Comment · 4 years ago
The way auth tokens are setup for Mopidy-Spotify you hold the encryption key for the blob with the OAuth data, and the intermediate server just has an id and the encrypted data. Note that the id is not a Spotify OAuth client-id but an internal one. This is done so we don't have to ship Mopidy-Spotify with the client-secret for the App registration (this was pre PKCE auth).
I.e. I would be highly surprised if our OAuth integration was the source for this issue, but I'm obviously biased as the author of https://github.com/adamcik/oauthclientbridge
As for libspotify, there you had to put in a (device) password and username, so if something scraped that config I guess all bets are off...
Comment · 5 years ago
I wonder how much of this is free trial abuse like https://therecord.media/crypto-mining-gangs-are-running-amok... and how much was real trials?
Comment · 6 years ago
Having gotten a Swiss C-permit (permanent residency) myself on the five year fast track it was rather easy. But looking at previous interactions it all feels very dependent on what privilege you have in the form of your nationality.
If you are from a "good" country things are a lot easier. E.g. I didn't have the TELC B1 test done when I sent in all the papers. So I had a co-worker help write a formal letter explaining I would forward the test results when ready and got the permit before the results.
There is even a set of countries that are exempt from the language requirement (Austria, Belgium, Denmark, France, Germany, Italy, Netherlands, Portugal, Spain, Greece, and Liechtenstein). Some of which make sense as they share a language with Switzerland while others I wonder what the story really is...
In contrast, friends from a "bad" country would be stringed along on 6 month L-permits, also for the spouse (who didn't get the right to work) while I brought my partner (we still aren't married) and got her a B-permit that could easily be upgraded to a working visa from the get go.
I wish the system wasn't so discriminatory :(
Comment · 7 years ago
Correct, it's basically pre-cut parchment paper.
The thing to watch out for though is that the parchment paper is not suited for baking (mainly thinner and cheaper), we once baked a pizza on the matpakke type and it was a pain to get the paper off the crust.
Comment · 9 years ago
Note that the tool does not seem to filter out revoked keys, or take expiration into account. You have to cross check against what (sub)keys you still have in use.
Comment · 10 years ago
It's a Swedish word for fast, https://en.wiktionary.org/wiki/snabb
Comment · 12 years ago
I actually had a lot of luck creating such a timetable website[0] for NTNU in Trondheim, Norway. Initial version did hacky scraping, eventually I found a database, after the site site gained traction the IME Faculty (IT, Maths, Electrical engineering) got in touch about the site.
At this point they actually paid me to opensource the code and hired me to setup a copy for them. We never got their version to take off, as mine was to well established. So eventually we shut their instance down, and mine lives happily on despite the fact that I've long since left the university.
IME also did some great follow up putting quite a bit of effort in creating an API for "me". The problem was that the central IT services could only provide payed access to their WSDL based XML service. So IME basically payed them for access and then reexported it with their own API[1] + caching.
On a side note, most of the code[2], except for the importers should be generic enough to use at other schools :-)
[0]: http://ntnu.1024.no/ or http://ntnu.1024.no/2014/fall/adamcik/35/ for a sample timetable
Comment · 12 years ago
Note that there is also Soundcloud support for mopidy, among other extensions:
http://docs.mopidy.com/en/latest/ext/external/#mopidy-soundc...
Comment · 12 years ago
Streaming is only available through libspotify or the beta SDK on IOS. Rumors from #spotify on freenode indicate that the SDK for other platforms is still being worked on. But once it ships it will provide a minimal lib for streaming and the web API will do everything else.
Comment · 12 years ago
Same conclusion we also had in https://github.com/mopidy/pyspotify/issues/139 when looking at if we should move away from libspotify in favor of the new web API. For now I would stick with libspotify wrappers until a more complete version of the API comes out.
Comment · 12 years ago
Populate a http://developer.echonest.com/docs/v4/tasteprofile.html with the listening history and you can use it for dynamic playlisting using the spotify catalog. That is as long as echonest matches the song metadata to an id.
http://static.echonest.com/enspex/web/ChillRadio/ linked from the demos shows this for artists as a seed, but tasteprofiles as the station seed works nicely as well :-)
Comment · 12 years ago
This idea keeps coming up and I believe mopidy is perfect for building such a system (of course I am biased as one of the main contributors).
The way to go about building this with mopidy is essentially one of the following:
- Create the voting system based on the MPD protocol to talk to mopidy
- Create the voting system using our JSON-RPC websocket access to the core APIs.
- Create a frontend in python with full access to the core APIs.
Each of these of course have it's advantages and disadvantages. But to me one of our main strengths is the architecture we've designed over time and how people can use mopidy almost like a framework for exposing the media server in a novel way.