Oh, I didn't mean to imply that megaupload were the "inventors" of sharing incentives, but their takedown has greatly marginalized this... noble practice.

I hoped Mega (the co.nz one) would rekindle it, but they chickened out and dropped the incentive model

Now I'm watching megareload carefully.

In its infancy, cryptocat was a js-crypto thing.

This has caused quite heated discussions, among which was this article:
http://www.matasano.com/articles/javascript-cryptography/

Basically, js-crypto is unreliable. This caused cryptocat to move to plugin model.

Actually, plugins (when open-source) are more reliable than both applets and js-crypto.

JS crypto is both rather unreliable and hard to audit (I don't know if attacker has compromised your server and is sending out hostile javascript or something like that)

Applets are somewhat better (at least the damn things are signed), but even if they are open-sourced, I can't be totally certain that your signing keys and server haven't been compromised (causing a properly-signed yet malicious applet to be distributed).

However, I have to admit, that it is unlikely someone will go through the trouble of rooting your servers AND taking over your keys just to screw over a file locker (admittedly, a cheeky one but still)

Now, if I have installed an open source plugin, I can be certain that (assuming the plugin has no auto-update functionality) as long as the version I installed is "legit", there is no way to "switch it over" to something malicious from your side.
Browser plugins (if done right, mind you ) are thus the best way to get some semblance of a secure environment.



Well, they are more like "mega" and "megaupload" cross-breed, it seems.

What I like here is that the incentive business model (which Kim sadly dropped) is coming back. I adore incentive-based file sharing, it really rubs MAFIAA the wrong way

Folks, I'm glad you're alive.

I kinda wrote you off (but had a google alert configured to watch for megareload.se stuff anyway)

Glad the "incentive" thing is coming back (off course, I will only use it to earn bitcoins on legal files uh-huh )

Things I think you need:

Folder-based uploading (not as in "upload this folder" but as in "upload all files in this folder"). This will make uploading split files much easier. Of course, then you will need some clever way to reuse password for a folder's content.
I mean, it's fine and dandy to encrypt them all with same pw, I reckon, but I guess entering the password for every-single-f[bleep]ing file a gazillion of times will get on people's nerves. I suggest you add some kind of "reuse password from previous download" functionality to the applet (you can store key material on user's box so as not to compromise your security model... or keep it in memory... whatever. You're the code people, not me )

And you definitely need to significantly reduce storage time for free files that are unpopular (so as to force people to host totally legal popular files)

Also, you need open-source browser plugin a-la cryptocat.

I mean, sepukku is fine and dandy, but I think there's a whole body of thought that suggests that as far as crypto "reliability" goes it's "js crypto" < "applets" <"plugins"

Cryptocat does it the plugin way, you should too*

*I even promise not to have my BF excise advertising code out of the open-source plugin (then again, if boyfriends excising ads out of your plugin becomes an issue, you can make the plugin so that it only works for paid members)

Why not Tritecoin ? 

Anyway, congrats on your first altcoin, dude.

CPU mining friendly algos didn't play out as expected last time it was tried.

I've heard some IRC talks with people discussing whether it's even possible (consensus was an uncertain "maybe") but so far, no actual attempts.

I think it's just too early... Give it some time, someone will find a GPU/FPGA/ASIC hostile PoW

Well, so far it doesn't seem dead enough for my collection.

Bought a few anyway so that I have them when they finally die (if they do)

1) slightly faster transactions (to accommodate the needs of...... )

2) an ex-CPU friendly - now GPU friendly - POW (to accommodate all the GPU miners who are about to be pushed out of business)

3) A general sense of hope for those who failed to get on the bitcoin train in time (to accommodate all those who failed to get on the bitcoin train in time)

4)  

...

Well, I admit, technically, that makes 3, hence, "many"  


Which "these" "things" ?

being bitcoin's big and, as far as I can tell, not really necessary, backup tape ? That's some ambition, there

So far, it is basically a rather contrived and complicated block backup mechanism so you could counteract and/or recover from a "bad" reorg.

I am not convinced it would benefit anyone.

 


I am aware of those facts.

However, I believe you missed the part where I explicitly stated the qualifier "malicious".

Detecting a reorg is trivial. Determining whether it is an okay reorg or a "bad" reorg does not seem so.
I don't see why Litecoin is required here.

I mean, I realize that in this scenario, it is, essentially, a large backup tape.

But what exactly prevents BTC from, just, you know, keeping the reorged-away blocks for a little while longer and pleading the node operator to investigate "suspect" reorg when it occurs ?
Both solutions provide, essentially, the same functionality - block material is kept around for a while longer, so that human-op can decide which side of a fork he likes the best. But one requires mutual inter-operation between two cryptocurrency nets, while the other does not.

I, so far, fail to see the advantages to the "inter-operation" scenario beyond "let's give litecoin a sense of purpose" and "it would be a shame if GPU miners starve".

I would give you mine just out of the goodness of my heart, but I am in the business of collecting dead coins, and my heart has recently run out of goodness.

So, no.

Excuse me if I understand something wrong... I'm a girl who dabbles in Java, and some of it might be over my head, but if this were to be implemented, a "hard 51" would go like this:

1) attacker uses Superior ASICs to mine a private BTC chain forked from some point long since past (probably so as to make a double-spend)

2) attacker publishes chain

3) an unspecified mechanism detects that there is, well, a so-called "malicious reorg", and BTC enters "hide yo coins, hide yo wife mode" and starts relying on backup data embedded in Litecoin's chain

It seems to me that

a) it would be exceedingly hard to properly develop detection algorithms for "malicious reorg" detector

b) if you succeed at a) you don't need no litecoin, you just keep around the blocks being reorged away until you are convinced that reorg was "not malicious".

c) you can, of course, just halt everything and have community "heavy hitters" decide in IRC which part of the reorg was "good" instead of doing it with "and then a miracle occurs" automagical "malicious reorg" detector, but as long as you don't discard the blocks involved (which does not require litecoin) you don't really need litecoin in this process.



So, TLDR:
I do see theoretical benefit to this general line of thinking (the "let's detect bad reorgs" line of thinking

I doubt that "malicious" reorg detector that would activate a "hide yo coins" mode when a real attack occurs is attainable

I could see a "dumb" detector being used to facilitate a "consensus intervention" on part of humans who have nontrivial power over the network (pool ops and devs).

I do not quite see why you need litecoin in any such scheme, beyond "let's give this altcoin some semblance of purpose"

Do you know something about solidcoin that I do not ?

You get to "mine" proof-of-stake by holding-and-spending coins in a manner that maximizes their age.

In principle, the idea is rather good.

In this implementation - not so sure   

Yeah, Voices from Beyond the Veil are telling me that "continuous adjustment" is likely to end in tears.

Well, it had a rather poor proof-of-stake design, didn't it?

I want to use chatbox to try to find someone to sell me TBX coins.

Ain't working for me despite the fact I verified email

Any ideas why ?

No offense, but drupal is kinda heavy-duty for an exchange. Way too much overhead, unless you are very clever and skilled (at which point you hardly need drupal anymore)

Like I said in your other thread, it would be very nice of you to provide some kind of whitepaper, or even a mere "this is how our tech works" forum post.

Keeping people "intrigued" by your technological promise is an old and annoying marketing ploy.

Satoshi didn't start with "I have tech, but I won't show you it" publication.

Well, I am running a TBX client now, so...

Hi Markm 

BTW, I think I'll put a bit of hashrate on this thing so transactions can get through...