Hacker Newsnew | past | comments | ask | show | jobs | submit | modemuser's commentslogin

Good to see Sarah mentioned here, it's the same for me. Her music is the one constantly good thing that I'm always looking forward to in the last year, highly recommended.


The only fully functional crypto I know that could make Bitcoin obsolete is Nano. It does one thing, and does it well. Fast, feeless, green.


But they don't know which half!


They know if you have a Y chromosome, so they know which half.


SEEKING WORK - Cologne/Germany or Remote

I'm an experienced full-stack developer, working mainly on

    - backend (Python: Werkzeug, Flask, Django; PHP5; Postgres, MongoDB, Redis...),
but also

    - frontend (jquery, angular.js, HTML5, CSS3, responsive design),
    - real-world interaction (Tinkerforge, Arduino),
    - mobile (Android),
    - desktop (Java, Python)
I've build Restful APIs, crawler, single-page apps, mobile apps, desktop apps, dashboards, CRM tools, deployed CMSs, admin'd servers/cloud instances.

If you need help with something not listed, I can probably pick it up quite fast.

Don't hesitate to contact me, I'm sure I can figure out how to help.

thomas@misera.org

Some of my private projects: http://misera.org/#projects


The metareddit monitor doesn't search through an index. It's a crawler that constantly fetches all new comments and submissions and looks for the (several thousand) keywords in each of them.

Source: I run metareddit.


> HTTP 1.0

If that is the only problem, flipping one bit in every response seems like a really simple solution. Why hasn't Cloudfront fixed it yet, do they know about this?


Yes they know about it. Below is the response from Amazon. The logic they employ is that since it is broken in an old version of Squid, it is fine for it to be broken on Cloudfront.

https://forums.aws.amazon.com/thread.jspa?messageID=351384&#...

- - -

Hello,

While we are aware of the issue with range request HTTP/1.0 206 responses and Chrome, we cannot provide an ETA for a fix. Since this issue is specific to range requests, an immediate workaround is to disable range requests on your origin server if this is possible for your use case.

It is also worth mentioning that multiple web proxy and cache application vendors have using HTTP/1.0 as a de facto standard for many years, so you will probably sporadically get similar reports from your end users using Chrome, but not other browsers such as Firefox or Safari. For example, here is a discussion between a Chrome developer on the mailing list for the popular Squid web cache about a similar report: http://www.squid-cache.org/mail-archive/squid-dev/201204/011... I am not saying that always returning HTTP/1.0 will stick around forever, but it is fairly common in real world situations today.


Some criticism and suggestions, in no particular order:

- If I click in the main search field when there is already something in there, my input disappears.

- What is the Ti column in the playlist? If it is the play time then there is something broken: I see 388, 0:0, 4:6, among sensible times.

- The playlist is seems non-interactive, I found double-click and drag-and-drop functionality by accident.

- The player controls are missing, took me a while to see them on the bottom of the screen.

- No full screen for video.

- The on/off button in the corner needs at least a label.

- The menu items About and Contact don't change the cursor to a pointer.

- The sidebar with explanations disappeared after a reload.

- All sorts of misalignments and layout oddities, like height of the playlist, see this screenshot http://i.imgur.com/Sy8RP.png

- Clicking two separate "add to playlist" links for to albums, the individual tracks are intermixed, also some track numbers are duplicated.

PS: I wrote this comment hours ago, could only submit it now.


Thanks for the feedback. And yeah TI stands for track length. The others will be added. Thanks!


I am affiliated with one of the sites JDownloader supports, and they certainly did not ask us for approval. Whatever you try to stop them is futile, since they can react quickly.

JDownloader breaks our business model since we don't have premium accounts, but in the end you have no other choice but to accept that some people are leechers.

So, please don't think you're doing good when using tools like that and advocating their use.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: