tilgovi

8 ms·

1.
by tilgovi 14y ago
Here you are talking sense.
2.
by tilgovi 14y ago
Except you're the one who brought up $200k as a number to begin with. And those people who sold themselves into debt slavery, by going to an extremely good school, may actually still hold jobs that will allow them to repay their loans even
3.
by tilgovi 14y ago
Hahahaha. I've totally posted my response to a recruiter on FB before, because I had to vent about it. He nails every important point, including that we should have some sympathy because they are incentivized, at least in the short term, t
4.
by tilgovi 14y ago
Nice! I didn't realize so much had been done on dataprotocols.org yet!
5.
by tilgovi 14y ago
PouchDB is ready for some testing and play. Dale Harvey has put a lot of work into it recently: https://github.com/daleharvey/pouchdb I'll see what I can do about getting a good publication of the replication protocol. People have been as
6.
by tilgovi 15y ago
I started thinking about the dictionary attacks, too, and ultimately you're right. Not worth enforcing and easy dropdown changing is eventually what we want. Thanks for your thoughts.
7.
by tilgovi 15y ago
Yes. I totally agree. I would certainly love to support multiple distinct personas. There is an open question of how to do that while mitigating the damage potential. There are also cases where multiple personas might usefully be linked. F
8.
by tilgovi 15y ago
Thanks! Wherever possible I'd like to ditch the personal information after signup and just keep a hash or something that we can use to prevent multiple accounts using the same Twitter, OpenID, etc, linking only these opaque tokens to user I
9.
by tilgovi 15y ago
I think Jon was just trying to provide some information on the spectrum of possible identity solutions one can choose from. At Hypothes.is, it's extremely unlikely we would try to do anything like this. However, it does represent a form of
10.
by tilgovi 15y ago
We're not trying to compete for attention in the social web. Part of that is reflected in our involvement with the W3C Open Annotation Working Group ( http://www.w3.org/community/openannotation/ ). While Hypothes.is may be one place to publ
11.
by tilgovi 15y ago
Quite the opposite, actually. I will be seriously considering the privacy implications of everything we do. One of our core principles is a commitment to pseudonymous accounts. To the extent we allow multiple identities to be linked to one
12.
by tilgovi 15y ago
I should add we have a low-volume list for outgoing announcements if you'd rather just hear those: announce+subscribe@list.hypothes.is
13.
by tilgovi 15y ago
Thanks, zerostar07! If you're interesting in helping out, watch https://github.com/hypothesis or subscribe to our dev list with dev+subscribe@list.hypothes.is
14.
by tilgovi 15y ago
That's only true under the assumption that popularity is the only factor in visibility. On hacker news that's not even true entirely because there's a temporal factor: new postings remain visible for at least a short time. However, there ma
15.
by tilgovi 15y ago
My understanding is that attempts will be made to algorithmically promote diversity and to reward/punish social behaviors in such as way as to discourage discursive protectionism.
16.
Hypothes.is: Taking peer review to the Internet(kickstarter.com)
46 points by tilgovi 15y ago|12 comments
17.
by tilgovi 15y ago
XMPP MUC is not fun, nor fun to scale. IRC has netsplits, but it does work reliably for tons of people all day every day.
18.
by tilgovi 15y ago
Do it.
19.
by tilgovi 15y ago
I think this is coroutines under the hood?
20.
by tilgovi 15y ago
Not necessarily. A callback function with the standard signature under the hood is implied. If the author is controlling flow into and out of these execution contexts there is no reason an error passed to the implicit callback cannot cause
21.
by tilgovi 15y ago
There's room for improvement. Most programmers shouldn't need to know how to write asynchronous code just as they shouldn't need to know how to write concurrent code. Consider mutexes vs Java's 'sychronized' vs transactional memory: there's
22.
by tilgovi 15y ago
node-fibers is one attempt to put coroutines into node. I like it because it uses libcoro, which is nice and tight and uses ucontext, and because it works as a module without forking the core of node. Once you've 'fiberized' the server modu
23.
by tilgovi 15y ago
The thing to hope for is the death of the terminology and the proliferation, not consolidation, of technologies. Saying that all these diverse storage systems are all "NoSQL" and there will eventually be a "winner" is like saying that there
24.
by tilgovi 15y ago
The problem doesn't come with the inserts, it comes with the deletes, where CouchDB will keep some metadata and stubs around to support its replication use cases. In a pure logging setup this is perhaps less than ideal.
25.
by tilgovi 15y ago
HBase might be a good solution, too, but I don't know a whole lot about it. CouchDB would work fine but you'd want to add some operational automation and a proxy to roll over between temporary databases since deleting old logs from a single
26.
by tilgovi 15y ago
I'd love to see a ctypes binding into Python of LevelDB, also. Anyone working on that?
27.
by tilgovi 15y ago
Also, the version on master does what you suggest and makes no attempt to accommodate replication-based merging, thereby dealing implicitly with merging revision histories stemmed to a height of 2. "Real" CouchDB replication is what we aim
28.
by tilgovi 15y ago
I'm the one working on this right now and this is exactly what I'm doing. However, old document bodies are not the only way to store history. Documents have a revision history, possibly 'stemmed' to a maximum height, which is an array that
29.
by tilgovi 16y ago
As though the gender of the agent had any relevance...
30.
by tilgovi 16y ago
Woohoo! I'll come by :)

More ›