[-] NekoKoneko@lemmy.world 6 points 1 day ago* (last edited 1 day ago)

Yes, agreed and exactly - and now Amazon's "price history" AI button helps Amazon keep shoppers from using independent (more reliable) tools.

I think what makes this worse is that Camel Camel Camel may not be able to even function in a surveillance pricing world. It requires an objective same-price basis, and once surveillance pricing algorithmically re-prices for each shopper, a single-point third party can no longer track the price reliably for everyone.

Then the reason why surveillance price tracking is so unrealistic is because shoppers would need to actively submit and refresh their pricing for any comparison site to be valid, and that just isn't going to happen.

[-] NekoKoneko@lemmy.world 6 points 1 day ago

I think unfortunately that overestimates the amount of information and discernment shoppers exercise, versus doorbuster/marketed deals and brand loyalty. Going back to net neutrality, "disclosure" just meant that fine print would be used to disclose, along with false "benefits" like saying you get "free" Netflix data on your cell plan, to sell it as a feature.

When you are online, as well, you will have no idea what anyone else is paying. The retailer will completely control the information environment unless consumers put forth an unrealistic, disproportionate amount of time to compare prices.

Disclosure is not how you kill stuff like this, it's how opposition to this dies.

[-] NekoKoneko@lemmy.world 7 points 2 days ago

Deathbed repentance, Republicans love it. Think it's their cheat code to sell their souls for money and power and not be damned.

[-] NekoKoneko@lemmy.world 10 points 2 days ago* (last edited 2 days ago)

They are going to "enforce" disclosure rules but not enforce to prevent the substantive harms of surveillance pricing. It's framed (and many stories and readers and commenters run with the narrative) that it's a restriction, when it's actually a permission. This means that unlike the direction Lina Khan's FTC was taking to prevent surveillance pricing, it is saying to companies, "It's fine to surveillance price as long as you disclose." Meaning, open season.

It's the difference between, for example, enforcing actual net neutrality versus enforcing "disclosure" about violating net neutrality.

[-] NekoKoneko@lemmy.world 156 points 2 days ago

The story and headline are pushing a narrative that hides what is happening.

The FTC made sure we didn't call it "surveillance pricing" and shifted from prevention to disclosure.

https://prospect.org/2026/08/21/ftc-says-it-will-enforce-surveillance-pricing-it-wont/

[-] NekoKoneko@lemmy.world 12 points 4 days ago* (last edited 4 days ago)

In the US, a minor cannot enter into binding contracts without the parents co-signing, and the T&Cs argument here is almost certainly going to be rejected by a court. They are just throwing spaghetti at the wall and being corporate litigation counsel - i.e., leaving no hour unbilled.

[-] NekoKoneko@lemmy.world 19 points 5 days ago

At least in the US, you have a very narrow window to cancel and then you're stuck with it, unless you pay a huge premium for a refundable ticket. But I agree, practically-speaking, the only solution in a late-stage capitalist marketplace is to create some crowdsourced pricing information to identify pricing outliers. Which, truly, isn't a good solution.

If we had a functional government, this would be regulated/prohibited on an emergency basis, since in theory government is supposed to represent people and not corporations. Unfortunately, in 2026, we're livestock to herd and fleece.

[-] NekoKoneko@lemmy.world 1 points 6 days ago

Sorry, all our steam is being used to build aircraft carrier catapults.

[-] NekoKoneko@lemmy.world 32 points 6 days ago* (last edited 6 days ago)

The theory on The Other Site is what I also agree with: They took #1, fed it into an AI 3D modeler to get #4, fed that image into a 2D style AI model to get #2, and then went back to #4 and used AI in-painting and lazy Photoshop to remove some elements to get #3.

[-] NekoKoneko@lemmy.world 1 points 6 days ago* (last edited 6 days ago)

"Not Found" error. From the link, I assume you're deeplinking to a temporary/personal tokenized download.

[-] NekoKoneko@lemmy.world 8 points 6 days ago

This doesn't seem sarcastic.

/s

[-] NekoKoneko@lemmy.world 1 points 6 days ago

What is the x-axis on this chart? Time?

7
submitted 2 months ago* (last edited 2 months ago) by NekoKoneko@lemmy.world to c/lemmyconnect@lemmy.ca

Update: appears fixed in 1.0.434 released today.

Bug Report

Describe the issue: Hi, this is just a bug I wanted to share. A very strange issue has started I think after the beta update yesterday. (1.0.431, June 2, 2026)

In any view (Hot, New, Active, etc), the post list will load as normal, but after scrolling down past about 10-15 posts, will update and rebuild, seemingly finding additional posts and re-sorting them (think of an email sync, where emails in your inbox start appearing and re-sorting themselves). This goes on for a few seconds, completely destroying the selected sort order.

E.g., if you select New, it will at first appear correctly, but then after scrolling a few seconds a bunch of other posts will appear in dynamic updates, eventually leaving you with a jumble of posts not at all in New order.

I can record a video of this happening if it's confusing, but I'm not sure how else to explain it. Happy to provide any other information.

Steps to reproduce:

  1. Open any feed view.
  2. Scroll past 10-15 posts.

Device Information

  • App Version: 1.0.431 (431)

  • Platform: android

  • OS Version: BP1A.250505.005.B1

  • Migration: n/a (attempts: 0)

Modified Settings

The following settings have been changed from defaults:

  • shouldLimitCardImages: true (default: false)
  • defaultRoute: /community?postCommonListingType=Subscribed&hint=Frontpage (default: null)
  • defaultPostSort: Hot (default: Active)
  • applyNsfwInCommunities: false (default: true)
  • cardType: list (default: card)
  • swipeActionsComment: [upvote, upvote, reply] (default: [upvote, save, reply])
  • postActions: [comment, save, none, none] (default: [comment, save, none, crosspost])
  • swipeActionsPost: [upvote, upvote, save] (default: [upvote, save, hide])
  • shouldLoadAllComments: true (default: false)
  • imageDomainRewrites: {} (default: {})
162
submitted 6 months ago* (last edited 6 months ago) by NekoKoneko@lemmy.world to c/selfhosted@lemmy.world

I have a 56 TB local Unraid NAS that is parity protected against single drive failure, and while I think a single drive failing and being parity recovered covers data loss 95% of the time, I'm always concerned about two drives failing or a site-/system-wide disaster that takes out the whole NAS.

For other larger local hosters who are smarter and more prepared, what do you do? Do you sync it off site? How do you deal with cost and bandwidth needs if so? What other backup strategies do you use?

(Sorry if this standard scenario has been discussed - searching didn't turn up anything.)

view more: next ›

NekoKoneko

0 post score
0 comment score
joined 6 months ago