.@Blender's videos on #YouTube have now come back, but they are also being told by Google/YT that they HAVE to monetise them. #Blender are considering refusing, which presumably would mean the videos being taken down again:
Whatever they once stood for, #Google's aim now is exploiting their users' content for maximum profit.
If you don't want your videos to be exploited, it is important to switch to an independent alternative:
@alexl @rigelk @320x200 @pixelfed @rra Ok. I get that. Still, the authentication with my Mastodon instance could still happen, since it works in the client, right? Then, in the case the instance are not federated, It could propose 2 things: either create a new note with a link to this video page attached to my comment, or just inform me of the impossibility of the action. Right?
But let's say I want to comment under a video on a peertube instance, why would not I be able to authenticate from the client interface of that peertube instance into my mastodon instance and be served with a comment form that will post a toot for me linked to that video.
@rigelk @320x200 I really appreciate @pixelfed initiative. It also implements ActivityPub in another language which is also part of the trip I guess. What I wish though is that #Pixelfed would focus on image manipulation and collections and leave the commenting part to Mastodon/Pleroma/GnuSocial types. Now, as @rra mentions, we probably need to figure out way to enable commenting within the Pixeldfed or Peertube interface with a Mastodon/Pleroma account, which should not be that hard, right?
Anyway, I'm in favor of the unix way where one tool does one thing best. Which means the #fediverse could move into a form of a distributed micro-service architecture in a way, right?
@320x200 Unix wars are the eternal September ;)
@320x200 Yes, that's where I'm going to. I would use the #pixelfed interface to browse a feed of photos, a #peertube interface for videos, etc. So should we build a generic #activitypub backend then? Or just very specialized ones? I like how #peertube is using #mastodon for commenting and staring videos. But afaik Pixelfed is implementing these functionalities natively. And I'm not even mentioning that Mastodon does image and video hosting itself too. Aren't we reinventing the wheel every time?
At some point, I could totally see myself having a #mastodon account for micro-blogging, a #pixelfed account for photo sharing and a #peertube account for videos. Now, since this is all federated, there is no difference between seeing a post coming from #pleroma, Mastodon, Peertube or Pixelfed. It's the interface in which you view it that makes it feel different. Probably mostly because of the functionalities provided by that interface. Am I thinking this straight? And where does this leads to?
Depuis la version 375.70 des pilotes #NVIDIA. Trois tâches planifiées s'exécutent périodiquement et envoient des paquets de données sur les serveurs de Nvidia. Difficile de savoir ce que contiennent exactement les données envoyées puisque celles-ci sont chiffrées.
L' envoi de données est désormais évoqué dans ses conditions d'utilisation. L'utilisateur, est donc consentant à la collecte et l'utilisation de ces informations.
Read this post by @xuv
Well done, some good stuff to know if you want to know how to transition with #birdsite and Mastodon
J'peux aussi dire qu'il se pourrait bien que ce soit la première instance officielle d'un organisme public 😋