k3d3

I think they'd have to use a different base board - the C2 uses an Amlogic S905, which as far as I know doesn't support USB3.

> For example, using it sleep tracking, or for waking you via vibration (as not to disturb your partner)

Yes, the pebble is great for that.

> or even just allowing your phone to detect that you're asleep so it can turn on do-not-disturb.

Wouldn't it just be able to detect that if you plug it in at night?

It's not an increase in obscurity though: https://github.com/WebAssembly/design/blob/master/TextFormat...

The format is intentionally being built in a way that you can look at the source, in the same way you would look at minified Javascript currently.

If you're worried about obscurity, look at what is generated by asm.js. WebAssembly won't be any worse than that (and is, in fact, more or less a more efficient/correct equivalent to asm.js).

SQRL relies on phone cameras and QR codes, for one

Why would you make all of your commit messages "1", instead of explaining what the added code does in each?

You can already use TLS client certificates - the UI is just terrible is all.

The problem with hashes of hashes is now instead of the password being directly grabbed, the hash is directly grabbed, which can be thrown through the challenge-response system with no problem.

This only mitigates knowing the password itself, not anything to do with authentication.

You might find interest in https://hacks.mozilla.org/2015/09/subresource-integrity-in-f...

It mitigates passive MITM attacks, for one.

On the other hand, there's nothing that's made _worse_ by choosing to do it that way. Plenty of things that are the same, some things better, but nothing worse.

Mozilla Persona / BrowserID might be of interest to you.

Which is then going beyond just using scrypt on the client. What you explain is simply challenge-response authentication.

If you use netstrings, why not take it a step further and just use bencoding?

IM has ruined me, so I think of it as "yur" (as in ur being a shortened "your")

Sorry to say, but if the source is not available for a crypto tool, it's probably not worth looking at.

Best of luck though.

Actually he was asking about both

And then after that they'll rename it to Firefox

> Essentially, the site uses JavaScript for showing images without providing any advantage to either the user or the site.

That is a very baseless and false conclusion.

To be fair, I'd hardly say that not knowing what a monad is = not knowing anything about FP.

Yep, exactly. Also it's nice to have the extra privacy, especially when linking to images privately amongst friends

Nobody else has been able to reproduce it, and you haven't given enough information on what you're doing or what you've tried. Have you tried different machines? Different browsers? Have you tried pressing the various buttons in the UI? What kind of machine do you have? Do you have a very small amount of RAM? Et cetera.

You might say your browser works fine, but I'd put my money on something there being the issue.

> impossible to view the image in a new tab seperately

But it's entirely possible, and there's even a dedicated button to view just the image. ("View in Browser").

Make sure your browser is functioning properly - this isn't an issue with the website.

Works fine for me. Make sure your browser is functioning properly.

This website works in every browser I've used, and I've never heard of any problem even remotely close to what you say you're running into.

> that the site is almost unusable.

The site is perfectly usable. More than usable, even, because I get RES-style zooming for free, amongst other things.

You can right-click save normally already - just right-click and save. If you want the browser zoom tools, hit the "View in Browser" button or right-click and open in new tab

Works fine for me

That doesn't make it okay

The decryption is done in a web worker, not the UI thread. That shouldn't be the cause.

We're actually not sure what most people use (apart from ShareX) for uploading images, but we're looking to implement functionality into new clients to support Up1 for sure.

That would be awesome! If you run into any trouble, be sure to hit us up in the IRC or throw an issue on Github.

That's true. It's also open source, unlike MEGA.nz.

Currently the upload size max is 50MB.

There were no plans to password protect images, but that's a good idea! For now, the post key itself (after the # in the URL) somewhat acts as a password.

Try uploading images and things to https://up1.ca/

Also be sure to check out ShareX at https://github.com/Upload/ShareX , a popular screen-shot tool adapted to work with Up1.

Contributions to the code are always welcome, and we hope you enjoy!