diff --git a/content/_index.md b/content/_index.md index 2a0cde7..307ed85 100644 --- a/content/_index.md +++ b/content/_index.md @@ -1,7 +1,7 @@ +++ title = "Home" layout = "index" -lastmod = 2025-01-17T12:07:30+01:00 +lastmod = 2025-01-17T12:10:28+01:00 draft = false [menu] [menu.nav] diff --git a/content/blog/I-love-emacs.md b/content/blog/I-love-emacs.md index e9cc6dc..a809381 100644 --- a/content/blog/I-love-emacs.md +++ b/content/blog/I-love-emacs.md @@ -1,7 +1,7 @@ +++ title = "I really, really like Emacs" publishDate = 2022-10-01T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["orgmode"] categories = ["emacs", "tech"] draft = false diff --git a/content/blog/LLM-Note.md b/content/blog/LLM-Note.md index 2432b81..ec45722 100644 --- a/content/blog/LLM-Note.md +++ b/content/blog/LLM-Note.md @@ -1,7 +1,7 @@ +++ title = "Note about LLM's and training data" publishDate = 2023-03-09T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["copyright", "thieves"] categories = ["llm", "tech"] draft = false diff --git a/content/blog/_index.md b/content/blog/_index.md index 55e8979..c05546a 100644 --- a/content/blog/_index.md +++ b/content/blog/_index.md @@ -1,6 +1,6 @@ +++ title = "Blog" -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 draft = false meta = true type = "list" @@ -92,30 +92,30 @@ Naturally they're trying to excuse this lack of consent by claiming that the con Just so you understand, this is _bonkers_. Let's go for it step by step. -- \`unrestricted, unlimited\` Means they can do whatever they want to that data, without any limits or additional licensing necessary. Currently they claim they aren't selling user data to advertisers or using it for training AI. Tomorrow they might, and the user agreed to these terms{{< sidenote >}}Even without being aware of this agreement.{{</sidenote>}}, they won't be in any breach of contract, even if the user trusted them not to while consenting to this{{< sidenote >}}Again, intentionally or not. {{</sidenote>}}. -- \`irrevocable, perpetual\` Means they have license to use collected user data forever, and users aren't able to ever revoke this license. The data becomes _effectively owned_ by loops.video at this point. -- \`transferable\` Means they can give further _effective ownership_ of this data to anyone they like or have a whim to. -- \`royalty-free, fully-paid\` Means users can never ask them to pay up for the use that data, including for commercial purposes. -- \`worldwide right and license\` Means they can transfer any collected data anywhere in the world, and process it there. The main issue is that they may very well take it outside of jurisdictions where a user's data is protected by say, GDPR, if they're in Europe. +- `unrestricted, unlimited` Means they can do whatever they want to that data, without any limits or additional licensing necessary. Currently they claim they aren't selling user data to advertisers or using it for training AI. Tomorrow they might, and the user agreed to these terms{{< sidenote >}}Even without being aware of this agreement.{{</sidenote>}}, they won't be in any breach of contract, even if the user trusted them not to while consenting to this{{< sidenote >}}Again, intentionally or not. {{</sidenote>}}. +- `irrevocable, perpetual` Means they have license to use collected user data forever, and users aren't able to ever revoke this license. The data becomes _effectively owned_ by loops.video at this point. +- `transferable` Means they can give further _effective ownership_ of this data to anyone they like or have a whim to. +- `royalty-free, fully-paid` Means users can never ask them to pay up for the use that data, including for commercial purposes. +- `worldwide right and license` Means they can transfer any collected data anywhere in the world, and process it there. The main issue is that they may very well take it outside of jurisdictions where a user's data is protected by say, GDPR, if they're in Europe. > to host, use, copy, reproduce, disclose, sell, resell, publish, broadcast, retitle, archive, store, cache, publicly perform, publicly display, reformat, translate, transmit, excerpt (in whole or in part), and distribute such Contributions (including, without limitation, your image and voice) for any purpose, commercial, advertising, or otherwise, and to prepare derivative works of, or incorporate into other works, such Contributions, and grant and authorize sublicenses of the foregoing. Let's do this again: -- \`to host\` Means they store the data. Fine, that's necessary for the stated purpose of the service. -- \`use, copy, reproduce, disclose\` Means they need to process (e.g. transcode videos) data, create copies in their infrastructure and display it to the end users. All good so far, these are necessary for their service to work. Note here that disclosure here may mean several different things. I'm going to assume good will on this, that they mean disclosure to the people/ groups intended by the user. -- \`sell, resell\` Wait what? Let me get this straight, [their FAQ says they don't sell the data... but they still ask for consent to sell user data!](https://loops.video/help-center/frequently-asked-questions) Clown world. -- \`publish, broadcast\` This is fine, that's what the platform is for... unless they mean outside of their stated service, that being the loops.video **online** platform. -- \`retitle\` Means they can change the ownership of the data/ content as they wish. Yet another red flag, which fundamentally undermines their claim that users preserve ownership of their. -- \`archive, store, cache\` Fine, necessary for their service. -- \`publicly perform, publicly display\` Means they get rights to put user content in public; note that this means they can ignore the user's chosen privacy options entirely - users may end up posting something very private to a select group of friends, and find that same video anywhere on the web, and loops.video will _not_ be in breach of contract, as they already gave them full license to do what they please. -- \`reformat, translate\` This is another red flag. Reformatting means that user content/ data may be used in a different medium, e.g. users give permission to loops.video to use their content not just on their platform, but in print, TV, e-mail (as opposed to the ActivityPub networks), using them on YouTube or other platforms, etc. -- \`transmit,\` Well yet, to the end users. Hopefully. -- \`excerpt (in whole or in part)\` The only way I can see this as legitimate is if they're going to have small excerpts of the video used as thumbnails, like YouTube does. But of course they won't, this ToS is clearly predatory to the bone. -- \`distribute such Contributions (including, without limitation, your image and voice)\` There you have it. _Zero_ protection for user data. A user interacting{{< sidenote >}}In any way, intentionally or not! {{</sidenote>}} with loops.video surrenders every piece of data (including your name{{< sidenote >}}Yes, 'image' means a person's public image with all the other data. These terms are chock-full of misleading legal jargon.{{</sidenote>}}, e-mail, face, voice, and all the content they post) to loops.video. -- \`for any purpose, commercial, advertising or otherwise\` More red flags. The only purpose they **need** to operate the platform is to distribute user media to the people of that user's choosing. Personally, I don't want my data used commercially, or to find my writing or person in the hands of advertisers{{< sidenote >}}I have zero expectations that loops.video will have an in-house advertising team. Do you?{{</sidenote>}}. And what's this 'otherwise'? Why isn't the distribution of content to the people of the user's choosing even mentioned{{< sidenote >}}To answer my own question: because loops.video is a data-scraping service, and not a video sharing platform.{{</sidenote>}}? -- \`and to prepare derivative works of, or incorporate into other works, such Contributions\` Just no? Ignoring the face meaning of this, of using user content for ads or making compilations of videos, _derivative works_ may easily include AI training. _Incorporating into other works_ is also a red flag, since a user may wish to maintain ownership and control over how their content is used. Fair use exists for a reason, and this clause completely bypasses that. -- \`and grant and authorize sublicenses of the foregoing\` Means they get to give any kind of license to user data and content to any party of their choosing. +- `to host` Means they store the data. Fine, that's necessary for the stated purpose of the service. +- `use, copy, reproduce, disclose` Means they need to process (e.g. transcode videos) data, create copies in their infrastructure and display it to the end users. All good so far, these are necessary for their service to work. Note here that disclosure here may mean several different things. I'm going to assume good will on this, that they mean disclosure to the people/ groups intended by the user. +- `sell, resell` Wait what? Let me get this straight, [their FAQ says they don't sell the data... but they still ask for consent to sell user data!](https://loops.video/help-center/frequently-asked-questions) Clown world. +- `publish, broadcast` This is fine, that's what the platform is for... unless they mean outside of their stated service, that being the loops.video **online** platform. +- `retitle` Means they can change the ownership of the data/ content as they wish. Yet another red flag, which fundamentally undermines their claim that users preserve ownership of their. +- `archive, store, cache` Fine, necessary for their service. +- `publicly perform, publicly display` Means they get rights to put user content in public; note that this means they can ignore the user's chosen privacy options entirely - users may end up posting something very private to a select group of friends, and find that same video anywhere on the web, and loops.video will _not_ be in breach of contract, as they already gave them full license to do what they please. +- `reformat, translate` This is another red flag. Reformatting means that user content/ data may be used in a different medium, e.g. users give permission to loops.video to use their content not just on their platform, but in print, TV, e-mail (as opposed to the ActivityPub networks), using them on YouTube or other platforms, etc. +- `transmit,` Well yet, to the end users. Hopefully. +- `excerpt (in whole or in part)` The only way I can see this as legitimate is if they're going to have small excerpts of the video used as thumbnails, like YouTube does. But of course they won't, this ToS is clearly predatory to the bone. +- `distribute such Contributions (including, without limitation, your image and voice)` There you have it. _Zero_ protection for user data. A user interacting{{< sidenote >}}In any way, intentionally or not! {{</sidenote>}} with loops.video surrenders every piece of data (including your name{{< sidenote >}}Yes, 'image' means a person's public image with all the other data. These terms are chock-full of misleading legal jargon.{{</sidenote>}}, e-mail, face, voice, and all the content they post) to loops.video. +- `for any purpose, commercial, advertising or otherwise` More red flags. The only purpose they **need** to operate the platform is to distribute user media to the people of that user's choosing. Personally, I don't want my data used commercially, or to find my writing or person in the hands of advertisers{{< sidenote >}}I have zero expectations that loops.video will have an in-house advertising team. Do you?{{</sidenote>}}. And what's this 'otherwise'? Why isn't the distribution of content to the people of the user's choosing even mentioned{{< sidenote >}}To answer my own question: because loops.video is a data-scraping service, and not a video sharing platform.{{</sidenote>}}? +- `and to prepare derivative works of, or incorporate into other works, such Contributions` Just no? Ignoring the face meaning of this, of using user content for ads or making compilations of videos, _derivative works_ may easily include AI training. _Incorporating into other works_ is also a red flag, since a user may wish to maintain ownership and control over how their content is used. Fair use exists for a reason, and this clause completely bypasses that. +- `and grant and authorize sublicenses of the foregoing` Means they get to give any kind of license to user data and content to any party of their choosing. - In short, yes, loops.video does practically take full co-ownership of user content; the only right users keep is author's rights (the right to say they made the original content - but not any derivative works), and the right to grant licenses to the content to other entities aside from loops.video. @@ -205,7 +205,7 @@ Fair enough, but then...! Who are these trusted third parties? There's no way to tell. -But here's the point: these parties 'assist loops.video' in \`conducting their business\`. Wait, what? What business? What even _is_ loops.video's business model? So far, at least from my reading on their website, they don't have any sources of revenue. +But here's the point: these parties 'assist loops.video' in `conducting their business`. Wait, what? What business? What even _is_ loops.video's business model? So far, at least from my reading on their website, they don't have any sources of revenue. But here they're saying they **do** sell, trade or otherwise transfer data to 'trusted third parties' who assist them in 'conducting their business' 'so long as those parties agree to keep this information confidential.' diff --git a/content/blog/a-kind-view-of-business.md b/content/blog/a-kind-view-of-business.md index 726eea7..4fa3edd 100644 --- a/content/blog/a-kind-view-of-business.md +++ b/content/blog/a-kind-view-of-business.md @@ -1,7 +1,7 @@ +++ title = "A kind view of business" publishDate = 2024-01-25T00:00:00+01:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["mindset", "rant"] categories = ["business"] draft = false diff --git a/content/blog/a-new-look.md b/content/blog/a-new-look.md index 40e587f..ec9dc1d 100644 --- a/content/blog/a-new-look.md +++ b/content/blog/a-new-look.md @@ -1,7 +1,7 @@ +++ title = "A new look: ox-tufte" publishDate = 2023-10-23T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["orgmode", "web", "css", "tufte"] categories = ["emacs", "tech"] draft = false diff --git a/content/blog/avoidance-in-business.md b/content/blog/avoidance-in-business.md index 95ef1d3..1ec536e 100644 --- a/content/blog/avoidance-in-business.md +++ b/content/blog/avoidance-in-business.md @@ -1,7 +1,7 @@ +++ title = "On Avoidance in Business" publishDate = 2023-05-04T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["psychology", "riskmanagement", "avoidance", "fear"] categories = ["business"] draft = false diff --git a/content/blog/brain-lube-2.md b/content/blog/brain-lube-2.md index d5d785d..ba375fa 100644 --- a/content/blog/brain-lube-2.md +++ b/content/blog/brain-lube-2.md @@ -1,7 +1,7 @@ +++ title = "Trying out some brain supplements, pt. 2" publishDate = 2022-11-20T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["supplements", "nootropics"] categories = ["mind"] draft = false diff --git a/content/blog/brain-lube-3.md b/content/blog/brain-lube-3.md index 40d1ee6..25f4856 100644 --- a/content/blog/brain-lube-3.md +++ b/content/blog/brain-lube-3.md @@ -1,7 +1,7 @@ +++ title = "Brain supplements: A two month summary" publishDate = 2023-01-06T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["supplements", "nootropics"] categories = ["mind"] draft = false diff --git a/content/blog/brain-lube.md b/content/blog/brain-lube.md index ca6eef8..e5b90fc 100644 --- a/content/blog/brain-lube.md +++ b/content/blog/brain-lube.md @@ -1,7 +1,7 @@ +++ title = "Trying out some brain supplements" publishDate = 2022-11-18T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["supplements", "nootropics"] categories = ["mind"] draft = false diff --git a/content/blog/call-it-a-day.md b/content/blog/call-it-a-day.md index 1b71359..efb3ece 100644 --- a/content/blog/call-it-a-day.md +++ b/content/blog/call-it-a-day.md @@ -1,7 +1,7 @@ +++ title = "On the value of calling it a day (and how to get there)" publishDate = 2022-09-30T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["psychology", "work", "projectmanagement"] categories = ["business"] draft = false diff --git a/content/blog/democracy.md b/content/blog/democracy.md index 8153698..11c448f 100644 --- a/content/blog/democracy.md +++ b/content/blog/democracy.md @@ -1,7 +1,7 @@ +++ title = "Democracy" publishDate = 2024-12-07T00:00:00+01:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:29+01:00 draft = false meta = true type = "list" diff --git a/content/blog/efficiency-typing.md b/content/blog/efficiency-typing.md index d3d2e85..47c05f2 100644 --- a/content/blog/efficiency-typing.md +++ b/content/blog/efficiency-typing.md @@ -1,7 +1,7 @@ +++ title = "Efficient computer use" publishDate = 2022-11-12T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["ergonomics", "keyboards", "typing", "speed", "efficency"] categories = ["tech"] draft = false diff --git a/content/blog/foss-subscription-model.md b/content/blog/foss-subscription-model.md index c8f9507..0e904fc 100644 --- a/content/blog/foss-subscription-model.md +++ b/content/blog/foss-subscription-model.md @@ -1,7 +1,7 @@ +++ title = "Considerations on FOSS and subscription models" publishDate = 2022-10-02T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["business", "foss", "vendorlock", "proprietary", "saas", "scam"] categories = ["tech"] draft = false diff --git a/content/blog/games-yakuza.md b/content/blog/games-yakuza.md index 51a6ff6..53e3320 100644 --- a/content/blog/games-yakuza.md +++ b/content/blog/games-yakuza.md @@ -1,7 +1,7 @@ +++ title = "Heaps of fun (Yakuza)" publishDate = 2022-10-17T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["yakuza", "review"] categories = ["videogames"] draft = false diff --git a/content/blog/haxe-vscode.md b/content/blog/haxe-vscode.md index 881e3fd..b75d35a 100644 --- a/content/blog/haxe-vscode.md +++ b/content/blog/haxe-vscode.md @@ -1,7 +1,7 @@ +++ title = "Haxe, heaps, and VSCode (small rant)" publishDate = 2022-10-10T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["proprietary", "vscode", "vendorlock"] categories = ["software", "tech"] draft = false diff --git a/content/blog/hugo-setup-improvements.md b/content/blog/hugo-setup-improvements.md index 373813c..3dae37a 100644 --- a/content/blog/hugo-setup-improvements.md +++ b/content/blog/hugo-setup-improvements.md @@ -1,7 +1,7 @@ +++ title = "Some improvements for my ox-hugo set-up" publishDate = 2024-11-18T19:37:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["hugo", "web", "orgmode"] categories = ["tech", "emacs"] draft = false diff --git a/content/blog/lists-self-promotion.md b/content/blog/lists-self-promotion.md index eaf142e..5176cee 100644 --- a/content/blog/lists-self-promotion.md +++ b/content/blog/lists-self-promotion.md @@ -1,7 +1,7 @@ +++ title = "[Happy Holidays!] On posting lists for self-promotion" publishDate = 2022-12-25T00:00:00+01:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["badmarketing", "linkedin"] categories = ["business"] draft = false diff --git a/content/blog/loops-video-terms.md b/content/blog/loops-video-terms.md index 9ef7332..5967d46 100644 --- a/content/blog/loops-video-terms.md +++ b/content/blog/loops-video-terms.md @@ -1,7 +1,7 @@ +++ title = "loops.video" publishDate = 2025-01-17T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["loopsvideo", "tos"] categories = ["legal", "tech"] draft = false @@ -87,30 +87,30 @@ Naturally they're trying to excuse this lack of consent by claiming that the con Just so you understand, this is _bonkers_. Let's go for it step by step. -- \`unrestricted, unlimited\` Means they can do whatever they want to that data, without any limits or additional licensing necessary. Currently they claim they aren't selling user data to advertisers or using it for training AI. Tomorrow they might, and the user agreed to these terms{{< sidenote >}}Even without being aware of this agreement.{{</sidenote>}}, they won't be in any breach of contract, even if the user trusted them not to while consenting to this{{< sidenote >}}Again, intentionally or not. {{</sidenote>}}. -- \`irrevocable, perpetual\` Means they have license to use collected user data forever, and users aren't able to ever revoke this license. The data becomes _effectively owned_ by loops.video at this point. -- \`transferable\` Means they can give further _effective ownership_ of this data to anyone they like or have a whim to. -- \`royalty-free, fully-paid\` Means users can never ask them to pay up for the use that data, including for commercial purposes. -- \`worldwide right and license\` Means they can transfer any collected data anywhere in the world, and process it there. The main issue is that they may very well take it outside of jurisdictions where a user's data is protected by say, GDPR, if they're in Europe. +- `unrestricted, unlimited` Means they can do whatever they want to that data, without any limits or additional licensing necessary. Currently they claim they aren't selling user data to advertisers or using it for training AI. Tomorrow they might, and the user agreed to these terms{{< sidenote >}}Even without being aware of this agreement.{{</sidenote>}}, they won't be in any breach of contract, even if the user trusted them not to while consenting to this{{< sidenote >}}Again, intentionally or not. {{</sidenote>}}. +- `irrevocable, perpetual` Means they have license to use collected user data forever, and users aren't able to ever revoke this license. The data becomes _effectively owned_ by loops.video at this point. +- `transferable` Means they can give further _effective ownership_ of this data to anyone they like or have a whim to. +- `royalty-free, fully-paid` Means users can never ask them to pay up for the use that data, including for commercial purposes. +- `worldwide right and license` Means they can transfer any collected data anywhere in the world, and process it there. The main issue is that they may very well take it outside of jurisdictions where a user's data is protected by say, GDPR, if they're in Europe. > to host, use, copy, reproduce, disclose, sell, resell, publish, broadcast, retitle, archive, store, cache, publicly perform, publicly display, reformat, translate, transmit, excerpt (in whole or in part), and distribute such Contributions (including, without limitation, your image and voice) for any purpose, commercial, advertising, or otherwise, and to prepare derivative works of, or incorporate into other works, such Contributions, and grant and authorize sublicenses of the foregoing. Let's do this again: -- \`to host\` Means they store the data. Fine, that's necessary for the stated purpose of the service. -- \`use, copy, reproduce, disclose\` Means they need to process (e.g. transcode videos) data, create copies in their infrastructure and display it to the end users. All good so far, these are necessary for their service to work. Note here that disclosure here may mean several different things. I'm going to assume good will on this, that they mean disclosure to the people/ groups intended by the user. -- \`sell, resell\` Wait what? Let me get this straight, [their FAQ says they don't sell the data... but they still ask for consent to sell user data!](https://loops.video/help-center/frequently-asked-questions) Clown world. -- \`publish, broadcast\` This is fine, that's what the platform is for... unless they mean outside of their stated service, that being the loops.video **online** platform. -- \`retitle\` Means they can change the ownership of the data/ content as they wish. Yet another red flag, which fundamentally undermines their claim that users preserve ownership of their. -- \`archive, store, cache\` Fine, necessary for their service. -- \`publicly perform, publicly display\` Means they get rights to put user content in public; note that this means they can ignore the user's chosen privacy options entirely - users may end up posting something very private to a select group of friends, and find that same video anywhere on the web, and loops.video will _not_ be in breach of contract, as they already gave them full license to do what they please. -- \`reformat, translate\` This is another red flag. Reformatting means that user content/ data may be used in a different medium, e.g. users give permission to loops.video to use their content not just on their platform, but in print, TV, e-mail (as opposed to the ActivityPub networks), using them on YouTube or other platforms, etc. -- \`transmit,\` Well yet, to the end users. Hopefully. -- \`excerpt (in whole or in part)\` The only way I can see this as legitimate is if they're going to have small excerpts of the video used as thumbnails, like YouTube does. But of course they won't, this ToS is clearly predatory to the bone. -- \`distribute such Contributions (including, without limitation, your image and voice)\` There you have it. _Zero_ protection for user data. A user interacting{{< sidenote >}}In any way, intentionally or not! {{</sidenote>}} with loops.video surrenders every piece of data (including your name{{< sidenote >}}Yes, 'image' means a person's public image with all the other data. These terms are chock-full of misleading legal jargon.{{</sidenote>}}, e-mail, face, voice, and all the content they post) to loops.video. -- \`for any purpose, commercial, advertising or otherwise\` More red flags. The only purpose they **need** to operate the platform is to distribute user media to the people of that user's choosing. Personally, I don't want my data used commercially, or to find my writing or person in the hands of advertisers{{< sidenote >}}I have zero expectations that loops.video will have an in-house advertising team. Do you?{{</sidenote>}}. And what's this 'otherwise'? Why isn't the distribution of content to the people of the user's choosing even mentioned{{< sidenote >}}To answer my own question: because loops.video is a data-scraping service, and not a video sharing platform.{{</sidenote>}}? -- \`and to prepare derivative works of, or incorporate into other works, such Contributions\` Just no? Ignoring the face meaning of this, of using user content for ads or making compilations of videos, _derivative works_ may easily include AI training. _Incorporating into other works_ is also a red flag, since a user may wish to maintain ownership and control over how their content is used. Fair use exists for a reason, and this clause completely bypasses that. -- \`and grant and authorize sublicenses of the foregoing\` Means they get to give any kind of license to user data and content to any party of their choosing. +- `to host` Means they store the data. Fine, that's necessary for the stated purpose of the service. +- `use, copy, reproduce, disclose` Means they need to process (e.g. transcode videos) data, create copies in their infrastructure and display it to the end users. All good so far, these are necessary for their service to work. Note here that disclosure here may mean several different things. I'm going to assume good will on this, that they mean disclosure to the people/ groups intended by the user. +- `sell, resell` Wait what? Let me get this straight, [their FAQ says they don't sell the data... but they still ask for consent to sell user data!](https://loops.video/help-center/frequently-asked-questions) Clown world. +- `publish, broadcast` This is fine, that's what the platform is for... unless they mean outside of their stated service, that being the loops.video **online** platform. +- `retitle` Means they can change the ownership of the data/ content as they wish. Yet another red flag, which fundamentally undermines their claim that users preserve ownership of their. +- `archive, store, cache` Fine, necessary for their service. +- `publicly perform, publicly display` Means they get rights to put user content in public; note that this means they can ignore the user's chosen privacy options entirely - users may end up posting something very private to a select group of friends, and find that same video anywhere on the web, and loops.video will _not_ be in breach of contract, as they already gave them full license to do what they please. +- `reformat, translate` This is another red flag. Reformatting means that user content/ data may be used in a different medium, e.g. users give permission to loops.video to use their content not just on their platform, but in print, TV, e-mail (as opposed to the ActivityPub networks), using them on YouTube or other platforms, etc. +- `transmit,` Well yet, to the end users. Hopefully. +- `excerpt (in whole or in part)` The only way I can see this as legitimate is if they're going to have small excerpts of the video used as thumbnails, like YouTube does. But of course they won't, this ToS is clearly predatory to the bone. +- `distribute such Contributions (including, without limitation, your image and voice)` There you have it. _Zero_ protection for user data. A user interacting{{< sidenote >}}In any way, intentionally or not! {{</sidenote>}} with loops.video surrenders every piece of data (including your name{{< sidenote >}}Yes, 'image' means a person's public image with all the other data. These terms are chock-full of misleading legal jargon.{{</sidenote>}}, e-mail, face, voice, and all the content they post) to loops.video. +- `for any purpose, commercial, advertising or otherwise` More red flags. The only purpose they **need** to operate the platform is to distribute user media to the people of that user's choosing. Personally, I don't want my data used commercially, or to find my writing or person in the hands of advertisers{{< sidenote >}}I have zero expectations that loops.video will have an in-house advertising team. Do you?{{</sidenote>}}. And what's this 'otherwise'? Why isn't the distribution of content to the people of the user's choosing even mentioned{{< sidenote >}}To answer my own question: because loops.video is a data-scraping service, and not a video sharing platform.{{</sidenote>}}? +- `and to prepare derivative works of, or incorporate into other works, such Contributions` Just no? Ignoring the face meaning of this, of using user content for ads or making compilations of videos, _derivative works_ may easily include AI training. _Incorporating into other works_ is also a red flag, since a user may wish to maintain ownership and control over how their content is used. Fair use exists for a reason, and this clause completely bypasses that. +- `and grant and authorize sublicenses of the foregoing` Means they get to give any kind of license to user data and content to any party of their choosing. - In short, yes, loops.video does practically take full co-ownership of user content; the only right users keep is author's rights (the right to say they made the original content - but not any derivative works), and the right to grant licenses to the content to other entities aside from loops.video. @@ -200,7 +200,7 @@ Fair enough, but then...! Who are these trusted third parties? There's no way to tell. -But here's the point: these parties 'assist loops.video' in \`conducting their business\`. Wait, what? What business? What even _is_ loops.video's business model? So far, at least from my reading on their website, they don't have any sources of revenue. +But here's the point: these parties 'assist loops.video' in `conducting their business`. Wait, what? What business? What even _is_ loops.video's business model? So far, at least from my reading on their website, they don't have any sources of revenue. But here they're saying they **do** sell, trade or otherwise transfer data to 'trusted third parties' who assist them in 'conducting their business' 'so long as those parties agree to keep this information confidential.' diff --git a/content/blog/mastering-emacs.md b/content/blog/mastering-emacs.md index cf37c3b..a7eaad6 100644 --- a/content/blog/mastering-emacs.md +++ b/content/blog/mastering-emacs.md @@ -1,7 +1,7 @@ +++ title = "Weekend thoughts - Mastering Emacs by Mickey Petersen" publishDate = 2022-10-08T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["emacs", "review"] categories = ["books"] draft = false diff --git a/content/blog/misskey-resetting-admin-password.md b/content/blog/misskey-resetting-admin-password.md index 3280bb2..4c6101d 100644 --- a/content/blog/misskey-resetting-admin-password.md +++ b/content/blog/misskey-resetting-admin-password.md @@ -1,7 +1,7 @@ +++ title = "MissKey: Resetting Admin Password" publishDate = 2023-08-11T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["misskey", "admin", "postgres"] categories = ["tech"] draft = false diff --git a/content/blog/moving-to-hugo.md b/content/blog/moving-to-hugo.md index 778e05d..bd9ad3e 100644 --- a/content/blog/moving-to-hugo.md +++ b/content/blog/moving-to-hugo.md @@ -1,7 +1,7 @@ +++ title = "Moving to Hugo" publishDate = 2024-09-28T00:54:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["hugo", "web", "orgmode", "css", "tufte"] categories = ["tech", "emacs"] draft = false diff --git a/content/blog/my-favorite-factorio-mods.md b/content/blog/my-favorite-factorio-mods.md index d243a7e..2bfd2e6 100644 --- a/content/blog/my-favorite-factorio-mods.md +++ b/content/blog/my-favorite-factorio-mods.md @@ -1,7 +1,7 @@ +++ title = "My favorite Factorio mods" publishDate = 2023-07-24T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["factorio", "mods"] categories = ["videogames"] draft = false diff --git a/content/blog/new-keyboard-layout-colemak-dh.md b/content/blog/new-keyboard-layout-colemak-dh.md index 134537b..21c8c1d 100644 --- a/content/blog/new-keyboard-layout-colemak-dh.md +++ b/content/blog/new-keyboard-layout-colemak-dh.md @@ -1,7 +1,7 @@ +++ title = "Learning a new keyboard layout" publishDate = 2022-08-18T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["ergonomics", "keyboard", "colemak", "typing"] categories = ["body"] draft = false diff --git a/content/blog/on-problems.md b/content/blog/on-problems.md index 95c49e8..4cf8e10 100644 --- a/content/blog/on-problems.md +++ b/content/blog/on-problems.md @@ -1,7 +1,7 @@ +++ title = "On Problems" publishDate = 2022-11-21T00:00:00+01:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["psychology", "problems"] categories = ["mind"] draft = false diff --git a/content/blog/overcoming-rsi.md b/content/blog/overcoming-rsi.md index e44e400..ffcdf61 100644 --- a/content/blog/overcoming-rsi.md +++ b/content/blog/overcoming-rsi.md @@ -1,7 +1,7 @@ +++ title = "Overcoming typing-related RSI" publishDate = 2022-09-22T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["ergonomics", "keyboard", "typing", "rsi", "health"] categories = ["body"] draft = false diff --git a/content/blog/realistic-deadlines.md b/content/blog/realistic-deadlines.md index 2486f28..020f599 100644 --- a/content/blog/realistic-deadlines.md +++ b/content/blog/realistic-deadlines.md @@ -1,7 +1,7 @@ +++ title = "Realistic deadlines" publishDate = 2022-09-30T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["projectmanagement", "work"] categories = ["business"] draft = false diff --git a/content/blog/saas-business-foss.md b/content/blog/saas-business-foss.md index a5c11c0..e39d8b2 100644 --- a/content/blog/saas-business-foss.md +++ b/content/blog/saas-business-foss.md @@ -1,7 +1,7 @@ +++ title = "Some thoughts on SaaS and business applications of Free Software" publishDate = 2022-09-28T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["saas", "scam", "vendorlock", "interoperability"] categories = ["business"] draft = false diff --git a/content/blog/shared-hosting-scam.md b/content/blog/shared-hosting-scam.md index 2deda8b..f90c597 100644 --- a/content/blog/shared-hosting-scam.md +++ b/content/blog/shared-hosting-scam.md @@ -1,7 +1,7 @@ +++ title = "Shared hosting is a scam" publishDate = 2023-03-29T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["sharedhosting", "saas", "scam"] categories = ["tech"] draft = false diff --git a/content/blog/shiny-objects-and-learning.md b/content/blog/shiny-objects-and-learning.md index a816154..dd4f56c 100644 --- a/content/blog/shiny-objects-and-learning.md +++ b/content/blog/shiny-objects-and-learning.md @@ -1,7 +1,7 @@ +++ title = "Shiny objects, and learning" publishDate = 2024-04-24T00:00:00+02:00 -lastmod = 2025-01-17T12:07:32+01:00 +lastmod = 2025-01-17T12:10:30+01:00 tags = ["mindset", "attitude", "rant"] categories = ["business"] draft = false diff --git a/content/blog/vps-is-my-new-friend.md b/content/blog/vps-is-my-new-friend.md index 84bd6dd..d3643c5 100644 --- a/content/blog/vps-is-my-new-friend.md +++ b/content/blog/vps-is-my-new-friend.md @@ -1,7 +1,7 @@ +++ title = "VPS is my new friend" publishDate = 2022-10-07T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["vps", "sysadmin", "servers", "ssh", "sshfs", "foss", "vendorlock"] categories = ["tech"] draft = false diff --git a/content/blog/vps-setup.md b/content/blog/vps-setup.md index 4a96784..c3156c0 100644 --- a/content/blog/vps-setup.md +++ b/content/blog/vps-setup.md @@ -1,7 +1,7 @@ +++ title = "VPS set-up" publishDate = 2022-08-18T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["vps", "sysadmin", "servers"] categories = ["tech"] draft = false diff --git a/content/blog/wisdom-from-a-satyr.md b/content/blog/wisdom-from-a-satyr.md index 7262547..ef58a3f 100644 --- a/content/blog/wisdom-from-a-satyr.md +++ b/content/blog/wisdom-from-a-satyr.md @@ -1,7 +1,7 @@ +++ title = "Wisdom from a Satyr" publishDate = 2023-03-30T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["ethics", "suffering", "buddhism"] categories = ["wisdom", "mind"] draft = false diff --git a/content/blog/words-in-a-moment-of-peace.md b/content/blog/words-in-a-moment-of-peace.md index 31cac3b..a3527e1 100644 --- a/content/blog/words-in-a-moment-of-peace.md +++ b/content/blog/words-in-a-moment-of-peace.md @@ -1,7 +1,7 @@ +++ title = "Some words in a moment of peace" publishDate = 2023-04-04T00:00:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["language", "words", "meaning", "clarity", "communication"] categories = ["mind"] draft = false diff --git a/content/blog/zucc-may-be-lying.md b/content/blog/zucc-may-be-lying.md index dd61cc5..c336297 100644 --- a/content/blog/zucc-may-be-lying.md +++ b/content/blog/zucc-may-be-lying.md @@ -1,7 +1,7 @@ +++ title = "On Mark Zuckerberg's recent claims" publishDate = 2024-09-27T12:02:00+02:00 -lastmod = 2025-01-17T12:07:31+01:00 +lastmod = 2025-01-17T12:10:29+01:00 tags = ["copyright", "zuckerberg"] categories = ["tech", "llm"] draft = false diff --git a/content/contact/index.md b/content/contact/index.md index 8034b1a..9c6054a 100644 --- a/content/contact/index.md +++ b/content/contact/index.md @@ -1,7 +1,7 @@ +++ title = "Contact" publishDate = 2023-06-20T00:35:00+02:00 -lastmod = 2025-01-17T12:07:30+01:00 +lastmod = 2025-01-17T12:10:28+01:00 draft = false hidefromhome = true meta = false