Stefan Tilkov retweeted
Irre, dass @c_drosten explizit genau diesen Fall in seinem Podcast vor 3 Wochen vorausschauen behandelt und @peteraltmeier's Rhetorik als Wissenschaftsleugnung bezeichnet hat.
.@c_drosten beschuldigt Altmaier der Wissenschaftsleugnung:
Da wird die Öffentlichkeit getäuscht, wenn
gesagt wird: „Wir wissen ja noch gar nicht, wo das
Virus übertragen wird, da muss noch viel geforscht
werden“ und solche Dinge. Das ist falsch, das ist
Wissenschaftsleugnung
7
269
8
1,650
Stefan Tilkov retweeted
Software Architecture and Design Practice Reference leanpub.com/b/software-archi… by Cesare Pautasso, Olaf Zimmermann and Mirko Stocker is the featured bundle on the Leanpub homepage! leanpub.com cc @pautasso @m_st
6
29
Somebody tweeted about FTP‘s 50th birthday and I got curious. And what else is there to do on a Friday night?
1
Stefan Tilkov retweeted
Ich finde, da müsste man jetzt dringend mal anfangen, einen Termin über eine Ministerpräsidentenkonferenz im Mai oder Juni abzustimmen, um dort Vorschläge zu erarbeiten, in welcher Zuständigkeit man künftig entscheiden kann, welche Arbeitsgruppe sich künftig darum kümmern soll.
Das gab es noch nie!!!
Alle Intensivstationen im gesamten Großraum Nbg/FÜ/ER sind bei der Leitstelle abgemeldet. Für Covid- und für Nicht-Covid Patienten!
Also besser heute Nacht keinen Herzinfarkt bekommen😥
Was muss noch passieren, ehe die Politik reagiert???
#NoCovid
14
71
3
275
Amen: “There are many good reasons, and maybe one or two bad ones, for making it appear that communication over the Network is only a special case of input/output” tools.ietf.org/html/rfc91, December 27, 1970
1
6
lol: “An important characteristic of most of the users […] is a lack of sophistication about data communication techniques and practices. The user will eventually be in the majority of those using the network […] but the problem is ours from the start.“ tools.ietf.org/html/rfc76
1
4
“The IPC described in the previous section easily generalizes to allow interprocess communication between processes at geographically different locations as, for example, within a computer network.” tools.ietf.org/html/rfc62, 3 August 1970
“If you are working to develop methods of communications within a computer network, you can engage in one of two activities.” Beginning of a killer 1st paragraph in tools.ietf.org/html/rfc62, 3 August 1970
5
I am unsure what to think of “CR = HOMOSEX Incorrect send/receive pair” tools.ietf.org/html/rfc55 TBQH
1
This predates TCP/IP by about 650 RFCs and half a decade, so I’m not 100% sure :) My understanding is it’s the physical endpoints, so probably analogous to network interfaces of today
1
1
“Notably lacking was any criticism of the basic concepts of sockets and connections. (Some have since surfaced.)” tools.ietf.org/html/rfc37, 20 March 1970
“Some interest has been expressed in a live presentation, so we will host a network meeting on Tuesday, March 17, at UCLA at 9:00 a.m.” tools.ietf.org/html/rfc35, 3 March 1970
“At UCLA, we will implement our tables to take advantage of this limitation. We also note that 32 may be even more realistic, but 64 is certainly sufficient.” tools.ietf.org/html/rfc25, 30 October 1969
“Because it may be desirable to reserve one or more link numbers for instrumentation purposes, and because 256 link numbers are many more than are needed, we suggest that no link number over 63 be used.”
2
1
“A sub-system called "Telnet" is proposed which is a shell program around the network system primitives, allowing a teletype or similar terminal at a remote host to function as a teletype at the serving host.” tools.ietf.org/html/rfc15, 25 September 1969
1
2
7