skysight-inc/HackerNews huggingface dataset:
Show HN: Metriport – Customizable personal analytics tool for health, and more
Hello HN! We're a new startup out of Vancouver, BC, Canada consisting of 2 people. We've spent the past 3 months building our product from the ground-up using Flutter/Dart, and are finally ready to start sharing it with the world!

The idea to build Metriport was mainly driven by our own need for such a tool. There were a bunch of existing apps for journaling, habit tracking, water intake, health device integration, spending tracking, etc, but nothing that met our requirements:

• Everything in one app: nothing would let us track whatever thing we could think of, with the data visualization, correlations, and insights to boot. Maybe a user wants to journal, but wants to track their focus rather than mood? Maybe they don't care about journaling at all, but they want to see how their caffeine intake influences their resting heart rate, or anxiety levels? With Metriport, we are building a platform that's as robust as possible to cover any personal data tracking needs.

• Customizability: we wanted an experience that's personalized to us, and all other apps felt too hard-coded. If an app did have a friendly avatar, we couldn't change what questions it was asking us. If an app had data visualization, we couldn't change the colors or type of the chart. If an app had a mood tracker, we couldn't change the name of the categories. We made sure to make customization a priority with Metriport.

• No paywall spam: we noticed that many apps offered very limited functionality in the free versions, and would use manipulative paywall tactics to get any actual utility from the app. As such, we wanted to provide as useful of an experience as possible for both free and paid users. We will only be providing additional features for all users as development continues, and will never hide existing free features behind a paywall in the future.

• Privacy: we are privacy freaks, so we wanted full control over our data and to know how it's being used. We are shocked that there are very popular journaling and habit tracking apps out there that don't have a single mention of encryption, and force you to use their cloud storage by default. That's kind of scary. So, we have the option for data import/export/deletion at any time, store all data locally by default with optional encrypted cloud backups/restores, and use a bare minimum amount of anonymized analytics with opt-out ability at any time.

We're just getting started, and are hoping to get lots of feedback from the HN community on what we're building. As this is a highly personal tool, we want to make sure we're building the best experience for every one of our customers.

Thank you all very much in advance, and we're looking to hearing back from you!
I (genuinely) wonder, how often have you paid authors for their articles/blog posts?
You would need more than one to do a rolling restart. Alternatively to do it with one instance of a software load balancer is a bit more work, spin another instance up and update DNS. Wait for traffic to the old one to die as TTLs expire, then decommission.

But I agree it isn't as easy as a in place upgrade.
> Isn't tackiness heavily context, culture, and timeframe dependent?

All the more reason to not require them?
Wow, this was quite something. The fact that the emergency door latches are on the inside only raises many questions, as does the fact that the hood is so unwieldy. It's confusing to me that the hood was designed to be opened by 2 people and also that during "normal" operation it can easily damage the bumper. I realize they don't want people doing it themselves, but even for the mechanic this seems extremely annoying. Serviceability is clearly not a top value for these cars but it seems like it's not even considered at all.
Thanks! TIL! That's a much cleaner way of doing it.

