svl

I don't own a smartphone. I have never owned a smartphone. There are inconveniences, and big organizations definitely try to push you toward the way of doing things which has the lowest costs for them - but there are no actual blockers. There is always a path involving actual humans, and regular phone calls (or emails or paper forms).

Reactions tend to be wistful variations of "I wish I could" or "but how do you?" - and it's really always about the most trivial inconveniences.

> Now that there is a Steam Deck Native build, is Baldur’s Gate 3 supported on Linux?

> Larian does not provide support for the Linux platform. The Steam Deck Native build is only supported on Steam Deck.

https://wiki.openstreetmap.org/wiki/Tag:roundabout%3Dturbo

https://en.wikipedia.org/wiki/Roundabout#Turbo_roundabouts

https://www.arcadis.com/en-us/knowledge-hub/blog/united-stat...

The setting being greyed out indicates that the entire functionality is disabled, and the value of the setting is irrelevant. That's a common pattern in Firefox settings when some other setting invalidates the current one. In this case, it's most likely because you have "Allow Firefox to send technical and interaction data to Mozilla" unchecked.

The full PDF with the investigation results e.a. as sent to clearview: https://www.autoriteitpersoonsgegevens.nl/en/system/files?fi...

Here's the list of all posts from the last month which are primarily about this. (There are also daily roundup posts, and lots of small and relevant tidbits in there, too.)

  https://file770.com/chengdu-worldcon-releases-2023-hugo-nomination-statistics/
  https://file770.com/2023-hugo-nomination-report-has-unexplained-ineligibility-rulings-also-reveals-who-declined/
  https://file770.com/chengdu-hugo-administrator-dave-mccarty-fields-questions-on-facebook/
  https://file770.com/hugo-controversy-hits-mainstream-news-a-chengdu-vice-chair-comments-in-social-media/
  https://file770.com/zimozi-natsuco-guest-post-the-hugo-awards-evil-fall-is-a-watered-down-affair-and-certain-issues-to-watch-out-for/
  https://file770.com/dave-mccarty-makes-statement-about-his-facebook-responses/
  https://file770.com/worldcon-intellectual-property-announces-censure-of-mccarty-chen-shi-and-yalow-mccarty-resigns-eastlake-is-new-chair/
  https://file770.com/decoding-the-tianwen-project/
  https://file770.com/the-2023-hugo-awards-a-report-on-censorship-and-exclusion/ (the big one)
  https://file770.com/2023-hugo-awards-related-statement-by-kat-jones/
  https://file770.com/diane-laceys-letter-about-the-2023-hugos/
  https://file770.com/glasgow-2024-announces-kat-jones-resignation-as-hugo-administrator/
  https://file770.com/chengdu-worldcon-wont-account-for-sponsorships/
  https://file770.com/cheryl-morgan-dave-mccarty-resign-from-wsfs-hugo-award-marketing-committee/

However, there was also controversy about this, as a very large number of those votes lacked an address (a minimal safety feature to give some indication that votes belong to distinct people). The responsible committee decided not to count them, but was overruled. If it wasn't for that, Chengdu wouldn't have won the bid.

His only fault was saying something impolitic at the wrong time, which people feared would be misunderstood due to his position as Chair. (You can see the difference in censured/reprimanded and in the reasoning behind it, but it's easy to skip over that and just retain the list of names. Kevin does not deserve to be lumped in with the others!)

[1] https://www.w3.org/TR/using-aria/#rule1

I can say something more sensible wrt your GDPR and "cookie" questions:

The GDPR has one overarching principle: "data minimalisation".

There are no requirements to preserve things like access logs, but rather the opposite: you should only retain personal information for as long as you _need_ it - and then once you no longer need it, you should remove it. And while you have the information, you should take meaningful steps to secure it, where the definition of that changes based on best practices over time.

The important thing here is that you think about what information you need, for what purpose (so something specific like "prevent abuse" rather than "it could come in handy at some point"), and then consider the tradeoff between privacy of your users and your own need for the information (and document this thinking in some way, so that you can later prove that you've done so).

So for those access logs, write down that you log e.g. ip address, timestamp, UA string, referer, visited page (possibly including querystring with search terms), that you retain this information for 2 weeks, maybe that you then aggregate it in some ways, and that you'll delete the information after this time. Your purposes for doing this are probably insight into usage patterns and detecting and fighting abuse. You're explicitly not connecting these logs to other data sources to identify specific visitors, nor sharing this information with any third party, so you believe the privacy impact for your visitors is minimal.

On your website, have a page (accessible from anywhere, so e.g. linked in the footer) that says the same. Specific wording effectively doesn't matter, but what does matter is that it's understandable by your average visitor.

As for cookies: "Functional cookies" (shopping cart, "remember me" function etc) you can set without any permission. "Tracking cookies" (advertising, analytics, etc), you can only set based on explicit and voluntary permission (visitors need to be able to say "no" as easily as you say "yes", without negative consequences, and if they say give permission, they need to be able to withdraw it just as easily at a later date, so one-click in the footer or somesuch - they also need complete and understandable information what they give permission for, so put that in the question, and link to a similar page as above for the GDPR).

It's common to such a degree that many of the shipping forms on webshops have a dedicated field to indicate that you don't want this, though I've never felt the need to use this; definitely more convenient to walk over to the neighbours than to a pickup point.

They explicitly call out the summer holidays effect above the first graph: "Generally, MAU fluctuates over the course of a year, dropping in the summer months and during holidays." So comparing the peak of Jan 2019 to the low of Jul 2021 isn't giving a good idea of the total loss.

  Jan 28 2019: 253.9M
  Jan 27 2020: 229.5M
  Feb 01 2021: 219.7M

  Jul 22 2019: 224.2M
  Jul 20 2020: 214.1M
  Jul 19 2021: 200.4M

I do remember it being the only decent option in the store. I guess other people have other priorities in kettles, for all those other models to stick around?

These aren't things where you can just scan the CSS of the top websites to find out if they're being used. These are things where you'd have to do visual comparisons to the output of at least two other browser engines to determine if you end up with the same result.

Building a browser engine from scratch is imho more doable now than it's ever been before (excepting EME), due to the insane effort by the WHATWG standards to truly describe what is actually happening in browsers (rather than coming up with some theoretically pure description of what is envisioned to happen), and the similar level of detail on the CSS side to the myriad interactions between properties, along with the huge set of testcases for all of that.

Yes, there's _a lot_ - but compared to how loosely specified it all was in the past, when the instruction for building a browser engine was: "reverse engineer the bugs the dominant browser engine of today made in reverse engineering the bugs of the dominant browser that came before, and emulate that to your best ability", anyone starting from scratch nowadays has a way better chance at succeeding.

One trick we're using which you might care to copy over (and improve upon) is a linear gradient to fake the pages. I think for thin books, I prefer your white version, but for thick books, it feels pretty sterile.