> Parse error: syntax error, unexpected '[' in /home/a2414827/public_html/config.php on line 21

This is a classic signature for an outdated PHP version that does not support the shorter array syntax format.

The ads are in an array so they can rotate.

There are very distinct differences between this concept and BitMessage. It uses different ways to ensure anonymity of metadata and retention.

For example, nodes only store relevant messages (to their hoster, users, etc), and hashes of messages they have seen (so they don't miss checking any messages) and an amount of random irrelevant messages for anonymity.

Just stop wasting people's time if you have nothing to talk about.

@DiamondCardz: Update your PHP version. If you're on shared hosting, ask them to upgrade / move you to a server that has the updated PHP version. Download the original script and it'll work, don't listen to the suggestions that will break the script.

The code did not work because DiamondCardz was running it on an outdated PHP version. Update to the latest PHP version and the original version will work.

Your suggestion does not throw an error, however it breaks the script and people will not get any rewards.

You do not quote NUMBERS with strings.

no r3wt wtf?

NOT like that. You do not put quotes around arrays. Have you written a single line of PHP code before?

Seriously, WTF?

It should be this:

$rewards = [1000, 1250, 1500, 1750, 2000];

$bannerAds = ["<iframe scrolling='no' style='border: 0; width: 468px; height: 60px;' src='http://coinurl.com/get.php?id=14179'></iframe>"];

WTF again.

What the fuck, is this CoinLab's forum account?

This isn't official

Nice job through

That will not happen. It might be maybe 1-3 years before, with the current difficulty adjustment it would not be practical for all the coins to be mined 8x faster?

No, you should play just-dice or wait for the sdice revamp

The draft

Users connect to nodes or run their own. Users do encryption and decryption locally, in their browser or computer.

Nodes pass encrypted messages between each other, store the relevant, and stream them to users

Node discover them through P2P means, as well as bootstrapping from IRC channels, dnsseeds, or anything really.

Identities

Users generate identities, just like bitcoin addresses, automatically with public private key crypgoraphy.

Identities have corresponding text representations and pictorial (eg randomart, colored pixels)

It would be very difficult for attackers to replace "I am [identity]" on numerous social networking websites, directories, blockchain timestamps, etc.

New identities would be generated and passed around with each message. Public identities are not used beyond an encrypted "identity swap".

Messages

Messages contain one from identity and an arbitrary amount of to addresses, a vague timestamp and arbitrary payload. They are identified by their hash.

The arbitrary payload may include details of the next identity to use (?)

Nodes will have their own policies on what they relay. Nodes probably will operate on a whitelisting level (unless there are better solutions)

Whitelisting will gravitate towards things such as identity swapping, solving CAPTCHAs, etc

------

MITM
If you post your public identity practically everywhere, it would be very difficult for an attacker to change them, especially if they are embeded in a blockchain like system.

From/to tracking
The software would automatically negotiate new identities through encrypted communications. If you run your own node, it would be very difficult to find out who you are talking to as your node will be passing messages rapidly

Spam
Nodes could operate on a fetch instead of push system, whereas only messages from specific identities chosen by the user are kept. Nodes may "whitelist" addresses that has completed proof of work (eg captcha). Nodes may trust other nodes in their whitelisting.

------

Example

Alice's public identity is towb0XgLHML1yyVBcYWn. This info is on a lot of directories, profiles and places.
Bob's public identity is likvMxGs0txShDuaSoXV. Both of the identities have completed "proof of work" of some sort and are recognized by nearly all of the network.

Alice and Bob runs their own nodes. Alice sends a message encrypted that only Bob can decrypt, and passes it around the network. The message contains a new identity. Alice and Bob's nodes may add these identity to "always keep messages".

Bob sees the message and replies with a message to Alice. The message may not contain an identity and may simply be gibberish that doesn't checksum. This makes it very difficult for people to determine if Alice is actually communicating with Bob. The software by default may occasionally send messages to random identities that it has heard activity from/to containing gibberish. A gibberish response is expected in that case.

Alice and Bob's nodes are constantly receiving a lot of irrelevant messages. They're all relayed to peers who don't have them, while the nodes only store the hash (possibly in bloom filter) to reply with "HAVE" when another node asks "GOT [hash]?"

Bob's software sends gibberish (does not match checksum) to a random identity it has observed mail from. It is customary for that selected identity to also reply with an encrypted message, which turns out to be gibberish too.

Alice now communicates another message from a new identity, to Bob's new identity. This may or may not include another new identity. Of course, there is the encrypted message, which could be text, could be image, could be a file, although large messages may be difficult to get relayed.

coinchat.org

coinlenders.com

inputs.io

Decentralized is a must. Don't focus on making your own alt coin - a few reasons:

The majority of people will not use something they have to pay to send messages (money or significant processing power or network)

The key thing would be to make it easy to use and fast. You have failed if you created PGP, because PGP is not going to get used by the average Joe. You failed if you created something like Bitmessage that is clunky and takes 4 minutes to send a message.

It needs to be as fast as IM. Seriously, you could code whatever you want but if it is not easy to use it will not be used other than as a forgotten niche.

Another thing that you may not see as a requirement but actually very much is - it must be web based.

"Talk to me on platform! Compile this binary: github.com/platform/platform" > 75% of people: "talk to me on skype"

vs

"Talk to me on platform! http://platform-project.org/webclient or download your own local copy" > 75% of people: *click*

Now of course it must be open source and just serving static javascript. It can connect to commercial providers while being decentralized.

The commercial providers would just be limited to passing encrypted bits, as well as storing encrypted data like a mailbox. Now you might worry about network fragmentation - but that isn't an issue if messages are designed to flood the network, AND you can connect to multiple providers to fetch data. Or run your own. I am 100% sure that this network will end up with free donation supported networks, even if there's nothing prohibiting charging, because $0.01 is infinity larger than $0.00.

Seriously, forget about DHT, forget about blockchain, forget about cryptocurrencies: this isn't difficult, this isn't perfect, but you need a web app and data transmitters.

A and B are the two major rivals that are withholding messages from each other? Join C which connects to both. Metadata like source, from, time, size etc being disclosed? Build a tor network on top of that.

OK, so how do you prevent MITM attacks?
Fingerprints.

But that's not perfect!
It won't be, because you won't succeed if you try to build the prefect system. You need to build something that can be adopted easily. You need to focus as much time on smiles as security.

Also, instead of producing a new forum, try making an easy to use secure messaging system. I'll contribute a few bitcoins of funding.

Step 1: Change username to a random strin
Step 2: Change email to something that doesn't exist

Speaking of which, I'm not having much luck connecting to Just-Dice.com using socket.io-client.

Anyone got something working?

We cannot guarantee this at this stage (especially if you mix large amounts). We do automatically send transactions between Inputs addresses to mix them beyond a default shared wallet.

You need to import the SQL file and create a MySQL database.

"Table 'bitcoin_faucet.dispenses' doesn't exist"

No longer running sorry

That's like saying "nothing on first post indicate, that i cannot hack into this website".

Change your sig to one of the options

No option says random ads.

> Thank you for the email. Yes the issue is for most of the customers. please wait this should be get back to normal.

No, dumb support agent.