VPN dependent.

  • 1 Post
  • 6 Comments
Joined 2Y ago
cake
Cake day: Jun 30, 2023

help-circle
rss

to preface what might sound like slander, I really would love to get my hands on apple hardware. It is engineered rather well and the geek in me can appreciate that. However, getting access to your own hardware is an issue.

While I have some concerns about their objective features, to my shame, the greatest problem is with the brand and their practices.

I think the root cause of all my issues stems from their morals and aggressive/elitist business practice - specifically their quest to squeeze money out of users and hide behind the lie of “we are doing this for the user’s benefit”.

I have no issue paying money for features I want or entities I’d like to support. In fact, I’m more inclined to financially support those who I believe in.

And apple loves to gatekeep features and keep them exclusive to apple. They effectively benefit from hard work of others who contribute to open standards and services, but at the same time do not share their own. Greedy.




agreed!

And with Meta’s resources and reach, they could stand up a Lemmy.world equivalent easily. Play nice, break their arms jerking each off the Fediverse. And once enough of the instances are reliant on the Meta instance, cut off everyone who won’t pay to federate.


I agree with the second part of your comment, and have concerns with the first part of your comment.

I’m all for allowing others to subscribe to Lemmy or Mastadon content, which is why simply defederating isn’t as attractive as ToS. I want others to see that their communities/intrests/heros/what have you/ exist outside of Meta. I want the average person to contribute even if they don’t know how to set up an instance. What I don’t want is Meta hosting content then paywalling it, cutting off others.

For the first part about limiting to one instance… Well FB is technically one instance from a “domain” perspective. They have load balancers and tons of servers hosting their “instance”.

like I said before, I’m not a policy guy, I don’t know how to solve this. But it would be nice for those who are to spear head this and rally up volunteers so we can get in front of it. If there are no solutions, defederating would be the easiest.



With rumors Meta wants to federate with ActivityPub instances, what say you about instances having Terms of Use policies preventing use of volunteer contributed content being monetized (for example)?
I am not one for policies restricting choice but I fear the situation where Meta sets up instances that become big, say like `Lemmy.world`. Then one day when their instance is popular, they decide to charge other instances to federate with Meta's instances. Big corps like YouTube, twitter, Meta, etc are known to offer services at a loss to grow their service and then drop the hammer and demand payment to use what people already rely on. I feel a policy that prevents federated corp instance from profiting early on from FOSS, self hosted, and volunteer federated servers is something to think about - **though I do not know the best approach.** **I like what Open Source software does with their licensing approach where you are free to view, use, and contribute but if you take you *must* distribute the source code to others. Some outright ban usage for profit without a license.** **Obviously licensing applies well for software to prevent abuse, and I would like a discussion about what Terms of Use policies can prevent volunteer work from being abused - if any are desired.** ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- see the following cross-post from: https://programming.dev/post/427323 > Should programming.dev defederate from Meta if they implement ActivityPub? > I'm not suggesting anything, just want to know what do you think. > > Here is a link if someone don't know what Meta's Threads is: https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
fedilink