In fairness, it’s Wired who called them creatives, while Adobe called them artists.

Target’s difficulty in Canada had more to do with logistics and existing trucking routes than anything else. They assumed they could push Canadian governments to allow for the creation of new carrier contracts, but they were wrong, and as a result their supply chain was immediately hamstrung.

The stores in Canada had a harder time getting goods, which caused the company to raise prices accordingly. Images of the stores show many empty shelves, which doesn’t encourage shopping. Canadian consumers weren’t without other options locally, and those shoppers on the US border found it easier and more advantaged to cross over and shop at Target stores in the US should they have a need.

Not true. If terminated for performance concerns, most companies would consider that “for cause” meaning that you would be ineligible for severance. The only costs are the OpEx of the manager and HR team member’s time in addition to the “lost productivity” that your underperformance caused.

This was the best explanation of how this is hurtful that I think you could possibly put together. I came into this thread skeptical of this being a real concern. This changed my mind. Thank you.

I interpreted her point about scholarly rigor to be referring to allegations of plagiarism. She’s vehemently denying those allegations, but she does address them. Otherwise, I agree that it’s likely other prejudices had a part to play in her dismissal.

Fediverse: the final frontier. These are the voyages of the starship Enterprise. Its continuing mission: to explore strange new worlds; to seek out new life and new civilizations; to boldly go where no one has gone before.

Straightforward enough. Dots and tics in fives. And a weird croissant for some reason.

The Meaning of Life, too. Those two Python flicks never get old.

I appreciate that his obit outlines how exasperating Kevin was. But ultimately he did a lot of good even if he did get a bit of a god complex from his notoriety. No matter how you slice it, 59 is too young, and Kevin was far from enough of a jerk to deserve that fate. I hope his family can mourn and find peace. See you on the flip side, Kevin.

I think it’s reasonable to argue, “a super like that also shares the post is functionally different from just a super like.” It doesn’t seem nit-picky when discussing the reasons why someone might choose one service over another to want to be precise about the mechanics of one of those services, no?

Uhhhhh. Not sure which fucking Lemmy instance banned you, but sounds like a real bum out.

At least the issues with lemmy.world seem to have been resolved. While I’m sure some folks were put off by the challenges, I don’t think that the migration is anywhere close to finished. What’s key now is to ensure that Lemmy has good engagement and content for people to interact with. From what I’ve seen, a lot of users here were lurkers primarily on Reddit, but are contributing more here in order to help get things off to a good start. If we keep that energy and keep improving the experience, then it’s entirely possible that Lemmy can be seen at a minimum as a viable alternative to Reddit for folks who don’t like what they’ve got going on over there.

With the improvements Ruud and team put into Lemmy.World, my experience has gotten infinitely better. Lemmy is completely satisfying my Reddit addiction, and Memmy is an incredible app to navigate it all.

Overall, I’m really happy I made the switch. Had a 12 year run on Reddit, but Lemmy proves that Spez is wrong about where the value lies. If the content is water, there are dozens of ways to move it to different places, and right now Reddit looks like a leaky bucket in comparison.

Things feel a ton better today. Thank you for all the hard work!

The most important part of the federation process is played by whichever instance hosts the original post. They’re the hub and all other instances are the spokes.

So once Instance A defederates from Instance C, nothing Instance C users add to posts hosted by Instance A will be added to the master manifest. Basically, everyone is updating Instance A’s copy of the post, and that copy is then being redistributed to all other federated Instances.

Once Instance A defederates from Instance C, the only time their users will interact from that point forward is on a mutually federated instance. Both communities can comment and interact on a post hosted by Instance B.

Basically it works like this:

Instances A, B, and C are federated initially. When a user posts on Instance A, users on Instances B & C can see and interact with the post directly. Any comments they make will be sent back to Instance A as the “home” instance for that content.

Now let’s say Instance A decides they don’t care for the type of interaction they’re getting from Instance C’s users and decides to block - or defederate - Instance C.

To users on instance A, nothing changes other than new posts and comments from users on Instance C will no longer show up. To users on Instance B, nothing changes other than new comments from users on Instance C won’t appear in posts they interact with on Instance A. However, for Instance C, things are suddenly branched.

On Instance C, any posts that were created prior to defederation still exist in Instance C’s record. However, any comments that users on Instance C commit to those posts will no longer be distributed to users on Instances A or B, because Instance A maintains the “primary” record of the post. Similarly, Instance C’s users will not receive updated comments from users on Instance A OR Instance B, because again, Instance A is what determines which comments appear in federated instances. Furthermore, new posts created on Instance A will no longer show up in users’ feeds on Instance C. From the moment of defederation, Instance C’s copies of all posts on Instance A are now distinct, and the only new comments or updates they will receive will be from local users on Instance C.