Please remove anything nitro and shop or quest related

[ventedcreeps]

Description

So much annoying shops and quest pop ups and monetization B.S.

Suggestions

I like Webcord's speed, but I want it to have Legcord-style blocking for shops and monetization. I suggest keeping Webcord’s fast, lightweight core and integrating Legcord’s filters to block storefronts, Nitro promotions (including quests), and other monetization UI. Add a single settings toggle to enable/disable all monetization and Nitro content, and make the blocking modular and configurable with allow-lists and per-channel exemptions while preserving low memory and CPU usage.

Alternatives

No response

Additional Context

No response

[SpacingBat3]

I have a feeling most of you request there is actually possible via CSS themes in WebCord: should say CSS itself got substantially more powerful with the selectors, so hiding stuff that you find annoying should not be that much of the trouble. That being said WebCord was always more into vanilla experience of Discord… which became substantially worse anyway and makes me regret that I hold to some trust into Discord they'll do a bit better at least on their front-end side. A bit of my idea for keeping Nitro as-is in the past was treating Discord as a service provider and trying to at least give them way to try be profitable even on WebCord as a way to paying them for providing their service, to make WebCord also slightly more friendly towards them… yet the choices they made over the years make it dubious if they are struggling with making their free tier users profitable or are straightforward degrading their service to the point they force them to pay for Discord. At least it became apparent they do a lot to lower the stress onto their servers, yet it feels they do a sloppy job about it and many limitations they impose seem to be designed as more of inconvenience to users to make them pay for their service than some way of quota to have some limits that their servers can keep up with.

With that being said, it might also be slightly a cat-mouse play, since, yeah, if you will be too much aggressive with CSS selectors you might disable pop-ups that might be somewhat useful and if you are going to be very much selective, new popups that Discord adds as their marketing campaign won't be filtered – they update it frequently to thrill people about Nitro I guess, at least I think I saw too many variants of them trying to advertise Nitro and those seem to happen to be delivered randomly so I'm not even sure how I would be able to capture them all in the first place.

Maybe it'll be a great alternative to just share some CSS modification that could be applied to WebCord? We already have GitHub Discussions as some threaded conversation place, where posting stuff like that is more than welcome. Maybe in the past I would care about distributing any anti-Nitro features, but now with mess Discord is in – I don't care anymore.

[SpacingBat3]

And yeah I'm also aware you can simulate some of their popups acknowledgements by messing with the localStorage, but I don't think there's any harm in doing just straightforward blocking of their popups or elements. And with advanced CSS features like :has I think selecting elements by anything is really easy these days with CSS to the point you don't need to have very large amount of classes or IDs to do precise selections.

[ventedcreeps]

Thanks. Webcord is nice, I like it because its so clean but I have an issue where I close it and try to reopen it and it does not work.

…

-------- Original Message --------

On Saturday, 04/11/26 at 14:23 SpacingBat3 ***@***.***> wrote: SpacingBat3 left a comment [(SpacingBat3/WebCord#710)](#710 (comment)) And yeah I'm also aware you can simulate some of their popups acknowledgements by messing with the localStorage, but I don't think there's any harm in doing just straightforward blocking of their popups or elements. And with advanced CSS features like [:has](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:has) I think selecting elements by anything is really easy these days with CSS to the point you don't need to have very large amount of classes or IDs to do precise selections. — Reply to this email directly, [view it on GitHub](#710 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AQ2I5RTGOBGRDJF2GTZ5XMD4VKZU5AVCNFSM6AAAAACXVD3IFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZQGIYDGMJQGY). You are receiving this because you authored the thread.Message ID: ***@***.***>