You can’t really measure the proportion of players that would buy the game were they not able to pirate it, which makes it easy for CEOs to imagine every incidence of piracy as a lost sale. Who’s going to convince them they put the cart before the horse? It absolves them of direct responsibility for almost any shortcoming possible

Upon looking to this further I’m not sure if it actually works as I understood it to, due to the way group services are handled currently in Mastodon. Clearly there is some sort of flag in Activitypub on group accounts to indicate to other apps that it is a group account, because e.g. https://lemmy.ml/c/climatejustice@chirp.social works and you can follow it but the same link substituting /c/ for /u/ does not work. And for normal user accounts, the inverse is true.

However, aside from that flag, my understanding is they are essentially just user accounts that boost any posts from followers that mention the account handle, which causes the boosted post to show in the feed for all followers of the account. Since that account isn’t actually posting the posts that it boosts, I guess it makes sense that activity wouldn’t be visible in Lemmy, where boosts don’t exist. Following this logic no posts would be displayed, and that’s what is observed. Initially I thought this was because no one on the instance had followed the group yet, because e.g. https://lemmy.world/c/BlackMastodon@chirp.social does show posts while https://lemmy.ml/c/BlackMastodon@chirp.social does not. The same group on a.gup.pe also shows more posts on https://lemmy.ml/c/BlackMastodon@a.gup.pe.

It’s hard for me to make sense of what’s going on here (especially as I don’t microblog or use Mastodon personally) because clearly the Mastodon content is federating through the lemmy instance, but I’ve only been able to observe a subset of it and I haven’t been able to figure out the parameters that have caused some posts to be visible in Lemmy but not others.

I think “communities” term is used on Mastodon in reference to what are “instances” on Lemmy. I’m talking about communities as they apply to Lemmy - in Mastodon I think they’re generally called a “group” account. You subscribe to them in Lemmy mostly the same as how you’d subscribe to a Lemmy community on a different instance. e.g. go to your.lemmy.instance/c/groupname@their.mastodon.instance and subscribe. Or just search for the Mastodon group on the Lemmy communities page, making sure the filters are set to “All”. To find a Mastodon user page is the same, just /u/ instead of /c/. You just can’t follow or subscribe to the user pages because that’s not currently a feature in Lemmy, but you can for groups/communities

Watch history is an absolutely essential metric for Youtube - I can understand how you’ve been led to believe that turning this option off is opting out from that data collection, but no. What this setting is asking is if you want the data collected to be represented to you as recommendations for other videos to watch. It absolutely doesn’t change what data is collected, just whether the videos you’ve watched should be accounted for when the algorithm is finding new videos to recommend.

My understanding is that isn’t correct - in Lemmy you currently can follow Mastodon communities, but not users (following users on any fediverse platform including Lemmy itself just isn’t a part of Lemmy yet). I believe it’s planned to be implemented, but this is one thing differentiating Lemmy and Kbin - you can currently follow Mastodon users in Kbin, and in that case I think it’s just the same way you’d follow another Kbin user. To find their user page it would just be kbin.social/u/user@their.mastodon.instance instead of kbin.social/u/user, so I assume it would be similar for Lemmy once implemented

I stopped using it because it was kinda shitty. Some page elements in my webapps just didn’t display or work correctly. Firefox is the more polished experience now. But it is kinda nice not having to morally justify your choice of browser, too.

I get it, so I installed the extension and browsed with it today. My feedback is that I feel like blocking individual words like Elon or Bezos would be required to make this meaningful at all. I still saw a bunch of stuff about them that the filter didn’t catch because they are so ubiquitous that you don’t need to say their full name to communicate who you’re talking about.

At the same time, while I almost always don’t care and don’t want to hear about a piece of Elon news, it doesn’t mean I’m not interested in Twitter developments, but I think the filter will block most if not all links/info about Twitter since it’s intrinsically linked to Elon’s persona.

At the end of the day I think it’s a cool idea, but I don’t think you can effectively block these guys via this method without blocking any mention of any platform they’re associated with, which isn’t really what I want.

I can’t scrobble my music to last.fm on iOS without some janky workaround. The “almost same level of control” part of what you said relies on an assumption that only the set of use cases explicitly determined by Apple as ones that “matter” are worth supporting. That it’s more important to prevent the user from explicitly allowing a scrobbling app permission to read the music player app’s now playing notification than for the device to be able to perform this simple function.

This point of difference doesnt have any meaningful impact on collection of my data. It just stops the device from being able to do the function I want. So that what, I can sleep easier knowing that Apple designed a slick interface to point out data vectors which were already implied to be collected? It used to feel like a smartphone with training wheels, now they’ve just locked up the handlebars so that it’s easier to go straight.

Bummer, I think it should be all good now that the initial problems with updating the instance and closing the exploit vulnerability are sorted though.

The main factor to consider in making an ultrathin phone in 2023 has nothing to do with the battery. It’s the requirement for a certain level of build quality to be suitable for end consumers. At some point we just need to develop new materials, because we can’t make it any more ultrathin without it also becoming ultrafragile using the materials available.

It hasn’t really been a focus since we realised back around the iPhone 5 that making these sweeping compromises for thinness was yielding diminishing returns and causing other problems. Today that’s still the thinnest mainline iPhone, only the SE and 12 Mini are thinner. 13 mini is thicker, and there is no 14 mini.

If it’s the same issue as me, you just need to logout/login inside the app. JWT secrets had to be rotated following a recent exploit, and the apps I’m using haven’t accounted for this case. Liftoff still thought I was logged in for example, but as far as the instance was concerned I wasn’t. No issues after I logged out/in manually.

The iOS styling is nice, I bet iPhone users would love this. Seems like true black background for OLED users too.

I don’t like that tapping on the Posts button doesn’t show you posts, it shows you a list of filters for the posts you might want to browse. I’d much prefer it just show me the posts using default or last-used parameters and add a button to change them instead.