The readable store takes a function as a second argument which has its own internal set method, allowing us to wrap any api, like Xstate or Redux that has its own built in sub­scrip­tion model but with a slightly different api.

Most simple example: <script> import ChildComponent from './Child.svelte'; </script> <style> .class-to-add { background-color: tomato; } </style> <ChildComponent class="class-to-add" /> ...compiles to CSS without the class-to-add declaration, as svelte currently does not recognize the class name as being used. I'd expect class-to-add is bundled with all nested style declarations class-to-add is passed to ChildComponent as class-to-add svelte-HASH This looks like a bug / missing feature to me.

The problem with working around the current limitations of Svelte style (:global, svelte:head, external styles or various wild card selectors) is that the API is uglier, bigger, harder to explain AND it loses one of the best features of Svelte IMO - contextual style encapsulation. I can understand that CSS classes are a bit uncontrollable, but this type of blocking will just push developers to work around it and create worse solutions.

This property makes the element so that it no longer seems to exist.

Reactive statements run immediately before the component updates, whenever the values that they depend on have changed.

Who needs a cookie consent banner? Any site or app running non-exempt cookies or scripts that could either:

have EU based users (i.e any website running cookies that isn’t actively blocking EU based users);

Even so, the inline function is still created on every render, useCallback() just skips it.

The bug won’t be fixed today…and by next week, I’ll have forgotten about it - but some time in the future, before our software “goes gold” and gets shipped out to the public - we’ll search through the entire million lines of software for the word “FIXME” - which is unlikely to appear in any other context BECAUSE it’s not a real word!

In cryptography, deniable authentication refers to message authentication between a set of participants where the participants themselves can be confident in the authenticity of the messages, but it cannot be proved to a third party after the event.

It may be the case that several sufficient conditions, when taken together, constitute a single necessary condition (i.e., individually sufficient and jointly necessary)

Its purpose is to decrease the reliance on privacy policies and enhance the ability for people to share and control personal information.

It’s useful to remember that under GDPR regulations consent is not the ONLY reason that an organization can process user data; it is only one of the “Lawful Bases”, therefore companies can apply other lawful (within the scope of GDPR) bases for data processing activity. However, there will always be data processing activities where consent is the only or best option.

I believe that beginning to distribute tools that patch Firefox and give back power to users and allow them to install unsigned extensions is necessary when an organization is taking away our rights without giving us a compelling reason for doing so.

I know, you don't trust Mozilla but do you also not trust the developer? I absolutely do! That is the whole point of this discussion. Mozilla doesn't trust S3.Translator or jeremiahlee but I do. They blocked page-translator for pedantic reasons. Which is why I want the option to override their decision to specifically install few extensions that I'm okay with.

Thus isomorphic structures cannot be distinguished from the point of view of structure only, and may be identified.

A language that features polymorphism allows developers to program in the general rather than program in the specific. $(document).ready(function() { recordAdModuleData(2964, "impressions","Dictionary Ad"); });

Password reuse is normal. It's extremely risky, but it's so common because it's easy and people aren't aware of the potential impact.

So there's a lot of stuff getting hacked and a lot of credentials floating around the place, but then what? I mean what do evil-minded people do with all those email addresses and passwords? Among other things, they attempt to break into accounts on totally unrelated websites

Want to keep your users? Just make it easy for them to leave.

Our eyes decide our focus of attention and therefore our thoughts and our cognitive load.

While we recognise that analytics can provide you with useful information, they are not part of the functionality that the user requests when they use your online service – for example, if you didn’t have analytics running, the user could still be able to access your service. This is why analytics cookies aren’t strictly necessary and so require consent.

PECR always requires consent for non-essential cookies, such as those used for the purposes of marketing and advertising. Legitimate interests cannot be relied upon for these cookies.

This means genuinely asking for permission — using honesty to win trust by enabling rather than disabling user agency.

“meet the minimal requirements that we set based on European law” — which they define as being “if it has no optional boxes pre-ticked, if rejection is as easy as acceptance, and if consent is explicit.”

All of which means — per EU law — it should be equally easy for website visitors to choose not to be tracked as to agree to their personal data being processed.

Consent to tracking must also be obtained prior to a digital service dropping or accessing a cookie; only service-essential cookies can be deployed without asking first.

When consent is being relied upon as the legal basis for processing web users’ personal data