Hacker Timesnew | past | comments | ask | show | jobs | submit | xahrepap's commentslogin

yeah, i ignored them for years just to see how long they'd play their little game. I finally got sick of it, paid them for a month, downloaded everything, and then canceled/closed the account. Didn't know there was the free option... but oh well. Glad to be rid of them.

So tired of the games everyone plays to squeeze $5 out of someone.


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.

It just feels restricted.


> I want to filter all to:`X.X@domain.tld`

You can filter based on the to: field, yes.

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”?


I think he refers to mail headers. Those are normally hidden away from you, at least on a PC browser you can see them:

1. Open the specific email.

2. Click the three vertical dots (More options icon) next to the "Reply" button.

3. Select "Show original" from the dropdown menu.


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 so much this. Gmail overall is pretty meh and then it has these stupid footguns that make it awful.


I miss being able to skip ads and previews without “this feature is disabled for this disk”.


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.


When my kids were young, we canceled our Disney Channel / etc cable subscription and showed them more PBS and similar.

It was really annoying turning on a show for 30 minutes then for the next week hearing about that new toy they just have to get. It was exhausting.


Honest question, how do you handle high cardinality data points?

Reference to where my brain is at: https://www.robustperception.io/cardinality-is-key/

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.

Is there a good solution for this?


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)


Asking this question got me to stop being lazy and actually try to answer my own question. Mimir being one that caught my eye

https://grafana.com/oss/mimir/


> 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.


Last paragraph of the article:

> 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.


Yeah, totally a woosh moment for me. Read all the way up to the `* * *`. That's on me :)


That last bit was added to the article after your comment, as the author realised the sarcasm had been too subtle for most people to catch.


Most HN visitors won’t read to the last paragraph, so it’s a good thing to emphasize.


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.

[1] https://packaging.python.org/en/latest/discussions/versionin...


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.


One time an interviewer asked me languages I knew.

After I went through my experience with Java, C#, python, etc. he said, “I meant like… Spanish…”


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)

So yeah interviewers can suck at their job.


Oh wow! Didn’t expect to see this piece of my childhood on the front page!

I used to spend hours on telnet playing this game with my friend. What a fun blast to the past!


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.


Archiving is good; all of these games contain thousands of hours of creative writing, and it would be a huge loss if they were all lost to time.

I hope you and others are archiving them, so that at the very least they would remain available in a readonly fashion.


Same. Spent a lot of time in Bree. Haven't been on in over a decade.


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

Search: