The reason you “git blame”
Whoa. It’s like I’m seeing clearly for the first time in my life. You’ve opened my eyes and I will now immediately stop enjoying things because you, for some reason, feel so weirdly insecure about your own tastes that you felt the need to write, like, 25 paragraphs (that I absolutely did not read) seeking validation from internet strangers.
Really though. What was the goal here?
I feel like we’re splitting hairs here. MIT is an extremely permissible license. The fact someone could take this and make a closed source fork doesn’t affect the existence or openness of the MIT licensed releases
https://github.com/bluesky-social
Even their web and mobile clients are FOSS
The FUD and misinformation on here about Bluesky an AT is wild
Bluesky is still in beta. It’s intentionally not open to the general public because federation hasn’t yet been opened up and they only have one instance running.
The nice thing about Bluesky’s architecture (over ActivityPub) is the fact your content and identity is portable. So you can move over to a different instance as they start to come online.
I think the important takeaway from articles like this is the fundamental misunderstanding of decentralized social protocols. It shouldn’t be on one central authority how things are moderated globally. These kinds of articles kind of prove the point.
I was a big fan of Vue 2. Vue 3 is a completely different library if you choose to adopt the composition API (which is where everything is headed). If everyone is going to have to learn a totally new composition pattern, might as well look at what else is out there.
Kinda similar to the big overhaul between Angular 1 and 2
Vue 3’s Composition API and composables are more similar to React functional components and hooks than it is to Vue 2 and its Options API. That’s not to say that React Hooks and Vue Composables are apples-to-apples. They still have different approaches to reactivity and so on, but the programming model is more familiar between the two.
Coming to Vue 3 from 2 was a bit of whiplash. However I’ve been working with it for a few days now and have come to appreciate how much more flexible and powerful it is to have access to Vue’s reactive primitives anywhere - you don’t have to write all your business logic in the scope of a Vue instance.
That said, it comes with a much higher learning curve. Vue 2 gave you guardrails, an easily understood component class structure, etc. That’s what I liked about it as it scaled well to large teams. Whereas React scaled to a large team quickly turns into a complete mess. Ask 10 different React engineers and you’ll get 10 surprisingly different approaches to how to implement components and architect applications.
I think Reddit does have a legitimate argument that the scales have tipped and Reddit eating the costs of “whales” abusing their APIs for for-profit use cases without Reddit being compensated at all is fair.
3P apps using the API at no cost while simultaneously monetizing Reddit’s content by showing their own ads does seem to be taking advantage.
That said, the way Reddit approached this was so scorched earth and bone headed.
For example. Reddit gets 10s of millions of dollars in free content moderation services from volunteers. The moderators of all their biggest subreddits rely on 3P moderation tools since Reddit’s are so poor.
So with the new API policy, they’re asking their unpaid moderators to PAY them for the privilege. It’s such a slap in the face.
Finally to address the original question, Reddit should absolutely block API consumers who are just training their glorified chat bots to regurgitate plagerized content.
I’m really good at searching Google. I’m a “prompt engineer” too