j1elo

(Just an objective comment, I'm not positioning here) this honestly puts the "tax the rich more" in perspective. A tiny tax increment to the rightmost column would provide more money than 100 years of all the other pitiful contributions together.

Go to the fundamentals. Assuming that this is low effort, if this is low value, it will die sooner than later. If this is high value, soon there would be incentive for someone to do a clone and charge $1 less to compete.

You can favorite messages, then check them out from your profile page just like you check on your previously posted messages.

Hit on a message's permalink (which is the "X hours ago" link), and in there you'll find the action to Favorite it.

Today I went over a TODO comment from 2007 in a C++ codebase that is still evolving very vividly, year after year. Trust me, for well established projects C++ is there to stay.

Solution is easy, in fact there are 2 solutions:

1. Clear that "might", it either is or isn't. An AI can get you 90% there, maybe the definitive confirmation would be good from a lawyer.

2. None of this matters if you share it from a foreign code forge and an anonymous pseudonym.

Probably! I just haven't seen it working on iOS. I'm mostly on Android, Windows, Linux, and Firefox everywhere.

I use it on Android and it's always been a Bitwarden-specific pop-up that shows up on password fields. Maybe with accessibility mode it would work as you mention? Ok that's a new thing to test.

Instead of overlaying its own UI on top of form fields, I'd like Bitwarden (or any other PW manager) to act as a provider for the underlying system's native fill service, usually the browser, or Android, or OSX. They will always work much better than any 3rd party app.

Is that possible, does that exist?

> Security from websites, installable software, physical access?

All those would be important, but don't let the perfect be the enemy of the good. We could start from the Vulnerability Of The Year: supply chain attacks.

I got it, we need a new USB-C connector (C for Car), that'd be something to see.

I don't mind, nor even care, about aesthetics.

But I do very much care about losing useful behaviors. The top-right pixel MUST still be able to register a click on the "Close" [X] button of the title bar, always.

Hide your lack of taste behind rounded corners all you want, but DO NOT change the underlying shape of the invisible event handling surfaces.

Why these examples start from a request for a JavaScript animation?

What is it that makes it "better" versus simply asking for an animated video? Is it the ability to later do some adjustments programmatically?

It means the exposure of being in HN front page usually causes a sudden spike of visits, and the increased traffic was too much for the server so the service is down for new visitors.

Please don't believe that this strategy is "reliable" in any way to get paid, if you or your company need that money for survival. FOSS and especially (A)GPL is just about forcing the balance to put more power in end user's hands, nothing else. A Proprietary+AGPL license combo might get you some cash from business wanting to change the code, but it will still allow any Amazon out there to host your code for free as part of their service catalog, while you are left to go out of business.

Recovery is similar to leaving a copy of your door keys to a trusted neighbour (a tradition in some places, it comes in handy when someone goes out and realizes they forgot the keys inside...), so in that comparison, having a recovery email unused for 12 years feels like leaving your backup keys to a neighbor that you never saw ever again in more than a decade.

This kind of posts are a valuable trigger for all others who are reading it. To the author: good luck, I hope you sort your situation soon! I'm now headed to check my accounts for what recovery options I left in there.

Clothing is also a bit of a special thing. Some people will just get bored or tired of wearing the same trousers or the same old coat every year during 10 years. So it is simply not worth it to spend a mini fortune on a great quality one.

This tends to happen more when one is young. Growing older usually means that a good old dusty 15 years great quality coat is seen as it being perfectly ok. I guess that's also what provides that feeling that some people when they approach middle age they "always look the same"... It's not cheap to have a large and varied wardrobe and at the same time filled with high quality garments.

I'd call it externalized costs of regulation and rising demands on production.

If end consumers were able to see an exact and measurable bump in prices the next day a new stronger regulation made production more expensive, voters would be more informed and the whole cost of doing things "better" would be clearer.

Thanks. There's no better way to check how it is than having it on hand.

I'd argue against relative dates because that's an opinionated design that requires cognitive overhead on the user. A young person might be able to mentally translate, but older ones tend to have it more difficult. Usually, opting for relative dates tells us about the designer's lack of experience with different groups of users than the normative one.

I'm just reading from the barrier here, and not knowing what it even looks like, but reading your description I can immediately agree that it is a bad design.

There's only a handful of critical details in a call history, and absolutely no reason for any UI to implement them as secondary or tertiary details: Whether it was in- or outbound. To/from what contact. The date and time.

2 taps for some other extra info such as call length, or further contact details, would be OK I guess, but for first-level info as these, it's 100% bad design.

I mean come on, design-wise this was already a "Done" thing in the golden Nokia days! https://the-gadgeteer.com/2009/03/02/a-week-with-the-nokia-n...

[*] Ctrl+F to find the image below "miss a call".

You're right! that's a bug in my comment then (or more like a spec redundancy I guess) :)

