Why posts by newbies are deleted ?

[darius2020]

Trying to post I get
my post deleted

(the following message is not correct since I try to post my first message today)

The last posting from your IP was less than 360 seconds ago. Please try again later.

[hilariousandco]

Trying to post I get
my post deleted

(the following message is not correct since I try to post my first message today)

The last posting from your IP was less than 360 seconds ago. Please try again later.

It wasn't deleted it just didn't go through because you posted within 360 seconds. Log ins and searches also count towards this time.

[darius2020]

Trying to post I get
my post deleted

(the following message is not correct since I try to post my first message today)

The last posting from your IP was less than 360 seconds ago. Please try again later.

It wasn't deleted it just didn't go through because you posted within 360 seconds. Log ins and searches also count towards this time.

Does it bitcointalk is clocked every 360 secs ?
Login , wait 360 s
posted a message - wait 360 s
to start with search

search done , wait 360 s
to start with reading/ writing ?

Ok, if bitcointalk is clocked at 360 s intervals, no chance to implement "clock feature" warning
not to have post drafts deleted ?

Just waited 10+ mins ( well above 360 sec limit)
and system generated the same bug as before


==
"
The upper limit is 4294967295, but Bitcoin resets the nonce long before you reach that
"
Does it mean a 1Th/s Bitcoin node can distribute already hashed blocks to special users (success nonce discovered ) ?

[pontiacg5]

Trying to post I get
my post deleted

(the following message is not correct since I try to post my first message today)

The last posting from your IP was less than 360 seconds ago. Please try again later.

It wasn't deleted it just didn't go through because you posted within 360 seconds. Log ins and searches also count towards this time.

Does it bitcointalk is clocked every 360 secs ?
Login , wait 360 s
posted a message - wait 360 s
to start with search

search done , wait 360 s
to start with reading/ writing ?

Ok, if bitcointalk is clocked at 360 s intervals, no chance to implement "clock feature" warning
not to have post drafts deleted ?

Just waited 10+ mins ( well above 360 sec limit)
and system generated the same bug as before


==
"
The upper limit is 4294967295, but Bitcoin resets the nonce long before you reach that
"
Does it mean a 1Th/s Bitcoin node can distribute already hashed blocks to special users (success nonce discovered ) ?

Huh? until you escape newbie rank you will have to wait 360s between every mouse click.

Not sure what this has to do with bitcoin noonce?

[hilariousandco]

Trying to post I get
my post deleted

(the following message is not correct since I try to post my first message today)

The last posting from your IP was less than 360 seconds ago. Please try again later.

It wasn't deleted it just didn't go through because you posted within 360 seconds. Log ins and searches also count towards this time.

Does it bitcointalk is clocked every 360 secs ?
Login , wait 360 s
posted a message - wait 360 s
to start with search

search done , wait 360 s
to start with reading/ writing ?

Ok, if bitcointalk is clocked at 360 s intervals, no chance to implement "clock feature" warning
not to have post drafts deleted ?

Just waited 10+ mins ( well above 360 sec limit)
and system generated the same bug as before


==
"
The upper limit is 4294967295, but Bitcoin resets the nonce long before you reach that
"
Does it mean a 1Th/s Bitcoin node can distribute already hashed blocks to special users (success nonce discovered ) ?

Huh? until you escape newbie rank you will have to wait 360s between every mouse click.

Not sure what this has to do with bitcoin noonce?

It's not every mouse click, but every click you do for a search message log-in etc.

[hilariousandco]

Quote from: hilariousandco on December 24, 2013, 02:22:48 PM
Quote from: darius2020 on December 24, 2013, 12:42:53 PM
Trying to post I get
my post deleted

(the following message is not correct since I try to post my first message today)

The last posting from your IP was less than 360 seconds ago. Please try again later.

It wasn't deleted it just didn't go through because you posted within 360 seconds. Log ins and searches also count towards this time.

Does it bitcointalk is clocked every 360 secs ?
Login , wait 360 s
posted a message - wait 360 s
to start with search
http://www.nasa.gov/images/content/65879main_kepler-portrait-330-427.jpg
search done , wait 360 s
to start with reading/ writing ?

Ok, if bitcointalk is clocked at 360 s intervals, no chance to implement "clock feature" warning
not to have post drafts deleted ?

Just waited 10+ mins ( well above 360 sec limit)
and system generated the same bug as before
data:
==
"
The upper limit is 4294967295, but Bitcoin resets the nonce long before you reach that
"
Does it mean a 1Th/s Bitcoin node can distribute already hashed blocks to special users (success nonce discovered ) ?
 

You what, mate?