xtf

Needs websitecode to be public, if this AGPL-Programm is shown in an I-Frame?

https://github.com/cdr/code-server

Have my multimedia in browsers, kde recognizes it and media controls work within taskbar preview, notification area and - most important - with the media keys.

Plus: Browsers are more secure and no need for other applications.

Just a simple one when needed. cp, downloader, etc. Nothing too complicated.

my simple jobqueue, if I need one

  waitfor() {
    while pgrep $1 >/dev/null; do sleep 2; done && $*
  }

With Apache License they don't have to contribute back and it is questionable/unlikely they'll do.

And that is what xmpp already offers

They use captcha to help AI to identify things, therefore: Keep it in the US

Sane defaults reduce complexity

And new systems resulting out of old understood ones, like SI-Units vs imperial units

seems so, germany

The blob: https://github.com/GPUOpen-LibrariesAndSDKs/RadeonRays_SDK/t...

Invented to describe what's being discovered.

And it seams to be for MacOS, at least. May be portable, but don't know.

Worst project-documentation 2020, so far.

Network Wide > Pi-hole

Browser > Ublock

Local System > hosts-file

Android (root) > Adaway (does hosts-file)

Problem is the scale. Script kiddies and junior programmers are 0.1x to 0.6x or people reinventing the wheel by not using a framework, they could be far less and let's not talk about security. Experienced (senior) devs should be counted as 1x. Beside knowing to programming fast, they (should) know how programm more correctly.

They also can use and improve it and give these improvements back to the source.

Tried to write it down and help to enhance the documentation, or written an own documentation? So that reoccurring questions could be reduced.

I would not put my data on the wild web, especially phone and address.

I have my own responsive, displayagnostic, offlinecapable cv and think everyone should have his own, because it is a platform for showing off your skills.

In the 80s there were plans to roll out fiber every with a 30 year plan under chancellor Schmidt, but with reunifiction plans got dismissed.

http://www.bundesarchiv.de/cocoon/barch/00/k/k1981k/kap1_1/k...

Then it got me there. And in respect to a satire, then it's a good one. Reverse it and you have a more accurate Webdev '19 Article.

IMHO Wrong:

1. Mobile App. The site has to work by itself. Else go PWA

2. DNT. Respect Users decisions. Allow cookieless and JSless.

3. See 2.

4. See 2. + I would't disable adblock in the net, because it the main entry for malware.

5. Block Foreign. Expand as you understand the laws.

6. Max Layout. Called Mobile First, and seams to be national behavior. International pages sometimes look foreign to me. Use your screenspace wisely, yes.

7. Use Notifications. OK, but, see 8 and 9.

8. Prompt User. Don't annoy users. If they are on the net, they know how it regulary works, don't get of the standard behavior patterns.

9. Allow Opt-out. Opt-In is the way to go, else maybe violates GDPR and other laws.

10. Use Javascript. Not all websites require Javascript, most yes, but not all. Don't rely on it, especially impaired users will hat you for 'visually correct' but not screenreader enabled. Use standards.

PS: Don't be an apple hipster. Was biased from the beginning, got confirmed. But, read it.

Simply put: Don't write for chrome, write w3c conform.

Or better: Use standards which match most browsers at caniuse.com

New Reiwa era, bad bamboo omen. OK

Except further optimisation in Cython like http://docs.cython.org/en/latest/src/tutorial/pure.html#stat...

this - it goes viral

Everyone is in the net.

- malicious activity such as hacking and harassment

- problematic system design such as business models that reward clickbait

- unintended consequences, such as aggressive or polarised discussions

These are problems of human evolvement. Education, education, education and not screaming at each other and discussing with the opposition till consensus.

AMD calls their CPU with integrated Graphics APU (Accelerated Processing Units), why not thinking that forth, oh OpenAL (Audio Library) is already in use, WebAL would confuse more. We are running out of acronyms.

Throwing in some random word creations: * Processing#, * UnifiedProcessing#, * ParallelProcessing#, * Accel#,

Prefixes *: Web/Open/Lib/Imperial/Federal/Continuum

#Suffixes: Library/Hole/Sink/Chain/[not Unit (it's for Hardware)]

WebGPU. That's an awful name. Given WebGL is taken and already in version 2. But WebGPU sounds like a virtual GPU for GameStreaming. Even GLWeb would be nicer.

And it's nothing new.

Same is possible with Raspberry Pi GPIO:

https://github.com/F5OEO/rpitx