HNHacker News
TopNewBestAskShowJobs

meejah

39 karma · joined February 27, 2015

https://meejah.ca
submissionscomments
meejah··on Localsend: Open-Source Airdrop Alternative
It is compatible, you just have to configure the other client to use the same servers.

For example, to use the "wormhole" Python CLI with Destiny, you can do this:

wormhole --relay-url wss://mailbox.mw.leastauthority.com/v1 --transit-helper tcp:relay.mw.leastauthority.com:4001 send README.rst

Then, the code it prints out can be consumed by a Destiny (or https://winden.app ) client.

meejah··on The Haskell job market has been growing steaily since 2008
I would personally keep "pair programming" at the top of the list, this _really_ helps everyone learn.

Even more importantly, it tightens the loop between "write code, review code, change code, merge it finally" since you're basically doing all of that "at once" in the best case.

meejah··on Wormhole-crypto: Streaming encryption based on Encrypted Content-Encoding
It sounds like you're suggesting that magic-wormhole only wishes to provide end-to-end encryption to "abnormal" people. I don't believe that's true and there already exist implementations of the open magic-wormhole protocol in several languages.

The original magic-wormhole project is at least 6 years old. How did you determine its goals?

FWIW, I agree with other comments that you've chosen a confusingly-similar name (and that's unfortunate).

meejah··on PrivateStorage.io: A secure and privacy-focused cloud storage solution
I don't know the exact answer to that, but "not much" in comparison to the time to send the bytes over the network. The actual contents are encrypted using AES which often has built-in instructions on modern processors and is thus very fast. The vast majority of the time is uploading time here.

Tahoe does use "convergent encryption" (basically, the key is based on the contents) so that the same file encrypted by the same client results in the same ciphertext (and thus, doesn't need to be re-uploaded).

I believe that only happens at the "capability" (i.e. file) level, though, not each chunk. So, if you had a directory of 10 files each 100MB and changed one, you'd only have to upload the new directory-descriptor and the one changed file -- but if you change a few bytes of a 1GB file, you'd have to upload all the ciphertext for that file again.

meejah··on PrivateStorage.io: A secure and privacy-focused cloud storage solution
Sure, yes you could do that -- I mean, PrivateStorage is just shipping you a "real actual Tahoe client". The main feature you're getting is the managed storage-servers.

So if you happened to "not completely trust" the availability of those you could also configure one of your own and configure your client(s) to use that and the PrivateStorage servers. That is, hedging against PrivateStorage going away so suddenly you can't retrieve your data.

But, I agree: if you're doing that you're likely able to run your own Tahoe grid on VPSes or similar.

meejah··on PrivateStorage.io: A secure and privacy-focused cloud storage solution
In the PrivateStorage case the machines aren't "trusted" but they are all run by the service you're paying for -- so the incentive to keep them running properly is indeed there.

For other kinds of Tahoe deployments, no there's nothing built-in to incentivize storage-server operators. That part is up to whomever is organizing and running the Grid (what Tahoe calls a group of storage-servers). For example, friends could agree to host storage-servers for each other and create redundancy + trust that way.

The difference between Tahoe and things like Storj / FileCoin is that those services intend to be "a single, global service" whereas Tahoe is software that can be deployed in several different ways -- one of which is a professionally managed Grid such as PrivateStorage.

If you are interested in these topics I'd encourage you to join #tahoe-lafs on Freenode or one of the Tahoe development meetings. These are definitely things I've seen discussed but I think Tahoe-LAFS is far more likely to introduce a concept of "federated Grids" rather than "a single global Tahoe service".

meejah··on PrivateStorage.io: A secure and privacy-focused cloud storage solution
An expert could figure out how to get the PrivateStorage Tahoe client to use other storage servers, but yes in general it is "a managed service" and I don't think using your own storage-servers will be "a supported configuration".
meejah··on PrivateStorage.io: A secure and privacy-focused cloud storage solution
Tahoe-LAFS does "erasure coding" on the chunks of data. This increases the size of the data (adding redundancy) so that you can recover a file without recovering every single chunk. These parameters are decided client-side. In the smallest possible case (i.e. every chunk required) there is some slight overhead from the zfec and Tahoe headers.

If you are using redundancy of any kind, it will inflate the size of the ciphertext versus the plaintext thus affecting sync speed.

Tahoe-LAFS does split everything up into fixed-size chunks, though, so the total size of the file doesn't really matter -- it will still be uploaded in 128kb (default) chunks to the storage servers.

So, it's not the encryption that has an impact but the erasure-coding (which gives the "RAID-like" features) and you can configure it to have zero redundancy and thus only some slight increase in the total amount of data to send.

meejah··on PrivateStorage.io: A secure and privacy-focused cloud storage solution
Tahoe-LAFS by itself is probably not (you do have to configure and keep some Python-based daemon software running), but PrivateStorage is a managed service.
meejah··on It appears my Google account is slated for deletion
I don't believe OnionShare uses txtorcon at all, actually. And I wrote txtorcon, not Micah ;) but they're both decent options for publishing depending on your use-cases.
meejah··on Magic-Wormhole – Get things from one computer to another, safely
It is the PGP Word List: https://en.wikipedia.org/wiki/PGP_Words
meejah··on Magic-Wormhole – Get things from one computer to another, safely
The codes have a small number in front; these are the requests. So if the server did allow 65k requests, each one would be a different number. You can guess once per request.

Yes, an attacker can denial-of-service by guessing once on all the (possible) requests. There is some work towards stopping this sort of behavior (see e.g. https://github.com/warner/magic-wormhole/issues/126)

meejah··on Magic-Wormhole – Get things from one computer to another, safely
The attacker still just gets 1 guess per wormhole / send request. Each send-request / wormhole is its own separate thing.
meejah··on Magic-Wormhole – Get things from one computer to another, safely
Any attacker only gets a single guess
meejah··on Working fewer hours would make us more productive
I think these types of studies are all going to be fatally flawed with a bunch of very-hard-to-untangle factors: since "40 hours" (or more) is the "expected norm" then if you're working less you've either fought incredibly hard to do so (which I personally have), you have way more freedom to choose working hours than most people or you're "forced" to work less (or more) for some reason.

e.g. my first thought about the "increased hypertension in workers reporting < 7 hours" (a paper I haven't read, mind) is that they're stressed about finances because they're working part-time (or the "hours" was averaged over the year or something, and they spent some time without a job).

Now, if you've chosen to work many more hours then it seems intuitively obvious that you'll be more productive. There's also the hard-to-study factor of what you're working on. For example, many free-software developers are doing their free-software-developing in their "non-work" hours -- so they might be "working" (in the sense of producing code) 80+ hours a week, but will likely only get "counted" as whatever their day job was. (If there are studies that account for "what you do with your other time" against productivity, I'd be very keen to read them).

In a similar vein -- and as John said in the original post -- if you're "stuck" on something (e.g. can't do any more "design the hard algorithm" thinking) and switch to something "boring" that still needs to be done (e.g. make the Makefile suck less) that's still "more productive". But, as others have pointed out, many developers don't have that freedom -- they have to keep pounding their face against whatever bug they got assigned. And if you're stuck, but have to keep working on it, I'd bet a lot that your productivity goes to shit.

So, all that said, I personally believe (note: not scientific! ;) that we'd be far better off to have shorter expected/forced "working weeks". And I don't mean that everyone should be forced to work less! This may (or may not!) have a "productivity" impact for employers but if you looked at individuals' "productivity" (including work and "non-work" parts) I think it would go way up -- precisely because this would give the vast majority of people way more choice about what they get to work on. This -- I completely unscientifically presume -- would also have a large positive effect on people's reported happiness.

That is, they'd be spending less time smashing their face on that bug at work and get more time to do whatever else they like to do -- free-software, painting, writing, building things, etc.

In any case, I know that for me personally being forced to work 40+ hours a week on the same thing is completely toxic to my creativity and productivity at programming and I've worked very hard to get paid less (to work less). I can also tell you that nearly every co-worker or friend I've told of my myriad different arrangements to achieve this have wanted to do the same (but feel they "can't"). The only exception seems to be when people realize the bit about "paid less" ;) and can't do (or don't want) that. Interestingly, I still have spent a bunch of my increased leisure time writing software -- but for myself, or free-software instead of "for work". Of course, I've also spent a bunch of it doing things for pure enjoyment.

Now, of course, that's all just anecdotal. But, for me, less "must work on X for $" time means a lot more happiness and a lot more "productivity" (if you look at everything I do with my time).

meejah··on Code Review Best Practices
I have, and it was more an attitude/cultural thing: the reviewee took any criticism very personally, and was hence super defensive and unlikely to change anything anyway.

Honestly, I think it's actually really, really hard not to react that way (to varying degrees) especially as most code-reviews basically come at the wrong time: you've already written the code, it works, it has glorious unit-tests -- who cares if it's a for vs while loop or whatever. It's actually even worse if there are serious design or maintainability issues, as that's even more code to re-write/"fix".

Personally, I really like having code-reviews -- it's better to get rid of serious problems if they're there. However, I've found a lot of reviews to be rather worthless "rubber-stamp" exercises -- especially if the dev team has just been told Thou Shalt Do Code Reviews Because Reasons! (I've also found the opposite, for sure: getting nice solid advice or missed cases; but these are invariably with other developers who want reviews no matter what management said).

