I think it is an A/B test, as you described, based on this part:
> We created a secret landing page. The product and design were identical. The only difference? One was labeled “Made in Asia” and priced at $129. The other, “Made in the USA,” at $239.
It's odd that they changed the text AND nearly doubled the price. They seem to attribute the conversion rate dropping to the text change, though.
> User interface designers aim to reduce cognitive load, improve ease of use, and guarantee access to all (Johnson, 2020).
Do they, though? Anecdotally, they seem to be primarily focused on optimizing engagement metrics, secondarily on adding gratuitous padding, and tertiarily on making all the buttons flat and harder to distinguish from the background. Rant over.
Can you explain the fallacy in more detail? It doesn't seem like a leap that if marriage is less popular, a larger percentage of the population is single.
They can be in a relationship (not single) but not married. I know people in relationships for 7+ years who haven’t married. That was far less common the further back you go.
I was responding to the parent argument that the pun couldn't have been written by chatgpt, when that is literally the _only_ pun that ChatGPT comes up with.
I'm curious how much review happens in Nix packages. It seems like individual packages have maintainers (who are typically not the software authors). I wonder how much latitude they have to add their own patches, change the source repo's URL, or other sneaky things.
Not a lot in most cases. You’re still just grabbing a package and blindly building whatever source code you get from the web. Unless the maintainer is doing their due diligence nothing.
Goes the same for almost all packages in all distros though.
I’d say most of us have some connection to what we’re packaging but there are plenty of hastily approved and merged “bump to version x” commits happening.
Nixpkgs package maintainers don't usually have commit rights. I assume that if one tried to include some weird patch, the reviewer would at least glance at it before committing.
I’ve never looked at the process of making a nixpkg, but wouldn’t the review process only catch something malicious if it was added to the packaging process? Anything malicious added to the build process wouldn’t show up correct? At least not unless the package maintainer was familiar and looked themself?
I am not sure I understand the distinction between the packaging and build process, at least in the context of nixpkgs. Packages in nixpkgs are essentially build instructions, which you can either build/compile locally (like Gentoo) but normally you download them from the cache.
Official packages for the nixpkgs cache are built/compiled on Nix's own infrastructure, not by the maintainers, so you can't just sneak malicious code in that way without cracking into the server.
What package maintainers do is contribute these build instructions, called derivations. Here's an example for a moderately complex one:
As you can see, you can include a patch to the source files, add custom bash commands to be executed and you can point the source code download link to anywhere you want. You could do something malicious in any of these steps, but I expect the reviewer to at least look at it and build it locally for testing before committing, in addition to any other interested party.
Nice work! It might be nice to hint to iOS users that they should disable silent mode via the little side toggle if they want to hear anything. Just a quirk of iOS that took me literally years to figure out -- I assumed it just didn't support the Web Audio API and went on with my life.
I hit this on https://ambiph.one - my solution ended up being similar (use an <audio> element) but because I also wanted audio to play in the background and when the screen is off there's an extra step of tricking Safari into thinking it's playing a livestream, since apparently that's the only kind of audio Apple thinks should be allowed to play in the background.
Coincidentally someone asked me about this the other day so I put together a minimal demo here in case it's useful to anyone: https://codepen.io/matteason/pen/VYwdzVV
I believe you need to use the audio element specifically. The Web Audio API is subject to different restrictions than the audio element. I used a similar approach on Audjust: https://www.audjust.com/blog/unmute-web-audio-on-ios/
(nice site you created btw! I love seeing audio stuff for the web)
Yes, exactly. This is on an iPhone, to be clear. Maybe the control center on iPads has an equivalent software toggle? Sorry, that probably isn't very helpful.
No, it just hasn’t been possible to differentiate as well before.
One example is biscuit manufacturing, where it’s a fairly open secret that supermarket own brand biscuits are the same product as name brand, because it’s better to capture that segment at a lower margin than to lose it to competition.
Tech now makes it possible to target individuals rather than demographics, but there’s nothing inherently against the status quo in doing so.
I have a side business and virtually every customer pays a different price, what you’re saying is simply not true. Airlines do it, hotels do it, I have different rates for my customers at my day job, etc.
And even if they pay the same price, they’ll have different costs.
I’ll gladly take all the free alcohol an airline will give me, but other people don’t at all!
I sell some stuff on eBay. If you appear untrustworthy, I’ll spend more for tracking/better tracking on your order so you’ll actually get your stuff faster/more reliably.
Oh, I'm not denying this is the way things are done. I just don't think it should be legal.
Price segmentation was more palatable a few decades ago, but technology has enabled us to push it to this absurd (to me) extreme where individuals get different prices at different times of the day.
It feels wrong to size up your customer and pick the highest price you think they'll pay.
The market is an agglomeration of many individuals, meaning that there is no hard and fast rule that you must charge only one price for the entire market; indeed, many custom-priced products exist, enterprise SaaS being one example.
There's no such thing as "the market", there are market segments that abstractly represent groups of people with similar characteristics. Charging different prices to people in different segments is standard business practice. Burger chains could charge wealthy individuals $100k per burger if they wanted to, just, burger chains usually have difficulty distinguishing the truly wealthy individuals who walk in the door who would have no trouble putting down that kind of money for a burger.
.... which, in the day and age of facial recognition, gives me an idea for a startup.
Burger chains have at least gotten a start on differentiating their pricing - by raising prices dramatically across the board, and telling anyone who’s frugal or just broke that they can only get discounts (to bring prices slightly lower than today’s pricing, but still a lot more than before) if they use the app. Upper-class people don’t bother with it and pay full price, frugal people take the time to figure out the cheapest way to use one of the current “offers” to assemble a meal.
Upper class people don't bother with it because we all know those discounts are temporary but they'll never let go of the data they extract from those apps and will try to spam you
One can always use a fake email and login account. Upper class people don't bother because they don't eat at fast food chains as often enough as lower class people to warrant needing an app for each one; 99.9% don't give a shit about data collection, only people on HN and other technical fora do.
>One can always use a fake email and login account.
When you're using that fake email be sure to have a burner phone or public internet so they can't link it to your IP, also don't use your computer or any computer you've logged in on so that browser fingerprinting doesn't tag you, also turn off your GPS so they can't geo correlate you.
Of course the rich person is in the same boat, their geolocation will log that they went to Burger King, or their credit card company will snitch on them. Okay, fine, pay with cash, cover your phone in a tin foil faraday cage. Now you also will need to drive a 30 year old car to said establishment since the car manufacturer put a cellular modem and GPS in your car and sells the fact that you went to Burger King to the highest bidder.
That's all I can think of off the top of my head, I'm sure there are dozens of other ways people are tagged. At some level may as well either use the app or just not go.
Definitely a personal fan of Graphviz as well! One thing I'm curious about are usecases that require version-controlled diagram sources. Do you guys have e.g. a build step that updates the rendered version somewhere? Or Confluence integration, etc?
I'm not the person you replied to, but for projects I maintain at work we've got a plugin for Confluence called Mark. It allows using Markdown to create Confluence pages, which is useful because the company uses Confluence for some reason. For diagrams (Mermaid, GraphViz, etc.) the source for the diagram is kept with the Markdown & I've got a CI job that generates diagrams & then runs Mark to update Confluence.
It makes it a lot easier to keep the documentation in sync with the code than having to remember to go to Confluence and update things. And avoids the pain of dealing with Atlassian's slow-loading site.
I work at a BigCorp with a fancy md-to-html generator that supports graphviz via code blocks, e.g.
```dot
digraph { a -> b }
```
But day-to-day, I actually use graphviz inside emacs org-mode (and in a private git repo). If you press C-c C-c with your cursor on the code blocks, it plops the rendered graph below.
> We created a secret landing page. The product and design were identical. The only difference? One was labeled “Made in Asia” and priced at $129. The other, “Made in the USA,” at $239.
It's odd that they changed the text AND nearly doubled the price. They seem to attribute the conversion rate dropping to the text change, though.