robflaherty

If you use this form instead of the one above it should work: https://motherduck.com/lp/ducklake-lakehouse-table-format-bo...

Browsing a few sites with heavy programmatic advertising I observed requests to these domains blocked. This happens in regular browsing mode without any extra privacy options checked. Includes LiveRamp and Unified ID 2.0.

As the article mentions Trade Desk ad delivery is currently blocked because they use the same apex domain for delivery and ID matching.

- api.id5-sync.com

- api.rlcdn.com

- b1-nydc1.zemanta.com

- check.analytics.rlcdn.com

- di.rlcdn.com

- direct.adsrvr.org

- htlb.casalemedia.com

- ib.3lift.com

- id.hadron.ad.gt - id.rlcdn.com

- id5-sync.com

- idsync.reson8.com

- idsync.rlcdn.com

- img.3lift.com

- lb.eu-1-id5-sync.com

- match.adsrvr.org

- pippio.com

- pix.cdnwidget.com

- pixel.tapad.com

- ups.analytics.yahoo.com

- v2.pixel.newscgp.com

I linked this post because it explains how the lottery works which I thought was more interesting and relevant for HN.

Always liked Reinertsen’s post on reframing tech debt to deferred work.

“When we refer to postponed work as technical debt this automatically biases us to assume that both ongoing and future costs are more certain than they really are. This, in turn, causes us to overestimate these costs, leading us to be overly cautious about deferring work. If it is your intention to bias the decision against postponement, this is clearly the best term to use. However, if you are trying to carefully weigh of pros and cons of postponing work, I’d recommend using a more neutral term like deferred work.”

http://reinertsenassociates.com/technical-debt-adding-math-m...

I see this with Framer sites all the time. Happens in Chrome too.

I know the intent is good (it is!) but this common notion that good design is a toolbox of fun little games really prevents the design function from getting taken more seriously. In the business world at least it ensures our seat at the kid’s table.

Is there a reason we won’t have LLMs that only speak in JSON? These JSON hacks are clever and cool but feel like they’ll be obsolete in 6 weeks.

The OpenAI Cookbook has had an easy to use chat with a PDF app example for a few months.

https://github.com/openai/openai-cookbook/tree/main/apps/fil...

Worth remembering that priority and sequence are not quite the same thing.

There's a useful framework called RICE where you evaluate/score ideas by Reach, Impact, Confidence, and Effort. Sometimes assigning numeric values feels forced so I often use it as "dimensions to be thinking about" rather than a literal scoring system. [1]

There's some great stuff in Reinertsen's Flow book about different sequencing strategies and when to use each. Eg, When delay costs are homogeneous, do the shortest task first. When task durations are homogeneous, do the highest cost-of-delay task first.

[1] https://www.intercom.com/blog/rice-simple-prioritization-for...

The author's framework-"you just start small and only add one at a time as needed"-and given example illustrate exactly the process that leads to too many metrics. Pick a few metrics, add another, add another, add another. If you have 5 teams working on a product you quickly end up in the 50 metrics scenario.

Too many metrics can be a problem but it's not the real problem. The real problem is choosing metrics without any regard for the decisions they're supposed to inform.

When you understand that the purpose of all measurement in business is to reduce uncertainty for a decision to be made, everything comes into focus, and you'll have a natural constraint on your scope of measurement.

> According to the ePrivacy Directive, they should not last longer than 12 months

The quote you keep referencing is false. The ePD says nothing about this.

The ePD text says nothing about a 12 month cookie expiration and also ePD != GDPR

It doesn’t. Or if it does, no one here has yet to explain why.

Can you explain what is invalid about it? The list of functional cookie permissions on the consent opt-in specifically mentions cookies to remember log in details.

“Zoom cookies are firstly written when the user connects to the website zoom.us and accepts the cookies options.”

That was the moment Zoom received your consent to store data transmitted by cookies. Adding a few more cookies to the pile, regardless of expiration date, doesn’t change the agreement.

Rummaging round the cookie bin on uninstall is a nice find and deserves a raised eyebrow but this doesn’t really have anything to do with GDPR.