Would I get banned.....
-
If I was unable to fill a position for a DevOps / Continuous Integration and Deployment person at a company with great benefits, working 8 to 5 and you get to pick the tech and the processes? If I would get banned, I will stop........... it is in Joburg, South Africa
-
If I was unable to fill a position for a DevOps / Continuous Integration and Deployment person at a company with great benefits, working 8 to 5 and you get to pick the tech and the processes? If I would get banned, I will stop........... it is in Joburg, South Africa
-
If I was unable to fill a position for a DevOps / Continuous Integration and Deployment person at a company with great benefits, working 8 to 5 and you get to pick the tech and the processes? If I would get banned, I will stop........... it is in Joburg, South Africa
-
Reads like an attempt at a job advert in the lounge......
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
-
O bloody hell. Although what could possibly be the advantage of doing it like this then? :doh:
»»» Loading Signature «««· · · Please Wait · · ·:badger: :badger: :badger: -
Charl wrote:
If I would get banned
If you have to ask that question, then it is probably wrong to do it.
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
*applies hammer*
-
Charl wrote:
If I would get banned
If you have to ask that question, then it is probably wrong to do it.
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
-
I don't know that flies in the face of it's easier to ask for forgiveness than get permission.
-
Difficult to ask forgiveness however if the general population has nuked the account.
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
-
Only a crappy community would nuke an account with that longevity for breaking a rule of that degree.
Why? If someone has been here that long, then they presumably know how we feel about spam, plagiarism, and so forth. If they feel they have been hard-done-by, they can appeal to the Hamsters who can reinstate the account (As happened with one member several times on the same weekend). If they have been hacked, then we nuke the account which stops the hacker, and the legitimate user can appeal and change his password.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Why? If someone has been here that long, then they presumably know how we feel about spam, plagiarism, and so forth. If they feel they have been hard-done-by, they can appeal to the Hamsters who can reinstate the account (As happened with one member several times on the same weekend). If they have been hacked, then we nuke the account which stops the hacker, and the legitimate user can appeal and change his password.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Why? Because there are always gray areas and exceptions. A community should be better than that. There's a significant difference between nuking an account and punitive action like preventing further posts for a time, etc.
If the site owner allows users to nuke accounts, that is his business. If we don't like it, we are free to go elsewhere; if we like it, we stay. His site - his rules.
-
Reads like an attempt at a job advert in the lounge......
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
Do you sometimes see "Message Automatically Removed" and find yourself itching to see the message? Of course, invariably seeing the message would be disappointing. Possibly another character flaw?
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
If the site owner allows users to nuke accounts, that is his business. If we don't like it, we are free to go elsewhere; if we like it, we stay. His site - his rules.
-
Why? If someone has been here that long, then they presumably know how we feel about spam, plagiarism, and so forth. If they feel they have been hard-done-by, they can appeal to the Hamsters who can reinstate the account (As happened with one member several times on the same weekend). If they have been hacked, then we nuke the account which stops the hacker, and the legitimate user can appeal and change his password.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
OriginalGriff wrote:
If they feel they have been hard-done-by, they can appeal to the Hamsters who can reinstate the account (As happened with one member several times on the same weekend).
Fckn great bloke him.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
Why? Because there are always gray areas and exceptions. A community should be better than that. There's a significant difference between nuking an account and punitive action like preventing further posts for a time, etc.
Nuking is the only option we are given: we don't want the spam, so we use the tools at our disposal. The "full Monty" nuke is only applied by the Hamsters, so any nuke we apply doesn't destroy articles, posts and so forth - but it does prevent spammers from continuing. Good enough for me.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Difficult to ask forgiveness however if the general population has nuked the account.
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
There's no point in us asking him to forgive us for that, then?
I wanna be a eunuchs developer! Pass me a bread knife!
