Skip to main content

Show HN: Two uBlock Origin rules to improve your Twitch experience https://ift.tt/3pkGtgP

Show HN: Two uBlock Origin rules to improve your Twitch experience It might come down to taste, but I feel like a lot of the "features" Twitch has been adding have cluttered the interface while offering little of value for someone like me who just watches streams occasionally and isn't closely involved in community events. But most importantly, I'm bothered by the non-dismissable popups that now appear over the video feed. They seem to be for extensions, but what features they provide evades me. These two uBlock Origin rules (which you can add in the My Filters tab) will remove the main two modals that can pop up over the video: www.twitch.tv##.extensions-dock-card ext-twitch.tv##.prime-extension-root Additionally, you may want to get back a chat frame without a leaderboard header: www.twitch.tv##.channel-leaderboard Twitch generates random class names, possibly to prevent your blocking some elements, so I tried to find the topmost classes. I hope that's useful to some. December 22, 2021 at 11:05PM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...