[–] 0 points 3 weeks ago

And what compelling reason is there to buy it at $100 more than the last one I bought that presently works just fine?

If they had just kept the price point they had, I may have got the new one just to have a newer model since it’s been a good 5 years since I bought the last one.

Keep trying to push those prices up, Apple…and you’ll price everyone out except your millionaire tech bro buddies. I wonder how their $2-3k foldable phone is faring…

  • source
  • [–] 1 point 3 weeks ago* (1 child)

    With the lack of actual feature improvements over the prior generation, I'm thinking this was just a way for Apple to increase the price to help compensate for the increased RAM/CPU costs these days. Sitting on the shelf next to to the 2022 model, the 2026 doesn't look compelling at all, but once the 2022 stock is gone, the new price will be the only option.

    We're still using a 2017 model AppleTV 4k. Since getting the better Function101 remote replacements, Its still doing everything we need and we don't feel the need to upgrade.

  • source
  • parent
  • context
  • [–] 3 points 1 month ago

    I thought the same thing. It was the episode I didn't know I needed. It felt like one of the emotional Rick and Morty episodes. I actually talked to a friend about it after because I was so overwhelmed by it. Definitely one of the best episodes of the season.

  • source
  • [–] 2 points 5 months ago

    I appreciate you explaining this. Finding out it's standard Mastodon behavior makes it even worse, lol.

    The term "Fediverse" makes people think there's some true integration across these services when really it's a subset of features that may partially work in some cases, some of the time. Widespread ActivityPub is probably great for developers, but I can't see what it gets users aside from confusion.

  • source
  • parent
  • context
  • [–] 2 points 5 months ago (1 child)

    Wow, what a ridiculous dev-brain design

    If I remember correctly it's baked into the main fork everyone uses, it's not like OPs instance decided to do this, I'm not even sure they can turn it off

    But I think it all comes down to whoever made the moan code, not anticipating people would "at someone" as a phrase and not really be wanting to "@ them". Linguistically it's cool and all, I just want them to stop the crossposts now that people are using it without intending it literally

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (2 children)

    part of their instances programming to post to a community if it exists

    Wow, what a ridiculous dev-brain design. "If the strings match, dump the content into the community. Whatever instance, who cares?" Communities have rules, norms… and at least in theory, culture.

  • source
  • parent
  • context
  • [–] 3 points 5 months ago (3 children)

    If their instance "at's" something, it's (to my understanding) part of their instances programming to post to a community if it exists.

    Since a reddit exodus came to .world years ago, a bunch of empty ghost communities exist, so that's why they always land here.

    I think there needs to be a clear divide between the two types, for instances that want to do both, have a toggle for how your post should be sent out to the fediverse.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (4 children)

    I get that they probably meant to do a # instead of a @, but that mistake leading to a post on a Lemmy community is just bizarre behavior... their "@" didn't even include an instance. This kind of integration across Fediverse platforms is so janky, and my hot take is that it shouldn't exist.

  • source
  • parent
  • context