As a recent YT premium-tryer, it's amazing how many ads they put in that aren't obviously adverts - comparing between non-premium and premium browsing.
Not sure I'll keep YT premium beyond the free trial, until I find more decent content producers. Even then, it's skipping those video's paid promotion segments.
So it's like paying for a streaming platform to not get ads... But still getting ads
towerful
Even the shitty mobile ads of "someone watching prerecorded gameplay and commenting it".
How obvious can you be?! "Oh wow, these 2 different people playing EXACTLY the same and saying almost the same thing".
That's not an ad.
Never mind that the gameplay in the ad is an extremely minor part of the game. The rest is some sort of city-builder with mtx shortcuts.
It's just whaling
Ah, I think it's like "keep track of 7 items, the 8th might push something else out" ( https://en.m.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two ).
So like mind-map-complexity.
Like, when you are trying to figure out some bullshit OOP inheritance, you are 9 levels deep and have no idea what the original problem was, but you feel like you have made a connection to the solution, but now you have to backtrack everything (or figure out where your last edit was) to try and figure out what that connection actually means and what you have to do now
I haven't tried this yet, but I'm excited for it's potential.
Having a bunch of RES-like enhancements with toggles, and the ability for users to (manually & anonymously, via a button) "submit" their preferences to a central database would be an awesome way to gather Lemmy user feedback on various upcoming features.
This would give fantastic options for Lemmy developers to implement, popularity of features, and easy ways for users to choose what they want (as long as any permanent Lemmy implementations come with an enable/disable toggle)
If the router/gateway/network (IE not local) firewall is blocking forwarding unknown IPv6, then it's a compromised server connected to via IPv6 that has the ability to leverage the exploit (IE your windows client connecting to a compromised server that is actively exploiting this IPv6 CVE).
It's not like having IPv6 enabled on a windows machine automatically makes it instantly exploitable by anyone out there.
Routers/firewalls will only forward IPv6 for established connections, so your windows machine has to connect out.
Unless you are specifically forwarding to a windows machine, at which point you are intending that windows machine to be a server.
Essentially the same as some exploit in some service you are exposing via NAT port forwarding.
Maybe a few more avenues of exploit.
Like I said. Why would a self-hoster or homelabber use windows for a public facing service?!
What a great origin. I Googled it, and it now means "to add your opinion".
- Seinen Senf dazugeben
Literal translation: To add your mustard to it.
Actual meaning: To give your opinion on something./To give your two cents.
Where there are sausages, there also must be mustard. If you want to ask someone for their opinion and sound like a fluent speaker when doing it, you better invite them to add their mustard.
https://www.mondly.com/blog/german-idioms/
In the process, I found some other great German proverbs with hilarious literal translations.
Literal translation: To talk around the hot porridge.
Literal translation: To ask for an extra sausage.
Literal translation: I believe I spider. (Edit: I believe I spin, see comment).
Literal translation: To have tomatoes on one’s eyes.
Literal translation: I can only understand ‘train station.’.
Literal translation: You’re walking on my cookie.
Literal translation: The bear dances there.
Literal translation: Everything has an end. Only the sausage has two.
But, I guess that's always the case with idioms. Their literal translation/meaning is useless. Regardless, I find German ones particularly titular
How many people are running public facing windows servers in their homelab/self-hosted environment?
And just because "it's worked so far" isn't a great reason to ignore new technology.
IPv6 is useful for public facing services. You don't need a single proxy that covers all your http/s services.
It's also significantly better for P2P applications, as you no longer need to rely on NAT traversal bodges or insecure uPTP type protocols.
If you are unlucky enough to be on IPv4 CGNAT but have IPv6 available, then you are no longer sharing reputation with everyone else on the same public IPv4 address. Also, IPv6 means you can get public access instead of having to rely on some RPoVPN solution.
At one point, blue LEDs were super expensive because of their difficult production.
So any product that has a blue LED was considered premium. I guess they were also considered futuristic and high-tech.
Somehow, this is still in the mind of some manufacturers.
All I want is a barely-visible-in-soft-daylight diffused/frosted red or amber LED.
But no, it's always some 5w lensed blue LED at somehow produces a tighter beam of horrendous blue light that's brighter than most flashlights.
Oh, so if a judge has a vested interest in more than 1 party, then they should recuse themselves from the case.
Good to know where the line is
Absolutely.
And casually, that's exactly what I do. To be honest, casually I haven't encountered any (I don't think...).
But for work stuff, sometimes I don't have a choice. I guess I'm just thankful it doesn't require edge IE compat mode, or even IE itself
Not having control of the core codebase, and branching/tracking based on 1 (declared) legacy feature could lead to huge amounts of work and issue in the future.
Manifest V2 spec is defined, manifest V3 spec is defined... They can be developed against.
JS-whatever-spec is defined, CSS-whatever-spec is defined, HTML-whatever-spec is defined... They have industry standard approved specs (even if they can be vague in areas). They can be developed against.
They have defined spec documents that can be developed against.
Firefox has control and experience of how they implement those specs.
Chrome forks do not have control of how those specs are implemented.
So if chrome changes how things are implemented, forks might not be able to "backport" for manifest V2 compatibility, and might find themselves implementing more and more of the core browser functionality. Browsers are NOT easy to develop for the modern fuckery of the web.
Firefox hopefully does have that knowledge and ability to include V2 manifest backwards compatibility in future development without impacting further spec implementations.... It seems like Google is depreciating V2 to combat ad-blockers (ads being their major funding revenue)
There are already very slight differences how Firefox and Chrome interpret all these specs. I've noticed a few sites & plugins that just work better (or just work) in Chrome. Which is why I still have (unfortunately) an install of Chrome.
I remember watching some video, falling asleep for a few hours, then waking up to a livestream of an ad. One of those "skip after 5s" but it was a livestream, so it just kept playing. I couldn't believe it!