Joined: 10/29/2014
Posts: 176
Location: Bavaria, Germany
I find the information (from Spikestuff venting about fsvgm's post) on following occurrences that preceed the incident around HappyLee & Mars608's case insightful and interesting as context on the topic of so-called ''flooding'' TVC:
[quote Spikestuff]SpikestuffToday at 5:27 AM
Also fsvgm's post doesn't shine the whole information of what occurred on TASVideosChannel in his post so there's the possibility that'll end up in the same direction of missing actual info.
Doesn't mention the intentions of why exactly just that it happened and just mentioned accomplice to me.
SpikestuffToday at 5:38 AM
Colin was before Lee then Lee happened.[/quote]
[quote Spikestuff]SpikestuffToday at 5:40 AM
iirc the reaction was "so"
I'll have to double check public irc logs.
<fsvgm777> EZGames69: Remember when you were so proud of your DecapAttack encodes?
--TASVideoAgent showing the changes from downloadables and YouTube encodes--
<fsvgm777> Well, they're now history.
<EZGames69> Cool, good for you
<fsvgm777> This is for the damage you've caused to our site's reputation.
<EZGames69> Lol what?
<adelikat> this seems like uncalled for rudeness
<Memory> yeah it really doesn't ask for this[/quote]
[quote Spikestuff]SpikestuffToday at 5:45 AM
It was to get rid of Colin's presence on TASVideos' YouTube.[/quote]
[quote Spikestuff]SpikestuffToday at 5:49 AM
This was planned back in Feb last year.
And executed in June.[/quote]
[quote Spikestuff]SpikestuffToday at 5:50 AM
23 - May - 2018
https://cdn.discordapp.com/attachments/379646653793304576/538215235660677130/unknown.png[/quote]
[quote Spikestuff]
SpikestuffToday at 5:50 AM
>Quack represents the reencode
>Wahoo represents the Publication for Klonoa.[/quote]
[Edit: Previous above image substituted by smaller image]
[quote Spikestuff]SpikestuffToday at 5:52 AM
These videos are all unlisted btw.
Before June 23rd happened.
Where those videos came out and the number goes to 50.[/quote]
[quote Spikestuff & Aran;Jaeger]
Aran;JaegerToday at 5:53 AM
and then not unlisted anymore within short time, right?
or was it different
SpikestuffToday at 5:53 AM
When encoders upload a video the video goes up unlisted for confirmation about the encode if it's in the desired resolution or not.[/quote]
[quote Spikestuff]SpikestuffToday at 5:58 AM
slowly scrolling back to Feb 2018[/quote]
[quote Spikestuff]SpikestuffToday at 6:14 AM
There's a lot to unpack seriously.
[/quote]
[quote Spikestuff]SpikestuffToday at 5:30 AM
- fsvgm's plan
- spikestuff's execution
- fsvgm's assistance
- spikestuff's fallback to blame
- fsvgm's attempt to damage the pride of Colin by laughing in his face
- colin/ezgames doesn't care
[end]
That's the spark notes.[/quote]
collect, analyse, categorise.
"Mathematics - When tool-assisted skills are just not enough" ;)
Don't want to be taking up so much space adding to posts, but might be worth mentioning and letting others know for what games 1) already some TAS work has been done (ordered in decreasing amount, relative to a game completion) by me and 2) I am (in decreasing order) planning/considering to TAS them. Those would majorly be SNES games (if not, it will be indicated in the list) I'm focusing on.
1) Spanky's Quest; On the Ball/Cameltry; Musya; Super R-Type; Plok; Sutte Hakkun; The Wizard of Oz; Battletoads Doubledragon; Super Ghouls'n Ghosts; Firepower 2000; Brain Lord; Warios Woods; Super Turrican; The Humans.
2) Secret Command (SEGA); Star Force (NES); Hyperzone; Aladdin; R-Type 3; Power Blade 2 (NES); Super Turrican 2; First Samurai.
(last updated: 18.03.2018)
fsvgm777, I am at a complete loss of words.
If you were replacing those encodes because of mistakes I made in them then I would totally understand that, but it seems like you only did it to completely remove my name from any of them, which side note you missed one: https://www.youtube.com/watch?v=pSVvEcjX9H0. (feel free to replace that one if you want, I do not give a fuck anymore).
but that's not what I'm upset about, what I'm most upset about is the #FuckColin trend you are pushing.
You should be very ashamed of what you did, and it's sad to see this kind of behavior from a SENIOR publisher of all positions.
[14:15] <feos> WinDOES what DOSn't
12:33:44 PM <Mothrayas> "I got an oof with my game!"
Mothrayas Today at 12:22: <Colin> thank you for supporting noble causes such as my feet
MemoryTAS Today at 11:55 AM: you wouldn't know beauty if it slapped you in the face with a giant fish
[Today at 4:51 PM] Mothrayas: although if you like your own tweets that's the online equivalent of sniffing your own farts and probably tells a lot about you as a person
MemoryTAS Today at 7:01 PM: But I exert big staff energy honestly lol
Samsara Today at 1:20 PM: wouldn't ACE in a real life TAS just stand for Actually Cease Existing
The problem, as I see it, is that people are talking about this new information that has surfaced, allegations that a particular staff member deliberately acted completely inappropriately, but the only responses we are getting are, essentially, "this was already dealt with months ago, the new information doesn't change anything". I don't think people are talking about the loss of subscribers to the YouTube channel. That's not the issue here.
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
EZGames69 wrote:
fsvgm777, I am at a complete loss of words.
If you were replacing those encodes because of mistakes I made in them then I would totally understand that, but it seems like you only did it to completely remove my name from any of them, which side note you missed one: https://www.youtube.com/watch?v=pSVvEcjX9H0. (feel free to replace that one if you want, I do not give a fuck anymore).
but that's not what I'm upset about, what I'm most upset about is the #FuckColin trend you are pushing.
You should be very ashamed of what you did, and it's sad to see this kind of behavior from a SENIOR publisher of all positions.
I was the only person using your encodes, and none of the staff members was happy about it. Mistakes kept being found, but then there was a personal issue that made it impossible to use your encodes in the future, I just don't want to describe it here. As for that "#campaign", it only existed in a private talk between 2 people, and thankfully we don't censor people's PMs, the ugly part is sharing private info as is (on Aran's part as well). Though I remember that fsvgm agreed it was a bad idea to "congratulate" you that all your encodes were replaced in the way it was done. And my logs only start at July 1st.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I think that what we should take away from all this is considering setting clear expectations for professional behavior from staff members in some sort of guidelines page similar to how we have guidelines for other things. This could go a long way towards reducing the amount of incidents we have as a whole.
[16:36:31] <Mothrayas> I have to say this argument about robot drug usage is a lot more fun than whatever else we have been doing in the past two+ hours
[16:08:10] <BenLubar> a TAS is just the limit of a segmented speedrun as the segment length approaches zero
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Memory wrote:
I think that what we should take away from all this is considering setting clear expectations for professional behavior from staff members in some sort of guidelines page similar to how we have guidelines for other things. This could go a long way towards reducing the amount of incidents we have as a whole.
I love this idea and I'll try to come up with something. Maybe this thread is a wrong place to ask for ideas/suggestions, but if you guys want, shoot.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
<fsvgm777> *reads discussion from about 2h20min ago*
<fsvgm777> I, frankly, should have never, ever pulled that off in the first place, and frankly, it's completely unacceptable behaviour from someone in my position.
<fsvgm777> EZGames69: Consider my threats (about blocking you) null and void.
<EZGames69> Thank you
<MemoryTAS> Thanks!
<EZGames69> fsvgm777 I know you get extremely angry very easily so I am sorry for not being careful about that.
<EZGames69> Lets finally put this behind us
<fsvgm777> Well, I don't necessarily get angry very easily, since I bear a very calm mind, but sometimes, I just snap.
<fsvgm777> And then I snap hard.
<fsvgm777> So....yeah, let's put it behind us once and for all.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Not to be this guy, but as I was probably the first one to admit, we as a community have been unfair when all we're talking about here happened. It all started in the SMB warpless submission, and we all overreacted, which led to a huge confrontation and confusion. TVC flood was just a result of it, and we, the community, are sorry about this result as well as what led to it. As I also said above, this whole situation showed us that we're very imperfect, and we will be using this understanding in future to be more fair and more united.
This almost makes it sound like you all were in cahoots to deliberately and knowingly sabotage that one SMB TAS.
Nobody has denied or refuted this. Am I to conclude that it's actually what happened?
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Why should I care about words you imagine me saying?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
Warp wrote:
Nach wrote:
Warp wrote:
That thread you are referring to seems to be talking about sudden loss of subscribers and views on the YouTube channel
Yes, that's exactly what I'm talking about. I haven't said anything different.
The problem, as I see it, is that people are talking about this new information that has surfaced, allegations that a particular staff member deliberately acted completely inappropriately, but the only responses we are getting are, essentially, "this was already dealt with months ago, the new information doesn't change anything". I don't think people are talking about the loss of subscribers to the YouTube channel. That's not the issue here.
Yes, the actual issue was dealt with months ago. The new information does not change anything.
What actually happened:
Encode flooding made ~850 people leave, and ~80,000 less viewings occurred.
Bear in mind, people left at other times too, and viewing is variable any way, so it's hard to know exactly how much was due to the amount of encodes at that time. ~40 people left earlier in the week for some unknown reason. We have no comparison against what happened in the past when just 10-20 encodes were released. Some of these people who left / did not watch may in fact just be using the site, RSS feeds, or watching via other methods anyway. Some of them may have come back later. Also with only daily totals, it's hard to know how many left and were cancelled out by new arrivals, and what the rate of that is like on other days. All in all hard to accurately measure.
On a scale of 1-10 how bad this is, assuming worst case scenario that people left and did not come back, and do not use other viewing methods, I'd rate it a 5.
Now we're being told that what some encoders/publishers really wanted was to release a lot hoping that maybe nobody notices that one encode. The same encode which appeared on the main site, RSS feeds, search features here, Google, YT and elsewhere, on unwatched lists, all without any sort of tampering. If that's actually what happened, on a scale of 1-10, I'd rate it a 1.
So yes, we dealt with a severity 5 situation, which at the time it was unclear what the motivation was, even though we had our suspicions, and now we're being told it was intended to be a severity 1 situation. Yes, that doesn't change anything.
I'm not happy about the situation, but it's the first time the people in question went wild with their encoding/publishing abilities and we already dealt with them. They've been thoroughly warned. We're not going to discount years of loyal dedicated hard work because of one bad incident where incidentally at the same time, behavior throughout the entire forum by many members was absolutely despicable.
On the bright side, it also led us to looking into making certain improvements in the site itself to prevent even unintended related issues in the future, and that's a great thing.
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.
On the bright side, it also led us to looking into making certain improvements in the site itself to prevent even unintended related issues in the future, and that's a great thing.
This should include the following:
When someone tries to help the site (for example, with encoding), it's completely natural for them to mess up at first. Instead of other encoders fixing it by themselves and saying that X has messed up, it's better if they tell the person what they did wrong and kindly asking them to fix it, and possibly help him with that. That's how people learn. Not by being told they messed up. Which includes comments on YouTube.
Not to stir the pot again and I'm aware that Ezgames and Fsvgm are good now, but what happened concerns me that if someone would want to help this site in the future, seeing what happened here is gonna make them reconsider that. Especially coming from senior staff.
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
I already said usage of his encodes was a one-sided decision, if you want details send me a PM (though promise it won't be seen by anyone else).
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Now we're being told that what some encoders/publishers really wanted was to release a lot hoping that maybe nobody notices that one encode. The same encode which appeared on the main site, RSS feeds, search features here, Google, YT and elsewhere, on unwatched lists, all without any sort of tampering. If that's actually what happened, on a scale of 1-10, I'd rate it a 1.
I think the idea that a publisher would intentionally try to sabotage a submission would rank worse than a 1 / 10. Even if the actual damage was minimal the issue here is whether or not there was malicious intent.
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
Flameberger wrote:
Nach wrote:
Warp wrote:
Nach wrote:
Warp wrote:
Now we're being told that what some encoders/publishers really wanted was to release a lot hoping that maybe nobody notices that one encode. The same encode which appeared on the main site, RSS feeds, search features here, Google, YT and elsewhere, on unwatched lists, all without any sort of tampering. If that's actually what happened, on a scale of 1-10, I'd rate it a 1.
I think the idea that a publisher would intentionally try to sabotage a submission would rank worse than a 1 / 10. Even if the actual damage was minimal the issue here is whether or not there was malicious intent.
The actual damage that occurred in reality was not minimal. Possibly permanently losing ~850 users if not more?
Regarding your hypothetical situation, I'm not convinced it's even possible to sabotage a submission in that fashion. If we want to start worrying about imaginary offences, put down that voodoo doll you made, and stop putting pins in it.
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.
Now we're being told that what some encoders/publishers really wanted was to release a lot hoping that maybe nobody notices that one encode. The same encode which appeared on the main site, RSS feeds, search features here, Google, YT and elsewhere, on unwatched lists, all without any sort of tampering. If that's actually what happened, on a scale of 1-10, I'd rate it a 1.
I think the idea that a publisher would intentionally try to sabotage a submission would rank worse than a 1 / 10. Even if the actual damage was minimal the issue here is whether or not there was malicious intent.
The actual damage that occurred in reality was not minimal. Possibly permanently losing ~850 users if not more?
Regarding your hypothetical situation, I'm not convinced it's even possible to sabotage a submission in that fashion. If we want to start worrying about imaginary offences, put down that voodoo doll you made, and stop putting pins in it.
It's not my hypothetical situation, I haven't accused anyone of anything. I just think that "It's not a severe issue" is not the correct response to claims of "a publisher sabotaged a submission." That makes it sound like it's accepted but is something we just don't care about.
If you think it's a false accusation just say that from the start.
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
But intent was already admitted in this very thread, its reasons were admitted, its consequences were admitted, restrictions were imposed, even the staff conduct page is already in the works. All participants apologized for all the problems it caused and most of the conflicting camps agreed to restore the peace, what are we still assuming and suggesting?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
Flameberger wrote:
It's not my hypothetical situation
The case of "release a lot hoping that maybe nobody notices that one encode" is a hypothetical. Maybe it can happen, maybe not. AFAIK, it's never been successfully tested on our channel.
Flameberger wrote:
"It's not a severe issue"
What actually happened, ~850 people possibly leaving forever due to what certain encoders did is a severe issue.
Insisting we should worry about a hypothetical, "makes it sound like", from your perspective, that ~850 people possibly permanently leaving "it's accepted but is something we just don't care about".
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.
The case of "release a lot hoping that maybe nobody notices that one encode" is a hypothetical. Maybe it can happen, maybe not. AFAIK, it's never been successfully tested on our channel.
Flameberger wrote:
"It's not a severe issue"
What actually happened, ~850 people possibly leaving forever due to what certain encoders did is a severe issue.
Insisting we should worry about a hypothetical, "makes it sound like", from your perspective, that ~850 people possibly permanently leaving "it's accepted but is something we just don't care about".
Alright now I'm lost. The only thing I've been trying to say is that your assigned
severity of 1/10 to the scenario of a publisher sabotaging a submission is too low of a value. I'm saying it's a more serious issue than that.
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
Flameberger wrote:
Alright now I'm lost. The only thing I've been trying to say is that your assigned severity of 1/10 to the scenario of a publisher sabotaging a submission is too low of a value. I'm saying it's a more serious issue than that.
Let me fix that for you:
"assigned severity of 1/10 to the scenario of a publisherpublisherssabotagingattempting to sabotage a submission".
And if you don't like my scale fine. My point is, it's a drop in the bucket compared to losing ~850 people. If you think it's more severe than losing ~850 people, that can be your opinion, it surely isn't mine.
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.
I tried to stay away, but still might need to say something.
Nach wrote:
Yes, the actual issue was dealt with months ago. The new information does not change anything.
Nach, I respect your effort in it, but to me this wasn't dealt with months ago, since me and Mars608 (and EZGames69) never got an apology, whether in public or in private, before BrunoVisnadi decided to bring this issue public. Neither did the YouTube encode fixed or many of those malicious ratings towards our movie fixed if it weren't for feos' efforts after I brought something up in NES TAS of 2018 thread.
I don't know why we have to split that topic, as if they weren't connected. But here's what Spikestuff did to sabotage our movie (that I know of):
1. Uploading at least 54 old (mostly obsoleted TASes) videos right after publishing our TAS on YouTube. All of them encoded by Spikestuff (and some later videos encoded by fsvgm777).
2. Using a unusual logo with a scary sound, probably to scare people away from watching our TAS.
3. Malicious comments by multiple fake YouTube accounts.
4. Messing up with the cover, introduction text, both encodes. This was quickly fixed by another publisher and Spikestuff himself after I pointed it out in our movie thread, but me blaming Spikestuff about his bad publication work caused our movie thread being locked by a moderator and still not unlocked.
5. A malicious rating (along with other users). I remember the entertainment rating was a "2".
BrunoVisnadi found out about those YouTube stuff before me, as I wasn't familiar with TVC on YouTube. By the time he told me, our thread was already locked. He also told me that he was talking with staff privately about how to deal with it, but I didn't see any progress being made in half a year.
I don't think it takes a genius or a mind reader to tell that those things are connected.
I don't know why Spikestuff had to be so persistent in doing everything in his power to make our TAS look as bad as possible, as I had nothing against Spikestuff before it happened.
Nach wrote:
"assigned severity of 1/10 to the scenario of a publisherpublisherssabotagingattempting to sabotage a submission".
If it were "publishers" instead of "a publisher", doesn't that make it worse?
And I don't know why it has to be called "attempting to sabotage", because they succeeded doing it until being exposed half a year later.
Did the publishers know that it's wrong to abuse their power to sabotage a publication? Of course they knew. But why they did it anyway? Because they thought they could get away with it, and they almost did.
Right now, many of what can be fixed have been fixed, thanks to the efforts of feos and BrunoVisnadi, except our movie thread still being locked.
I don't think the problem is that we allowed publishers to upload so many YouTube videos in a short time. There are many things we technically can do, like using fake accounts to attack people or things we hate, but that doesn't mean that we should do.
I think the key issue and what people concern the most is: What do we learn from all this? How do we prevent similar things from happening again?
Recent projects: SMB warpless TAS (2018), SMB warpless walkathon (2019), SMB something never done before (2019), Extra Mario Bros. (best ending) (2020).
Why should I care about words you imagine me saying?
The apology post you made, in the context of this thread, almost sounded like you were apologizing that the entire tasvideos staff intentionally colluded in trying to bury that one SMB TAS. I was asking for clarification because that can't possibly be so. I'm convinced you didn't mean that, so I was asking what exactly you were apologizing for.
I find an answer like "I don't care if you are understanding what I meant incorrectly" very puzzling. Why wouldn't you want to clarify such a misunderstanding? First you write a commendable piece of apology, and then you act in a very confrontational and dismissing manner towards someone asking for clarification. I don't understand why.
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Warp wrote:
The apology post you made, in the context of this thread, almost sounded like you were apologizing that the entire tasvideos staff intentionally colluded in trying to bury that one SMB TAS. I was asking for clarification because that can't possibly be so. I'm convinced you didn't mean that, so I was asking what exactly you were apologizing for.
I find an answer like "I don't care if you are understanding what I meant incorrectly" very puzzling. Why wouldn't you want to clarify such a misunderstanding? First you write a commendable piece of apology, and then you act in a very confrontational and dismissing manner towards someone asking for clarification. I don't understand why.
You weren't satisfied by simply asking for clarification, you started imagining whatever nonsense my words meant (you even knew it was nonsense in the first place), while none of them was even remotely close to the nonsense you imagined. If you reread the SMB warpless thread and feel perfectly fine about everything what happened, then you don't have to worry about people apologizing.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
You weren't satisfied by simply asking for clarification, you started imagining whatever nonsense my words meant (you even knew it was nonsense in the first place), while none of them was even remotely close to the nonsense you imagined. If you reread the SMB warpless thread and feel perfectly fine about everything what happened, then you don't have to worry about people apologizing.
This paragraph of text could have been a brief summary of what you actually meant. Instead, you still insist on a knee-jerk and antagonizing reaction.
The onus of being understood correctly is on the writer, not on the reader. If the text is confusing and someone asks for clarification, the proper answer is not "do your own research to try to find out what I actually meant, I'm not going to explain it to you". You are asking me to do research to interpret correctly what you wrote, rather than actually explaining what you meant.
It is still unclear to me what exactly was the thing you were talking about in that apology post, and I'm asking for a brief explanation. Why is that too much to ask? Am I somehow being unreasonable here to ask for clarification?
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Stop twisting my words. You're not helping anyone.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
HappyLee wrote:
Nach, I respect your effort in it, but to me this wasn't dealt with months ago, since me and Mars608 (and EZGames69) never got an apology, whether in public or in private
Those who wronged you should apologize to you.
HappyLee wrote:
Nach wrote:
"assigned severity of 1/10 to the scenario of a publisherpublisherssabotagingattempting to sabotage a submission".
If it were "publishers" instead of "a publisher", doesn't that make it worse?
If multiple people were intentionally involved in attempted sabotage, then yes, it's worse.
HappyLee wrote:
And I don't know why it has to be called "attempting to sabotage", because they succeeded doing it until being exposed half a year later.
Define "it". The only context I'm talking about is publication burying. Even though it looks like it was attempted to bury the publication, I see no evidence that it was actually buried in any meaningful way.
Regarding your other issues, you have every right to be upset, but this is not the thread for it. This thread is solely about the issue of flooding reencodes to TVC.
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.