> Wetting the filter gives you a more "accurate" result, but you'll get a consistent cup of coffee either way if you commit to either always wetting it or not doing so.
The big difference that wetting a filter has is that certain filters have a slight taste associated with them. If you wet the filter first and throw that water away you get a cleaner/brighter cup without the paper filter adulterants.
I can definitely taste the difference between slowly pouring over and not, but so far I have not been able to taste the pre-wet filter. I’d prefer not to gain the ability either because there’s only so much time in the morning.
One of my favorite bagel shops is barely making payroll during this shutdown, and only because they are heavily innovating how they keep customers.
They are now offering meal kits, so you get a meal for two to four people in one easy go, they started shipping via USPS, and they are doing local deliveries. They make their own in-house butter, cheese and cream cheese so their kits do fairly well.
They are also increasing what other items they are selling, such as adding bread to their lineup. Which is absolutely fantastic.
But it's still hard for them, with the reduction in people coming in and sitting around they don't get people buying a bunch of coffee or having breakfast and then lunch while chatting. They have had to furlough some of their staff, and I really hope they make it through, because another favorite restaurant of mine is going under, they simply can't afford to keep going, even with a loan that would help pay salaries, there are other contracts and payables due that simply can't be covered with enough loans... loans against what collateral?
One of my favorite bread shops is basically in tears on instagram due to this thing. They've tried a few approaches to improve sales but they're basically closing shop for now.
I doubt that this is going to be an issue for applications using ReactNative or other solutions to package websites as applications.
For applications that have you add it to your home screen using the app icon, it may be more of an issue, but why wouldn't you sync that data back up to the server?
Yes of course if you're running a business then you're getting users logged in ASAP. There are other models of software development, however. Even if you're in the commercial sector, some users may be less eager than others to sign up for your fine service. Should you preemptively suck in their data, whoops I mean back up their data, without telling them? It seems there could be several responses to that question...
It's fine that Apple don't want to support this valid mode of app distribution and use. It is a valid mode, however.
It seems that the server running on the other end doesn't properly match the certificate from the SNI if the domain sent by the browser is a FQDN (i.e. ends in a .)
The relevant RFC says not to send a trailing dot in SNI. Browsers should probably trim the dot out if present. Maybe they aren't doing so because it causes some unexpected compatibility mishap, maybe in reality it rarely causes any trouble so nobody got around to it.
> "HostName" contains the fully qualified DNS hostname of the server, as understood by the client. The hostname is represented as a byte string using UTF-8 encoding, without a trailing dot.
git blame suggests the change was made 15 months ago, though that doesn't take it to account time to publish.
Which I guess just goes to show that it can be tough to find information on the docs, despite them been relatively decent as far as docs go (in my opinion).
The big difference that wetting a filter has is that certain filters have a slight taste associated with them. If you wet the filter first and throw that water away you get a cleaner/brighter cup without the paper filter adulterants.