As a society we need to sort out this simple scenario:

* 16 years old Joe buys a $70 cartridge/disc game, already assuming and counting on the $35 that he'll get back on second-hand sell.

That's it. A simple idea that should never cease to be possible, regardless of the medium.

This particular example made games affordable, and it also inadvertently put a concrete price on several other factors like how much it costs to be a first owner vs. wait for a second-hand purchase, and how much it costs to keep it for your collection vs. allowing the product to flow back into the community.

There are buyers who want drugs for recreational reasons, murders for emotional reasons, or spy cams on hotel rooms for business reasons. But those are simply 3 instances where existent demand doesn't mean we should be allowing any offer to exist.

I'd personally agree to put Flock-levels of civil vigilance in the same bag.

Don't publish your code. Let the AI "accidentally escape the sandbox and publish it in a readily available Git repository". Tongue in cheek, in current days who would blame a poor LLM just trying to do the right thing? :)

> Publish your codec, and if the company cares about this they will send a cease and desist.

If there are doubts about C&D letters, don't publish code to a USA provider. Bring it to Gitee, under an anonymous author name.

I've been using Slint as UI toolkit for Rust and so far liked it, coming as I am from the Qt/QML world.

However, at the beginning I had to choose between Slint[1] and egui[2] (which this project uses)

[1]: https://slint.dev/

[2]: https://www.egui.rs/

Anyone has experience in both and is able to drop some thoughts on their strengths & weaknesses for mid-to-large projects?

That's an idea that got some discussion but generally is strongly discouraged. Cutting must mean that the underlying bytes are absolutely not there in the final result, otherwise it will cause data leaks that users would very reasonably expect not to be there.

Imagine "smart cutting" a critically compromising part of a video (e.g. showing some personal info) only to later find out that the actual footage was still there, it just needed some timestamp shifting to unveil.

Note on the specific intervals: that's where the clever optimization comes in: leave as-is (passthrough) all not affected sections of the video (basically everything) and only recode the tiny fraction that needs recoding due to the cut being set on a non-keyframe.

That one, I do believe should get more research and implementations. Currently I only know of LosslessCut's "Smart" mode, but I'd like to see other big players of the video editing space improving the state of the art in that direction for simple cuts.

On related news, you can talk point to point with just a pair of copper wires that physically connects with a device on the other side!

Wait there's more: a couple of simple plastic glasses joined with a string under tension also does the trick.

However more seriously, while being snarky about "obvious" things can be fun, we should all remember to acknowledge the xkcd's "Ten Thousand" effect as a very real law of life.

The list of files that such app would try to access by default on initial startup would be finite and well defined. So, a Flatpak package of such app should already, if done "properly", (I'm just imagining here, not an expert) include allowed access to those paths by default.

I loved Flatpak until I started building a MiniPC with a 112 GB internal disk for HTPC usage... Then I felt the pain of having to get all slightly different dependency versions for each little program I wanted.

The box' cost already topped the project's budget so no new disk for it. I'm back to "proper .deb packaging please"

- 'How many fingers, Winston?'