I think it’s a major feature gap that Gmail (paid or free) cannot create filters on headers.
I also can’t do wildcard filters on “to” or “from”. For example, in my GApps I have it set up to route all emails not associated with a specific user to my primary user. So that it’s easier to make throwaway emails. I want to filter all to:`X.X@domain.tld` to a certain folder. No can do.
For many years I’ve been creating filters on free Gmail for to:, from:, subject:, etc.
I set them up on desktop web.
Perhaps there is something more specific you’re trying to do?
> a major feature gap that Gmail (paid or free) cannot create filters on headers.
You can create filters on header fields like from:, to:, and subject:, so I am guessing you mean something different than “cannot create filters on headers”?
Mail headers also include to:, from:, subject:, etc, as well as more obscure items too, which is why I think OP commenter meant something very different than “cannot filter on headers”.
Also, more items that might help OP (as I can’t edit parent comment) - they mentioned wanting to use wildcards on to: field. Those header fields do allow specifying just part of the header, like just the domain, or one part of the to address. (But those match at word boundaries and I’m not aware of being able to match sub parts of words or more complex items.)
Regardless, I don’t think I’d call this a “major” feature gap - maybe minor or more of a niche feature.
This is definitely not true for general .us domains.
I registered one a year or two ago. And assuming my normal default Whois privacy was being applied (I clicked through too fast. Wasn’t paying attention)
I noticed my mistake after the spam bots started hitting me up for their web design products.
I feel like splunk’s business model favors a healthy system and gives major disadvantages to an unhealthy one. What I mean in an example: when the system is unhealthy, I know it because all my splunk queries get queued up because everyone is slamming it with queries. I hate it.
But I’m stuck in knowing how to move some things to Prometheus. Like say we have a CustomerID and we want to track number of times something is done by user. If we have thousands of customers, cardinality breaks that solution.
This gets even worse if you have a language with one process per CPU as you can get clobbering other values on the same instance if you don't add fields to uniquely identify them.
We got a lot of pushback when migrating our telemetry to AWS after initially being told to just move it when they saw how OTEL amplified data points and cardinality versus our old StatsD data.
You probably need less cardinality than you think, and there are a mix of stats
that work fine with less frequent polling, while others like heap usage are terrible if you use 20 or 30 second intervals. Our Pareto frontier was to reduce the sampling rate of most stats and push per-process things like heap usage into histograms.
An aggregator per box can drop a couple of tags before sending them upstream which can help considerably with the number of unique values. (eg, instanceID=[0..31] isn't that useful outside of the box)
> That would probably not trigger anyone’s midnight pager, but it would make it clear that relying on the deprecated functionality is a bug lurking in the code.
How do you know? This is a wild assertion. This idea is terrible. I thought it was common knowledge that difficult to reproduce, seemingly random bugs are much more difficult to find and fix than compiler errors.
If you're ready to break your api, break your api. Don't play games with me. If more people actually removed deprecated APIs in a timely manner, then people will start taking it more seriously.
> In case the sarcasm isn’t clear, it’s better to leave the warts. But it is also worthwhile to recognise that in terms of effectiveness for driving system change, signage and warnings are on the bottom of the tier list. We should not be surprised when they don’t work.
I thought I had read it. :) I thought the three `* * *` at the bottom was indicating I was about to start reading suggestions for the next article. So definitely a "Woosh" moment for me :D
Yeah, I agree - this sort of intermittent failure could be incredibly hard to track down, and will absolutely fuck with people's faith in their CI systems as well - a flappy test is the absolute worst kind of test.
I agree, maintainers should just break the API if they're going to do it.
At the same time, it's crazy that urllib (the library mentioned in the article), broke their API on a minor version. Python packaging documentation[1] provides the sensible guideline that API breaks should be on major versions.
I tried to use a USB-C HDMI dongle I had. But I assumed it was because the switch 2 was looking for something that could deliver enough power and actively cool it, like the first party dock does.
Thst is a badly phrased question. "What languages do you speak?", would be the question to ask.
Because even of you were thinking about spoken languages, what does "knowing" mean? I "know" Hungarian exists, I know how Hungarian sounds like, I know how Hungarian words look like, but that doesn't mean I speak or understand it. Now if it was clear they meant apoken languages we could infer from the context they want to know about our skills with different spoken languages and didn't read our CV, which at least where I am from always contains a languages level with a skill level (e.g. German A1, English B1)
Pretty amazing that this is still around. I used to be active on Elendor MUSH, but as far as I know it's been dead for years - I poke my head in once every year or two and there are always 0 players online.
Is the server available anywhere or is that too lost to the sands of time?
Sucks when MUD servers eventually shutdown and all of it is lost forever. I’ve found a few on github though and have been archiving as many as I can find.
Switch to a MIPS transflective or e-paper display as on a Pebble or Garmin, OLED and LCD displays on Apple and Samsung watches look pretty indoors (when they're not turned off to save power) but are hard to read outside (without excessive brightness) and are battery gobblers.
Just charged my Garmin Fenix for the first time in... 9 days (it was down at 18%, could get a few more days but it makes me nervous), most of the battery use went to some 11 hours of GPS activity recording and heart rate recording. Could get 30 days if I turned off the features the Pebble doesn't have.
Even Garmin has largely moved to AMOLED screens. They look great both indoors and outside and with modern technology they are not as battery hungry as they once were. Personally I find the battery life on my Apple Watch more than acceptable. I charge it while I’m showering and getting readying in the morning and have never had any issues even though I am a very heavy watch user and often use it independently of my phone.
I used to have a Pebble Time and agreed the battery life with those displays is nice, but honestly it doesn't bother me to put it on the charger every evening.
The only real benefit a longer battery life would have is not needing to bring a special charger if I go out of town for a few days, but I solved that years ago using a power bank that has qi and watch charging pads on it as my travel charger.
If anything, I'd switch back to a Pebble or similar because the Apple Watch does too much and I don't want that much gizmo on my person all the time. But the Pebble reboot products don't do it for me design-wise.
Just a tip with Apple watches: get the battery service at least once during the lifespan of your watch. It's $99 and Apple gives you a brand new watch.
With that battery service the watch should last you about 6-10 years judging by the current status of my Series 4.
Yes, a watch should be able to last a lot longer than that, but I think if you're buying Apple products you already have the expectation of a maximum 10 year lifespan just from software alone with just about the entire product lineup.
As long as it's minor scratching and not big chips or cracks, yes. Another huge plus to the battery service.
Another tip regarding scratches is that the higher tier finishes (Stainless Steel or Titanium in the Series 10) are, in my opinion, worth the price premium solely for the improved screen glass.
Apple barely mentions the spec nowadays, and I'm not sure why they don't tout it. A conspiracy theorist might say that it's because it keeps your watch looking new longer so they'd rather you be buying the cheap one frequently.
The sapphire crystal screen is the killer feature that justifies the upgraded models more than anything else: it's something like a whole extra number higher on the Mohs scale for hardness (scratch resistance).
I buy them on the refurbished store to lessen the pain of their ridiculously inflated price.
You may have an app draining your battery. Was having the same issue with my watch, I deleted a few apps and all of the sudden my watch was better. I can’t tell you what app was because it was just luck. I was creating space on my phone when it happened.
I also can’t do wildcard filters on “to” or “from”. For example, in my GApps I have it set up to route all emails not associated with a specific user to my primary user. So that it’s easier to make throwaway emails. I want to filter all to:`X.X@domain.tld` to a certain folder. No can do.
It just feels restricted.
reply