LinkedIn “Held for Moderation” kills participation.
Ever posted to one of your groups and get the dreaded “Your Post Is Being Held For Moderation.” … I’m going to try to convince you that this is hurting all Linkedin users, and we should tell LinkedIn to STOP doing this.
LinkedIn wrote a software “feature” that allows ONE group owner to BAN you from ALL your groups. It works like this – you post to a group you’re in – let’s say the I-Like-Cheese Group. But you mention a cheese by it’s brand name. The group owner (head cheese head) decides that the post is promotional – and so he marks that YOUR posts are to be … “Held For Moderation.”
Now, your posts are BANNED from ALL the groups you’re in. Try to post to the I-Love-Dogs group … and you’ll get the “Your Post Is Being Held For Moderation.” Try to post in the My-Blue-Pony group and you’ll see … “Your Post Is Being Held For Moderation.” Post to a group critical to your career … you guessed it – held for moderation.
Now when I say “banned”, I don’t mean you can’t read what is going on in other groups, but you’re banned from the conversation as your posts will either be held so long that moment has past, or your post never gets seen at all. You see, every post that is held, requires that the group owner release your post. Not just the posts of the blocking group, but of ALL the groups you’re in. So, if you post to a non-blocking group, but the owner is away for a week, your post gets held for a week. If the non-blocking group owner rarely check the group, your posts rarely get posted. And if the non-blocking owner is just tired of releasing your posts, well, they never get posted at all.
So how do you get unblocked?
ONLY the original blocking group owner, who blocked, you can unblock you. As long as they have the block on, your posts are held for ALL your groups. AND the idiot group owner never needs to tell you. So if you’re in 50 groups, you need to contact each one and HOPE you find the hidden owner. And they unblock you. But … what makes this game extra fun is that the owner does NOT need to tell you who they are and LinkedIn refuses to help. LinkedIn has this lame statement about how they “can’t” when in fact they can. It’s there database that the block is in.
LinkedIn in has lied and said that they cannot change this – well sure they can – it’s just software. A developer wrote the code to do this, and they can remove it or change it.
I suggest a system where a group owner can ONLY hold posts for HIS/HER group, and the hold informs the member. “Hey dude, the Cheese Heads don’t allow mentioning of brand names, your posts will be held for moderation from now on.” And if this system is to prevent spam, LinkedIn could have a system where if your posts are being held by 10% of your groups, you can’t post to any until you clear these blocks. Maybe 10% is to low for a person who is only in two groups, but some reasonable system could be established to balance spam and legitimate participation.
Please join me in posting to ALL your groups that you support this idea. Ban the Ban!
Imagine having your competitive data on the same computer as ten competitors. That’s exactly what happens with Software As A Service (think Salesforce.com). Many companies have their prospect lists, clients and sales data on the same computer. Yet these companies sleep like a baby at night … how?
This SaaS application I wrote for an insurance client. They wanted it for their 25 telemarketers and five insurance agents. But they also wanted to sell it to other agents. That meant that the prospect lists, clients and even telemarketing scripts stay confidential. But how?
Because a SaaS application will be used by multiple users, it is critical to keep data separated, encrypted and only available to the right users. To keep data separate, I wrote server side code that knows where the data is, but does not transmit this to the web browser. Basically, when a user logs in, my server code gets the right data, and that is presented to the session of the logged in user. And the data for each company is either in a different folder on the same server, or on a totally separate server.
Next, each company gets it’s own database file. And that file is encrypted. So getting the file is useless. Yet the decryption code is based off the user ID/Password pair. So the right person gets access.
Unlike Apache, MySQL, PHP solutions, compiled server side applications are hardened. They are protected against MySQL injection attacks, PHP attacks by viewing the code, and common web server exploits.
This insurance application allows multiple competitors to co-exits – sharing the same application, but none of the data, data locations or decryption keys.
For a Video pre-view goto http://youtu.be/T3bWZC56v7Q