For my part, I saw a thread and joined it, not aware that github was primarily being used to discuss the technical aspects. My apologies. I'm a writer and publisher, not a tech.
You are viewing a single comment's thread from:
For my part, I saw a thread and joined it, not aware that github was primarily being used to discuss the technical aspects. My apologies. I'm a writer and publisher, not a tech.
@markrmorrisjr , No worries. We really don't have much of a better way to directly address technical concerns and their likely ramifications to the Dev's without hopping on to Github. The original posts that drew attention to this very issue even had links pointing people to Github because the flow of information around here is a little... Uhm... Disorganized at times?
We don't have sub's like Reddit we only have #tags so the next best thing was to point people at Github I guess? (Doh... I doubt that mistake will be made again in the future.)
It was kind of like watching a scene from Family Guy where Peter just keeps on fighting with the chicken regardless of the venue or the collateral damage. The debate just kept moving from place to place only to end up right back where it started. We even managed to carve a path of collateral damage in our wake as well that shall forever be attached to the Steemit Git Repo.
Yup, we're an awesome bunch sometimes. You may not have known any better but plenty of us did and I'm sure we all realized this morning that it was too late to take it back. I honestly doubt anyone was proud to have taken place in the cross platform brawl, but as @anyx said on his thread from yesterday this place is very much the Wild West of social media.
In light of that revelation here's my peace offering of a parody for taking part in such an incident considering many of us did this very thing right here :
Steemit, gave me a bad coupon...