
But unfortunately, Indi had opened a platform, to all Memory Bank critics to have their word against Memory Bank. It's obvious, during last few days many anonymous comments were thrown against my political stance from very few. Also I wanted Indi to have a sort of forum on this [future posting], not after Memory Bank being de-syndicated, but before he took that decision. BTW he was very quick to remove Memory Bank, with no prior notice, but even by now he has not reacted to those who put comments in Indi.ca, to interpret his words in different ways to harm Memory Bank.
Also I never argued that Future Posting is a fair thing when it comes to a blog aggregator. Technically competent blog aggregators already have found ways to deal with this, except Kottu. So, even if it's technically not feasible, may be b'cos Indi is busy - then we need to build a discussion among bloggers and come to an agreement, none of us do future posting and if some body violates then he will be removed. Memory Bank is totally okay with this.
But, Kottu had different thoughts. It simply removed Memory Bank with no prior notice and then sent a mail. This is what you find in Indi.ca. I don't think this is professional. Although Kottu is not something belong to everyone, SL blogging community expects Kottu be professional. Indi should have sent me a mail first mentioning Kottu does not encourage 'future posting', and if I still violate that, he would have removed my blog.
Also this is not the first time he acted in this way. Few years back he removed many .Net blogs with no prior notice and this is Indi's response to it.
"The reason that people were deleted without telling them was because I was lazy and frustrated"
Indi: I have no hard feelings with you or Kottu. People do visit Kottu to read what bloggers have written. No bloggers - No Kottu. Please be democratic with your approach.
Right now Kottu has a monopoly over blog aggregators. That has given Indi the freedom to act on his own. Just remember one thing, a monopoly is okay till it serves people - when it deviates, history has spoken.
my view is that kottu should manage the aggregation sorting 100% (which i have mentioned in my blog post)... because there will be other blog/cms software and its not like everyone would stick to a wordpress blog... and you cant expect ppl to comply with timestamp tampering esp now... and it is a flaw... and just that he (indi) is not willing to accept it as a flaw in wordpress...
ReplyDeletekottu will have a problem with timestamp tampering till someone fixes the code in kottu.org... and because the tampered post will always be on top... and there are ppl who are religious about this whole thing... and blah blah blah... and they will always make a big deal about it... and its been such a big deal that the voice had not posted anything since then, in his/her blog!
but he (indi) has a different view... and he's made a request/demand/whatever... and the fact remains that he wont tolerate timestamp tampering... and whats the big deal... i mean everyone else (including me) dont seem to have a problem with it...
i didnt like the way voice and rest of the guys pounced on MB... not cool! havent you read harry potter (i've not but i've seen ppl who have)... wars start like this... ah... the issues ppl have these days!
So, I think we've reached a compromise. I've readded Memory Bank to Kottu and sent you a mail. However, I think that mail bounced from your main account, so I sent it to Yahoo as well.
ReplyDeleteYes, we came to a compromise - I also received your last mail. I appreciate your patience through out the discussion.
ReplyDeleteShehal: thanks a lot for forwarding your thoughts.
A bit melodramatic and oversensitive, much?
ReplyDelete