Hacker News new | past | comments | ask | show | jobs | submit | ixfo's comments login

No - toothpaste is in part an abrasive. If it's wetter, the abrasive is less effective at removing biofilm/plaque, and the chemical components are diluted in situ. Your mouth is plenty wet enough as-is.


That implies toothpaste isn't designed with this water dilution in mind, as that is common practice. If I don't wet it beforehand it's too thick and doesn't get distributed as easily.


My experience is that working in an office is _much_ worse for distraction. Even if you're lucky enough not to be in open plan, the shoulder taps and quick chats easily demolish any chance of focus for me. At home I can knuckle down for a few hours and deal with something complex easily.


Personally, I am somewhere in the middle. I use in office days to catch up on gossip I would not have gotten otherwise. The amount of work I actually manage to finish seems higher, but I wonder if it is simply because of how some of my work is structured.

Honestly, I don't think I care that much. I am practically checked out now. I can't imagine I am the only one. I also can't imagine this change making a difference.


Yeah, 100% agreed with this. My team is currently 1 day/week (Thursdays) in-office, and for both better and worse, there are conversations that happen which wouldn't otherwise. A lot of great things come out of those conversations, but also I can reliably write off getting work done that day.


That might also be because you're not in the office every day, people use those days to talk more (scarcity bias). I'm in-office 5 days per week and because we don't have this scarcity of time, there are lots of periods of quiet. When I wasn't in person all the time at this and other jobs it was exactly as you described.

The biggest advantage of being primarily in person is actually that we have fewer meetings. I don't have to schedule 30 minutes on Zoom with someone and if I pop over for a question (when I see the person isn't in deep focus and can contextually grab them which is fantastic as well). If it takes 5 minutes to come to a decision, great - if we need to go over to the whiteboard and take 2 hours to flesh something out; also works.


Environment visibility is easy to get. If you pwn a box which has foo.internal, you can now impersonate foo.internal. If you pwn a box which has *.internal, you can now impersonate super-secret.internal and everything else, and now you're a DNS change away from MITM across an entire estate.

Security by obscurity while making the actual security of endpoints weaker is not an argument in favour of wildcards...


"You can use adblock" is a pretty chunky benefit over Chrome


but "Netflix and my bank actually work in Chrome" is Google's endgame.


the adblock "endgame" will be a self-hosted DNS system that blocks requests to ad-server urls (or return benign responses).

Then the game will switch to encrypted proxied traffic that you cannot block.

Then the adblocking software will switch to the GPU layer, and use machine learning and AI to wipe the region of memory in the GPU containing the ads (and replace it with something benign).

Then the next logical step from likes of google is a fully trusted computing environment - aka, you as an end user no longer control your own machine.

This is entirely predicted by Richard Stallman.


The browser... or the javascript running in it, served from the primary domain you are browsing will just do DNS over HTTP from within the browser, completely avoiding your dns filter


Which follows that the final frontier of ad blocking are AR glasses that use machine learning and AI to block light from ads from reaching your eyes?


Trust. OpenAI's ignored everyone's copyright and legal usage terms for the rest of their training data, what lawyer is going to trust them to follow their contractual terms?


Doing in-database computation can be very advantageous for some applications, and writing those functions in Rust would be fantastic for some uses, not least for the library ecosystem. I did some work on video similarity search with in-DB search which would've certainly benefited.


There were some legal challenges likely for the relevant statute, and doing it this way is much more in keeping with Singapore's approach to keeping politics "in politics".

It's carefully coordinated and done in a way that most conservatives can't really attack. In line with .sg's usual approach to doing things carefully and slowly in a controlled manner.


Assa Abloy's eCliq stuff (similar to this) uses asymmetric crypto for some parts and symmetric for short-lived stuff. The lock cylinders in that system are updated with new CRLs when inserting a key which has been updated, and authorisations are typically pretty short-lived (we use 1 day for most stuff - engineers sync up their key via an app in the morning and then they're set - and only 15 minutes for high security things, which is enough to go find signal and get back if you're in an area with spotty 4G). The keys also pull access logs off cylinders whenever they're inserted and sync up to the server next time they're synced with the app.

Dunno if this system works the same way. We went through a few of these sorts of things before settling on the Abloy solution, and most of the stuff we saw was atrocious from an infosec perspective (let alone physical). The Abloy system uses CR2032s in keys, which last a year or two, whereas this seems to do some sort of low-power networking off of mechanical energy harvesting?


It's enabled by default, actually, but otherwise about right.

https://www.blocked.org.uk/ is a useful resource on this front.


Unsure about "enabled by default". I don't think I've ever been offered (explicitly) a parental for my home ISP (not EE) that I opted out of. Archive.org isnt blocked on my home internet.

Archive.org is also available on my EE phone (when using mobile connection) - it's possibly I explicitly opted out of parental control filter, but I don't think I have. I'm less sure about that.


GiffGaff's is enabled by default. I hate the way they (all) phrase it too, like you can disable it if you want to access 'bad stuff' - no, I just want not to be told what I can and can't access, 'no filter', one less place for anti-privacy logging potential etc.


EE's Content Lock is enabled by default, and is called out in the article itself. To opt out of Content Lock, you must undergo age verification, either via ID checks in person at the store, or via a credit card.

Please note: All new and existing accounts with Content Lock enabled have the "Moderate" setting applied by default. [1]

[1]: https://myaccount.ee.co.uk/app/anonymous-content-lock


QGIS will, for raster basemaps, fetch the detailed version to get you your high DPI detail but this of course involves stitching together lots of tiles from the basemap's lower zoom levels - which then have small labels. For raster maps which are not labelled, it makes complete sense and produces a much better result than the alternative (picking the "scale based" zoom level and interpolating).

This is kind of the only "right" answer when dealing with raster basemaps. It's either pixellated or going to be rendered "too small" for the zoom level.

Vector basemaps don't have this problem, and QGIS supports them, so that's the way to go if you can get data. QGIS can then render at the required DPI in full clarity but with elements scaled/positioned appropriately.


> Vector basemaps don't have this problem

I was about to firmly disagree, but perhaps my issue is that I've been assuming XYZ tiles were vector. Maybe _some_ are vector, based on the connection? If I'm remembering right, I imported a load of XYZ sources, and then never thought twice about them. I should have been more discerning. I'll look deeper into getting some proper vector basemaps.

> This is kind of the only "right" answer when dealing with raster basemaps.

I believe ArcMap uses rasters (when you choose the simple "add data" feature and one of their pre-selected basemaps), but they still render the labels appropriately when you export.


Here are a few workarounds for raster tiles [0]. You can either:

- limit the maximum zoom for raster tiles layers

- use higher resolution tiles (if they exist @2x or @4x)

- lower the DPI in Layout Settings -> Export settings (it should not impact vector layers)

- user vector tiles

[0] https://gis.stackexchange.com/questions/286167/qgis-gives-di...


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: