#Google #Search Asked to Remove One Billion ‘Pirate’ Links in 9 Months

source: https://torrentfreak.com/google-search-asked-to-remove-one-billion-pirate-links-in-9-months-230807/

Looking more closely at the timeline, we see that a billion #URLs were reported to Google search in less than nine months. For comparison, it took twice as long to go from five to six billion, suggesting that the #takedown volume picked up again after a previously reported decline.

#internet #piracy #copyright #economy #news #url

Rant: Open Source and the concept of: Release early, release often or publish early & publish often -> continuous development/continuous integration (CD/CI) -> tight loops ok but still - linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup…

https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

1. bad url management:
   • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
     • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
   • or maybe it’s wrongful integration? (but maybe it just sucks)
   • why is every developer-user using it?

• PS: as mankind still ponders and evolves (by making mistakes) how to best deal with computers
  • yes someone said “publish early” & “publish often” (doing this with the blog… also… often too often and too early X-D)
    • or: “Release early, release often” (wiki)
      • “tight feedback loop between developers and testers or users” (wiki) - yeah sure as a developer that might be a good thing, as a user… really doubt it… - there are highly intelligent respected developers that pioneered this concept… it might work for small teams… (of one)
      • “This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated “Release early. Release often. And listen to your customers”.[4]”“This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development.””The alternative to the release early, release often philosophy is aiming to provide only polished, bug-free releases.[5] Advocates of RERO question that this would in fact result in higher-quality releases.[4]“
    • has this lead to every developer going in the: continuous development/continuous integration direction? (definately sounds like it)
      • it really should be called CD/CI not CI/CD because first comes the development, then the integration (but well hewego: CI/CD@RedHat)
      • still pondering if it’s really a good idea - well if software quality sticks to UNIX principles of K.I.S.S (most do not and have NO IDEA what non-K.I.S.S means for their software-project or company: - it is the difference between: - lost in chaos of complexity = dysfunctionality - vs a lean stream of running smooth software-company - src: https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s07.html - plus test-driven development: 100.000 use case checks tested afterwards automatic & semi-automatic & manual - than that probably works (but then that is what needs to be done anyway to ensure good software quality) - plus: maybe a feedback channel that does not de-motivate - always say something positive first - then the critique
      • signal.org is a very cool mobile & desktop messenger (that usually works pretty well) but: - what is already annoying: if updates per program are 100MBytes and more… (always downloads the full thing (signal.org desktop client) no differential updates?)
• word of advice: never blindly follow “the trends”
  • always think for yourself, “does it make sense”?
    • test it if it works for you, if not, drop it, what’s the point?

imho gotta to do both…

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects #ci-cd #cd-ci #CICD #CDCI #dev #systems #system #company #developers #developer #buckminster #buckminister

Originally posted at: https://dwaves.de/2022/02/03/rant-open-source-and-the-concept-of-release-early-release-often-or-publish-early-publish-often-continuous-development-continuous-integration-cd-ci-tight-loops-ok-but-still-linking-to-n/

Rant: Open Source and the concept of: Release early, release often or publish early & publish often -> continuous development/continuous integration (CD/CI) -> tight loops ok but still - linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup…

https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

1. bad url management:
   • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
     • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
   • or maybe it’s wrongful integration? (but maybe it just sucks)
   • why is every developer-user using it?

• PS: as mankind still ponders and evolves (by making mistakes) how to best deal with computers
  • yes someone said “publish early” & “publish often” (doing this with the blog… also… often too often and too early X-D)
    • or: “Release early, release often” (wiki)
      • “tight feedback loop between developers and testers or users” (wiki) - yeah sure as a developer that might be a good thing, as a user… really doubt it… - there are highly intelligent respected developers that pioneered this concept… it might work for small teams… (of one)
      • “This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated “Release early. Release often. And listen to your customers”.[4]”“This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development.” “The alternative to the release early, release often philosophy is aiming to provide only polished, bug-free releases.[5] Advocates of RERO question that this would in fact result in higher-quality releases.[4]“
    • has this lead to every developer going in the: continuous development/continuous integration direction? (definately sounds like it)
      • it really should be called CD/CI not CI/CD because first comes the development, then the integration (but well hewego: CI/CD@RedHat)
      • still pondering if it’s really a good idea - well if software quality sticks to UNIX principles of K.I.S.S (most do not and have NO IDEA what non-K.I.S.S means for their software-project or company: - it is the difference between: - lost in chaos of complexity = dysfunctionality - vs a lean stream of running smooth software-company - src: https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s07.html - plus test-driven development: 100.000 use case checks tested afterwards automatic & semi-automatic & manual - than that probably works (but then that is what needs to be done anyway to ensure good software quality) - plus: maybe a feedback channel that does not de-motivate - always say something positive first - then the critique
      • signal.org is a very cool mobile & desktop messenger (that usually works pretty well) but: - what is already annoying: if updates per program are 100MBytes and more… (always downloads the full thing (signal.org desktop client) no differential updates?)
• word of advice: never blindly follow “the trends”
  • always think for yourself, “does it make sense”?
    • test it if it works for you, if not, drop it, what’s the point?

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects #ci-cd #cd-ci #CICD #CDCI #dev #systems #system #company #developers #developer

Originally posted at: https://dwaves.de/2022/02/03/rant-open-source-and-the-concept-of-release-early-release-often-or-publish-early-publish-often-continuous-development-continuous-integration-cd-ci-tight-loops-ok-but-still-linking-to-n/

Rant: Open Source and the concept of: Release early, release often or publish early & publish often -> continuous development/continuous integration (CD/CI) -> tight loops ok but still - linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup…

https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

1. bad url management:
   • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
     • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
   • why is every developer-user using it?

• PS: as mankind still ponders and evolves (by making mistakes) how to best deal with computers
  • yes someone said “publish early” & “publish often” (doing this with the blog… also… often too often and too early X-D)
    • or: “Release early, release often” (wiki)
      • “tight feedback loop between developers and testers or users” (wiki) - yeah sure as a developer that might be a good thing, as a user… really doubt it…
    • has this lead to every developer going in the: continuous development/continuous integration direction? (definately sounds like it)
      • it really should be called CD/CI not CI/CD because first comes the development, then the integration (but well hewego: CI/CD@RedHat)
      • still pondering if it’s really a good idea - well if software quality sticks to UNIX principles of K.I.S.S (most do not) - plus test-driven development: 100.000 use case checks tested afterwards automatic & semi-automatic & manual - than that probably works (but then that is what needs to be done anyway to ensure good software quality) - plus: maybe a feedback channel that does not de-motivate - always say something positive first - then the critique
      • signal.org is a very cool mobile & desktop messenger (that usually works pretty well) but: - what is already annoying: if updates per program are 100MBytes and more… (always downloads the full thing (signal.org desktop client) no differential updates?)
• word of advice: never blindly follow “the trends”
  • always think for yourself, “does it make sense”?
    • test it if it works for you, if not, drop it, what’s the point?

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects #ci-cd #cd-ci #CICD #CDCI #dev

Originally posted at: https://dwaves.de/2022/02/03/rant-open-source-and-the-concept-of-release-early-release-often-or-publish-early-publish-often-continuous-development-continuous-integration-cd-ci-tight-loops-ok-but-still-linking-to-n/

linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup…

https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

1. bad url management:
   • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
     • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
   • why is everyone using it?

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects

Originally posted at: https://dwaves.de/2022/06/03/linking-to-nirvana-without-redirection-badly-written-software-that-everyone-uses-another-case-of-nothing-works-ok-klarer-fall-von-nichts-funktioniert-ok/

My Dearest Edelman Trust Barometer Task Force and Web Team:

A friend brought my attention to the Edelman Trust Barometer report, by way of an Axios reference.

Unfortunately, the article failed to link the report directly, though a quick Web search brought up the 2019 report at:

https://www.edelman.com/trust-barometer

Further exploration determined that the 2020 report is found at

https://www.edelman.com/trustbarometer

I quickly noted the innovative and space-efficient versioning method of removing a hyphen.

This thought was rapidly followed by the realisation that such a techique WILL NOT BE AVAILABLE in future releases of the report, and may require some further innovation.

I offer my services freely in addressing this urgent and deadline-critical need.

Comparing the years "twenty nineteen" and "twenty twenty", we note the finial 'y' which is found in "hyphern". Which seems to explain the governing rationale.

Next comparing "twenty twenty" and "twenty twenty-one", we note that the letter 'n' appears three times, as an outlier from earlier notations. A doubled 'n' ("nn") resembles an "m", so I suggest the 2021 URL:

https://www.edelman.com/trustbaroeter

As we move onwards, into the future, to "twenty twenty-two", the prevalence of the letter "t" has become unmistacable, and strongly suggests the next versioning variant: drop the 't's:

https://www.edelman.com/rusbaroeer

Now, I'll admit that "twenty twenty-three " presents several options, all obvious, and none particularly recommending itself, though the poetry of the doubled 'ee' sequence, along with the numerous other 'e's, could make the following an option, though I'd recommend forming a working group to discuss the impact and market reception:

https://www.edelman.com/rusbaror

With "twenty twenty-four", we have the highly distinctive 'r', an easy choice, and patriotic to boot!

https://www.edelman.com/usbao

For "twenty twenty-five", the solution may at first appear confusing, but is clearly:

https://www.edelman.com/usao

This should suffice to provide a set of distinctive URLs for the next five years, which in the best central-planning tradition should be adequate for now.

Or, you know, you could just add in the year:

https://www.edelman.com/trustbarometer-2020

---

Sent from ProtonMail mobile

#edelman #versioning #urls #ThisIsSatire #ButYesIReallyDidEmailThem