Regarding keeping the file, if memory serves the "real" pipeline had some `tee`s in it. I recreated this much more recently to make a GitHub repo of funny code snippets (https://github.com/MaxBondABE/one-thread-crashing/).

You reminded me of a different toy I made many years ago. I created FIFOs for files that you might try to read when exploiting an arbitrary file read in a web app, say /etc/www/apache.conf (if that's the right path - it's been a while since I've configured a web server!) and I'd have a program that opened them. This would block until someone opened the other end of the FIFO, at which point I'd raise an alarm (which was just a print statement).
You forgot to include time to park.
I’m not sure what your point is here - you could also create a new Google account per website or simply use an email address.

The author advocates using third party services such as meta mask, who would need to be trusted.

How do you implement it without any third party site.

If we are talking about likelihood it’s unlike you’d be banned from Microsoft/Facebook/Google for no reason too.

Furthermore as the administrator how you stop bad actors?
If you're remotely interested in this sort of thing, definitely check out the VESC project (https://vesc-project.com), which is kind of the secret sauce that makes this sort of thing accessible to mere mortals.

There are a lot of hardware variants at different price and quality points but it's a great, hackable, open-source (GPL3) motor controller for smallish motors (in the 24-44 volt range—they typically use a gate drive/power supply controller with a 60V limit).
This page made me smile almost like when I had only started to use internet. Expected to see such a subthread before wanting to post similar.
Most Vietnamese in America are from South Vietnam or descended from those from there, so that's probably one of the bigger reasons for their offense.
I could see this working well for teams that are engineering led and where customers don't expect a ton from the software. If you're trying to ship fast and get to market quickly, then fine, skip the tests, skip the code review.

Once you have lots of engineers shipping many different apps and need to work within and across teams. This system is not going to be fun. When a nasty bug ships and you're responsible, you'll wonder "should I have requested review for that one?" When one of your colleagues ships a few bugs that force you to paged during your on-call. This system is likely to erode trust on both ends. IMO, a no code-reviews model is going to stunt junior engineers career growth as they will not be performing what is common practice on software engineering teams. It's also going to keep out many other stakeholders who may wanna weigh in on the software you're delivering, be it UX, Accessibility, Security, Documentation, Product experts. Pull requests keep others on your team in the loop and educated.

I agree that this model gives you the advantage of speed, but I don't think it builds trust. I trust my colleagues and we do pull requests. I don't feel like I'm missing trust because I can't push to `main`. Code reviews have very little to do with trust. They serve as a communication tool and serve a tool to give the best possible experience for customers and provide an opportunity for alignment with our colleagues.
Most service techs turn off the car (ICE) before working on it. So it's usually very clear if your hand can be caught by a fan belt or not (and not deadly if it is). When turned off and 12v battery disconnected, a car is pretty darn safe.

Are you sure you can sense high voltage / high amperage as well?
I'm thinking more of their cold war strategizing, but I also ask you, have you ever met an American QAnon enthusiast? ;)
Do you have a link to these millions of data points?
Sorry dumb question, but could he not get a heart transplant?
This is already possible. You can configure whether you want inetd style socket activation (where systemd calls accept() and passes you the client socket)), or just systemd listening to the socket (where systemd passes you the listen socket and your binary calls accept()).

https://www.freedesktop.org/software/systemd/man/systemd.soc...
Honestly, I'm loving this process because you discover so many situations where the answer is "Why not? Uhhh shit, I don't know, actually. You're right, this is stupid. Why does everyone do it this way?"

Mine is 2, so most of the situations so far are just about English rules. (Though every language has stupid inconsistencies)

But there are many things like this in the world. I'm looking forward/dreading trying to balance "OK, from first principles, you're right. But in order to exist in society, you need to do something differently. It's important to recognize when you need to try to fit in. And also important to recognize when it's worth breaking those rules. And even if you choose not to break them, you should be aware of the underlying purpose or lack thereof"

I think it's an impossible task. My kid is going to hate it. I'll do my best.
> drive-by take-down by someone with none of the context.

If this is an issue in your workday, you should bring it up with management or the individual rejecter. If someone has the authority to kill PRs, they should also be required to put in the effort to understand it and/or be available for discussion at an earlier stage of the development process. PRs shouldn't ever be rejected without mutual agreement - neither internally in an organization, or in an open source project.
I'm a bit torn between these as none is suiting all of my needs:

http://ecere.org/
https://haxe.org/
https://dlang.org/
and ofc ...
https://vlang.io/

All can compile to C and I find it somewhat important as would be very happy to share same code base with microcontrollers (SDCC), Android, Linux, Windows and web wasm. Unfortunately (to my knowledge) not all offer optional or selective garbage collection, some look immature and so on :-(
It could be used for that obviously, though do we have any evidence? Who would the AV vendors sell the secrets to, and how? (I guess it's not a surprise I wouldn't be in those meetings, but you'd think there be a whistleblower somewhere?)
a competitor won't be enough, the whole supply chain is made by companies which are single point of failure (the reason why europe can't afford to say "ASML only sell your machines to EU fabs" is that one of the key ASML supplies is US.. and without them no machines...).
Every time I open a recipe online these days, I sigh so loudly out of desperation of what I need to scroll through to get to the actual recipe. And that is before I do the cookie dance.

I guess you guys heard my sighs!!! Amazing. Thanks!
Those are great to have. I will say that 3100mAh is pretty low and wouldn't even fully charge most smartphones. 20kmAh batteries can be purchased for less than $100, and 10k-15k mAh for less than $50.

A good idea to have just in case. :)
cloki can be used to read metrics out of any CH table so it should work fine.

we also just introduced experimental support for ingesting OTLP/ZIPKIN spans and a tempo-compatible API in cloki, looking for testers to validate this feature:

https://github.com/lmangani/cLoki/wiki/Tempo-Tracing#clickho...

Internally trace spans are stored as tagged JSON logs, meaning they are available from both Loki and Tempo APIs and can be used from pretty much any visualization, too!
It’s not justified, I don’t claim it is. It should be condemned, I just feel like the term “just following orders” has a bit of a loaded Nuremberg connotation to it.

I guess I’m accusing the parent comment of hyperbole more than being “wrong”.
Even just a podcast player with bookmarking (including transcript and links as you said) would be massively helpful. The amount of time I’ve spent trying to track down relevant/interesting chunks of Radiolab episodes alone to share with others is not inconsequential.
Were small apartments of yesteryear more generous with their kitchen sizes?

The parent comment said kitchens are getting smaller and smaller but I'm not sure if that's actually true. I lived in quite a few houses (middle / lower-middle class) growing up and it seemed like the older homes all had much smaller kitchens than the ones that weren't as old.

Maybe that is happening for apartments for singles and DINKs living in urban areas where your lifestyle may be shifting towards eating at restaurants more than at home, but especially for families with kids, the trend definitely seems to be larger kitchens and kitchens that are more integrated into the home.
So, web3 regularly gets updated into the front page, only to be utterly trashed in the comments session.

What gives?
Federated/Decentralised identity/authentication is a solved problem.
For example, this is essentially OpenID.
Unfortunately this entire concept failed to gain traction.
Great read, love how it has a display. Something for the kings of the era to be amazed by.
Why for the cancer research use?
> And now I've discovered that vim spell check skips words with leading markdown symbols like `*randical`. I'll have to dig into that more.

Taking a quick look, for me it seems that (Neo)Vim spell check skips anything in italics or bold. No highlights whatsoever anywhere in that region. Definitely not something you want to realize _after_ publishing articles!

Edit: Considering the comment about using :syn off, seems like this is probably a conflict of some kind with the way Vim actually italicizes/bolds things in terminals that support it, now.
Those shirts are dumb, but at least there's an explanation: They're typically associated with premium brands that have a long, rich history in the fashion industry (usually by making lots of products that are quite a bit more challenging than the t-shirt).

There is no such history with random monkey NFT pictures.
Paperless Post|NYC,REMOTE(US)|Senior Software Engineers(multiple positions: Front-end, Back-end, Engineering Manager)|Full-Time|https://www.paperlesspost.com/about/jobs/

Hi! We’re Paperless Post and we help people celebrate moments that matter with our customizable, design forward digital invitations. The PP Engineering team, a highly collaborative group of developers and technologists, is charged with building and refining a consumer-facing product that millions of people interact with each month. Our individual feature teams each focus on a unique piece of the user experience and are made up of engineers, product managers, QA, and product designers. Our open roles are below:

Engineering Manager - https://www.paperlesspost.com/about/jobs/?gh_jid=3476369
Sr. Software Engineer, (Front end) - https://www.paperlesspost.com/about/jobs/?gh_jid=3743495
* Sr. Software Engineer, Services (Back end) - https://www.paperlesspost.com/about/jobs/?gh_jid=3164592
Sr. Software Engineer, (Software-Action) - https://www.paperlesspost.com/about/jobs/?gh_jid=3683001
Sr. Software Engineer, Graphics - https://www.paperlesspost.com/about/jobs/?gh_jid=3394349

If your interested, please shoot me an email at: recruiting@paperlesspost.com
inetd style socket activation (iirc) forks a process for every connection.

So, simply replacing the binary on disk will cause all new connections going forward to use the new binary, while existing held connections (with in-memory references to the old binary's inode) will finish the operations. Once they are done and all references to that inode are gone, the blocks referencing the binary will be removed.
Used both an Apple Watch latest and the samsung gear watch latest (I switched to android over christmas). Tracked using their workout watch apps.
You can get macros out of rust or julia or other languages other than LISP as well.

It is also arguable that overuse of macros leads to less readable code since you wind up inventing your own personal language the more you do it, which requires more of a learning curve to work on it.

There's a large advantage to sticking with verbose idioms that are common and built out of a relatively few building blocks rather than building a meta-language which is terse.

At the same time I'm not saying don't have macros, but they should really be reserved for more extensive heavy lifting, not a pile of tiny ones used all over the codebase to make it terse.

A well written codebase should read more like Hemmingway at an 8th grade reading level using simple constructs from the base language which are put together, generally using programming design idioms which are common and terminology which everyone shares. There shouldn't be a lot of "what does this macro do and where it is it defined?" questions on every other line.
I dunno, I think it's more accurate to say that it ended terribly in Episode 9 when Abrams returned, shrugged, and ignored everything that had happened in 8. The film where we were given the phrase "somehow Palpatine returned"... :D

All symptoms of staggering mismanagement by Disney, of course. A trilogy with a stupid planned plot arc would have been better than the sequence of "solid but uninspired Star Wars throwback" + "interesting and out there reinterpretation of the mythos" + "but what if RotJ again but dumber?"
“Raise eyebrows” is basically an idiom that means “have skepticism for (what is being told to them)”. I think the standard lay person on a jury would not necessarily be open to a defense attorney attempting to explain that the word “decode” in goes against their base understanding of the word. The defense argument has to overcome the jury’s lay understanding of decode by arguing that although yes, we are revealing information…its not really revealing anything since it was easy to reveal in the first place for someone with the skills to do it.

To use a metaphor—if a state building is closed, but a person with certain knowledge knows that the windows on the building are easily opened by lifting and pulling in a certain way. Then, that person opens the window, enters the building, takes pictures of sensitive information, and later tells the government about the window, then writes to the world later after the government replaces the windows about how easy it was for them to enter and find that sensitive information, would they be guilty of breaking in and stealing information? I think yes.

Even if their intent was not malicious, and ultimately resulted in more secure data, they did something that was not authorized and then capitalized on it after. If the law doesn’t have a caveat for that situation and if the jury is doing its job and doesn’t have an instruction to allow the out, a conviction is likely.
Random, low confidence and trollish, theory: Compiz et al had the opposite effect. The number of different compositor / effect projects increased the already substantial fragmentation of the linux desktop world, and put a large amount of developer energy into things that didn't end up having influence over the long haul.
Suggestion: If the start and destination inputs are left empty, select a random article for both.
Why not just allow bodies (that can be arbitrarily large) with GET requests?
This is a common argument encouraged by the fossil fuel industry but it's not that simple. Climate science operates on a longer time scale so there isn't a single “We did it – Exxon, et al.” note to find but what you can talk about are the probabilities shifting (100 year floods become 20 year floods, etc.) and that tends to happen after most major events. For example, two noteworthy weather events this summer:

https://arstechnica.com/science/2021/07/pacific-northwest-he...
https://arstechnica.com/science/2021/08/europes-july-floods-...

In this case, what I'd look at is whether this event is in line with what the climate scientists have been saying for decades, namely that we'd see more volatility and extreme weather events. This is especially compatible with predictions for the mid-Atlantic region which have called for more big snow events despite generally less snow on average. No, it's not definitive enough that you could use it in a criminal case but it tells anyone that cares to expect higher insurance rates, taxes, etc.
If your code is unimportant then so are your bugs that get into production. So I guess I agree. Don’t waste time writing, testing, reviewing unimportant code.
I’ve never accepted GET with a body but I’ve been burned several times using curl to test APIs. curl and browsers are very different beasts.
> Even though the work product was purchased from the bankruptcy auction, the copyright was still owned by the creators and could not be rendered/released just because they bought a box in auction for $20.

Does the first-sale doctrine not apply here?

https://en.wikipedia.org/wiki/First-sale_doctrine
I don't agree. I've never taken psilocybin, and I'm interested to hear the subjective experiences of folks who have, in addition to reading scientific studies, so this does add to the conversation. If I only wanted to read the study, then I'd subscribe to the Journal of Psychopharmacology.

However, there are some (in my opinion) huge flaws in this study and its presentation:

1. This study was conducted on a small sample (60 people who received the psilocybin, and addition 29 who received the placebo - of whom 4 did not actually complete the study).

2. The study looked at short term effects and followed up at '29 or 85 days', (my emphasis). I'm not sure that I would be comfortable saying there had been 'no detrimental effects' after less than a month.

3. The study limits the scope of 'detrimental effects' to cognitive functioning or emotional processing.

4. The study was supervised and all participants took part in mandatory preparation and therapy sessions.

5. All of the participants were self-selected, and 35 participants had already taken psilocybin out of the 89 total participants (including those who had taken the placebo), which is about 13 times higher than the estimated population lifetime use in the UK.

6. Importantly in conjunction with point 5, participants were screened for pre-existing medical and psychiatric conditions, meaning a highly significant proportion of participants had already taken psilocybin without detrimental effect at least once before, and other non-first time users who had experienced detrimental effects previously would have been excluded from the study.

7. Four participants in the placebo arm did not complete the study, meaning the control group was only 25 people.

8. Efficacy of blinding was not assessed, and given the nature of psilocybin and the fact that up to 41% of the people who completed the study had taken psilocybin before, it seems quite likely that a significant proportion of the participants were unblinded.

9. Particularly worrying in the study is the statement: "An AE [Adverse Event] of substance induced psychotic disorder was reported for a participant who became behaviourally disinhibited during the acute drug experience. After a medical assessment, 2.5 mg oromucosal midazolam was administered. This event was not considered to be an SAE [Serious Adverse Event]." It would be unusual to administer buccal midazolam to someone who was not experiencing any 'detrimental effects'.

In a study which is potentially only looking at 25 people taking psilocybin for the first time[0] at low doses, I don't think we can really discount personal anecdotes, especially when they're clearly and properly presented as such.

[0]: Admittedly worst-case scenario where all of the placebo group turn out to have never taken psilocybin before.
Can somebody explain the "won't eat vegetables" thing? The only place I've heard about this being in issue is in America.
Fair enough, I always take a cab/Uber to IAD, as that cost is far less than the price of parking. And living so close to IAD, I try to fly out of it whenever possible (all work travel, 80% of pleasure travel).
This is probably true but it's quite an angry response to the linked article which is mostly just a joke.