delight-im / faceless Goto Github PK

when i install server over. i post like this
http://192.168.113.129/android/Server/public_html/workers/score_updater.php
but it is not responed,why

After a transition period of roughly 42 days (i.e. 2014-08-28), the branch that uses MCRYPT_BLOWFISH in decrypt() can be safely deleted.

All new messages and comments are already encrypted in Rijndael/AES and from that date, old messages will be either outdated or have been destroyed automatically, anyway.

This is a question and not an issue.

Apart from the cost of buying an sms-enabled phone. Is there an cost associated with sending and receiving sms on the phone in your Twilio account. If yes, what is the average running cost of setting up the service.

Secondly, is it possible to work other third-party sms/phone services.

Right now the "Block user" feature only prevents new messages by that user from appearing in the "Friends" feed.

When a user is blocked, however, this should also cause new messages by that user from appearing in the "Latest" and "Popular" feeds.

A requirement is that blocking affects future messages only.

#4 (comment)

Looking at the table structure, I would suggest to replace all the IDs with a UUID to allow multiple servers to write at the same time without possible DB problems, but until you do some code rewriting, I would suggest to drop the field id in the throttling table and change the UNIQUE key left into a PRIMARY one

Users often report that they don't want to write something and reveal certain things because they're afraid their friends may read it.

Of course, friends cannot identify the author of a post, but especially right now (at the beginning), users are afraid of friends guessing their identity.

This brings up the question whether users should be allowed to select the audience of their messages, for example like this:

Audience:
+ Friends and Public
+ Public only
+ Friends only

Public means that their messages will appear in the global feeds and Friends means that their messages will appear in the specific feeds with a label such as "Friend" or "Friend of a friend".

But this may cause users to select "Friends only" or "Public only" habitually, defeating much of the purpose and potential of the app while there is no rational reason and need to do so.

Benefiting from word-of-mouth advertising is realy hard for anonymity/pseudonymity apps.

Users want to hide precisely the fact that they're using such an app, usually.

Allowing for anonymous invitations to be sent to friends may sound like a great solution, but this should normally be considered spam/illegal.

The first instinct is often just to hash the contact information before sending it to the server. If the server has the SHA256 hash of every registered user, it can just check to see if those match any of the SHA256 hashes of contacts transmitted by a client.

Unfortunately, this doesn’t work because the “preimage space” (the set of all possible hash inputs) is small enough to easily calculate a map of all possible hash inputs to hash outputs. There are only roughly 10^10 phone numbers, and while the set of all possible email addresses is less finite, it’s still not terribly great. Inverting these hashes is basically a straightforward dictionary attack. It’s not possible to “salt” the hashes, either (they always have to match), which makes building rainbow tables possible.
[...]
As far as we can determine, practical privacy preserving contact discovery remains an unsolved problem.

https://whispersystems.org/blog/contact-discovery/

https://github.com/delight-im/Faceless/blob/master/Server/public_html/classes/Encryption.php#L49
This HMAC comparison is not made in constant-time, nor does it follow a "double HMAC" construct.

http://blog.astrumfutura.com/2010/10/nanosecond-scale-remote-timing-attacks-on-php-applications-time-to-take-them-seriously/

https://github.com/delight-im/Faceless/blob/master/Server/base_crypto.php
I'm curious as to why you're using MCRYPT_BLOWFISH instead of something like, say, AES (MCRYPT_RIJNDAEL_128)?

I'm online via wifi, but still when I open the app and when I try to post something I get this message. Latest version via GitHub.