tOkeshu

7 ms·

1.
by tOkeshu 12y ago
Well it's called Remote Storage [1] but I guess we can't expect companies like Google, Apple, Amazon or DropBox to actually embrace that, isnt it? [1] http://remotestorage.io/
2.
by tOkeshu 12y ago
I generally find that using tuples of booleans this way is (sometimes) blurring the intent. Indeed, not only you have to keep in mind which boolean value correspond to which variable, but you also have to not forget what's the meaning
3.
by tOkeshu 13y ago
Some people try to address this issue in Europe and especially in France. I strongly recommend anyone interested to take a look at the DIY ISP project [1]. There is also a map [2] showing existing initiatives and a previous thread on HN [3]
4.
by tOkeshu 13y ago
> This is a solved problem. There is strong technical obstacles but yes the problem is more or less solved in different ways. The point of Randall Munroe here is to emphasis the gap between the fact the Internet made possible a lot of in
5.
by tOkeshu 13y ago
It is way more complicated than that. WebRTC is all great and shiny but there is strong obstacles to build correct data transfer applications on top of that: - You still need a server to do the "signaling" part - NAT are everywher
6.
by tOkeshu 13y ago
Dropbox has a storage limit, requires an account and is non free software. The usage proposed here is a "no-strings" attached approach. Ideally you want something you can trust, hence free software, and that does not store anythin
7.
by tOkeshu 13y ago
It's a really geeky approach. The 949 problem concerns a lot of persons who does not even know what a server is.
8.
by tOkeshu 13y ago
Do not forget that this solution is inherently mono-threaded and does not benefits from a proper concurrency model like node.js for example (which is also mono-threaded by "design" but provide non blocking IO). So for big files wi
9.
by tOkeshu 14y ago
Yes Fountain Codes are definitively something I have to look at. Improving bandwidth usage and resuming downloads are part of the next improvements with https. For now Erlang have been an excellent fellow to deal with these things :)
10.
by tOkeshu 14y ago
Theses files are examples files. You can find the same in the cowboy_examples repository[1] (Cowboy is the erlang server I use to build the application). I should remove these files as the application do not use them. For your information,
11.
Fixing the 949 problem with Fipes(monkeypatch.me)
11 points by tOkeshu 14y ago|4 comments