Not the parent poster, but I am similarly concerned about tag spam. I find big tag blocks can ruin the reading experience on platforms that display them in-line with the body text.
Another comment suggested that tags be put in a field separate from the body of the post (and they shouldn't be parsed from the body, either). I think that's the best way to facilitate Lemmy clients to (optionally) hide big tag blocks.
I do that too. There are plenty of subthreads going arguing straw-use is an accessibility issue, but in my case, I just want them for specific drinks -- mostly cocktails.
The head on a Ramos Gin Fizz practically requires a straw to enjoy. Especially as someone with a mustache.
Strongly recommend hay straws (like, made of "straw").
They're better than paper in that they don't sog up. They're inconsistent in size but that has never bothered me. A little flimsy, but I stir iced drinks with them all the time.
They ask a bit of trust on that, but their FAQ also has an appeal to reason:
I have privacy concerns over linking my search queries with my credit card. Why should I trust you?
We do not log search queries. Queries you type are never associated with your account. The simple reason is we don't have any reason to do so, as it would only be a liability for us. We are in the business of selling search results, not user data.
You might consider a more elegant approach to accomplish your goals.
For example, I run Tailscale on all of my devices. They are accessible to each other (at all times) through the encrypted "Tailnet" while each has its own public internet provider (my home ISP, my cellular provider, my VPS host, etc).
They all route their DNS requests through my home server which is running Adguard (for DNS ad blocking on every device). If I wanted I could route all their traffic (not just DNS) through the home server, and I could have the home server's internet-facing interface connect through a commercial VPN to then hide all that egress traffic, across all my devices.
YouTube is in an advantaged position relative to other sites because they directly serve the ads from the same servers that serve the content. That's why DNS blocking doesn't work.
It would take more effort than they currently put in but they could track each user-session closely enough to require that the ad stream complete before the content stream is served.
If that happens, I think the next step in ad blocking would be to accept the ad stream but hide it from the user. Let it play silently in the background if necessary.
That'd mean accepting the extra data transfer but still avoiding the psychic damage.
Not the parent poster, but I am similarly concerned about tag spam. I find big tag blocks can ruin the reading experience on platforms that display them in-line with the body text.
Another comment suggested that tags be put in a field separate from the body of the post (and they shouldn't be parsed from the body, either). I think that's the best way to facilitate Lemmy clients to (optionally) hide big tag blocks.