@quikblend_ it's sad they let you go. you were always one of the most dedicated and reliable folks in that part of the org. hopefully you'll land somewhere new, doing something even better!
@ember_kane Software rollouts do not reach all users the same day and system load varies based on numerous external factors. The reality is we blocked erroneous requests to shed load. I’m sorry if you think there’s more to it than that. Not everything is a conspiracy.
Hey dude, hope you've been well. Behind the scenes there has been some communication yesterday, but it's unclear if anything will come of it. Personally speaking, it's hard to work with an organization that both harasses and tarnishes your personal and business reputation through its social media and community for its own gain. Even their reply here appears somewhat deceitful in that they had no easy way to reach out, but there are numerous ways as you have imagined.
@ember_kane I think there's some conflation between two different issues here. BetterTTV did not block 7TV, but rather fixed an issue causing system instability for its API. The GitHub issue I believe you are referring to is related to an update 7TV made which breaks other extensions.
@MilesN64 i'm not sure if you're trying to get a rise out of me or something but there's nothing noteworthy that occurred here. there was a bug in 7tv that they spun into a hit piece. bugs happen, things break, and things get fixed.
@AlexThaHero @bizmuths I don't work at Discord any longer. My guess would be it's related to a new feature that's in development. No company wants to archive and store all video/audio. That's very expensive.
@MicDubTV @Vincent_V6 @HoldingKeys@BetterTTV From what I've heard they have bots which sit in all the Twitch chat collecting data, and when the bot gets banned it rejoins on a different account (i.e. you can't get rid of it).
@fire we use an enterprise api that still only serves static resources, but our code already supports them. the bigger problem is migrating synced images, since we already stored them static.
@_joeygallegos@find_evil@entemper Discord already maintains a list of leaked/common passwords and prevent them from being set. Email 2FA is enforced at minimum for new location logins. Requiring a mix of upper/lower/number/symbol characters is frustrating UX, which is why we didn’t take that approach.