...but all that said, I think so-called "code reviews" really work best if they're spread out over the coding (unless it's really small chunks at a time) -- a bit of pair-programming (or "hey, can you help me with ...") and design (or whatever you call "early on in the cycle") reviews make it a hell of a lot easier to take a different approach.

I think they used to call this "collaboration"?

Companies that just blast out a "new rule: everything gets code reviews!" memo without helping people understand the benefits, and how to do more "along-the-way" validation of design, refactorings, etcetc are always the very worst at having code reviews that are in any way effective. At such places, I find "code reviews" devolve into either useless "rubber stamp" affairs or something like what you describe. Or worse.

Also, if you have "Junior Developers" blasting out code for a couple days (or more!) with no adult supervision with a hope that some last-second "code review" procedure is going to equal amazing code, you're doing mentoring wrong. It's a lot nicer for everyone involved if there is someone sitting down with (or chatting or watching-the-commits-of or whatever works) the less experienced developers. These mentors should be providing hands-on, practical advice as they go. Some devs might need more hand-holding, some will need "a plan", maybe you need to sketch out classes or method-signatures for them, perhaps they need a bunch of half-day tasks written down, etc...Such mentoring should, IMO, be what your Senior Developers are spending a decent chunk of their not-coding time on.

meejah··on Josh Tetrick's food revolution: saving the world one egg at a time
Yeah, the answer to "commercial mass-produced eggs waste resources" isn't "let's use mass-produced X instead!"

...it's more along the lines of what you suggest: preferring locally-produced eggs from smaller producers. Preferably organic, free-range, etc. Certainly more expensive in "dollars", but ...

meejah··on The Terrible Technical Interview
Do you ask to see the resumes of candidates?
meejah··on Limitations of the GET method in HTTP
...and in fact, there's a popular use-case called "using memcached" that does have side-effects. That is, doing a GET on something absolutely changes the server "state" (in the sense that memcached might have a key added to it) but that should be invisible to the user.

Of course, it's not actually-invisible: their next request might be a little bit faster.

← PreviousPage 2 of 2