●● IRC: #boycottnovell @ FreeNode: Friday, November 20, 2020 ●● ● Nov 20 [00:54] *liberty_box has quit (Ping timeout: 260 seconds) [00:54] *rianne_ has quit (Ping timeout: 260 seconds) [00:54] *rianne_ (~rianne@host81-154-173-112.range81-154.btcentralplus.com) has joined #boycottnovell [00:56] *liberty_box (~liberty@host81-154-173-112.range81-154.btcentralplus.com) has joined #boycottnovell ● Nov 20 [06:22] schestowitz >> roy@vonick:~$ ls -la ./irc-log-techrights-151120.html 15.txt [06:22] schestowitz >> -rw-r--r-- 1 roy roy 78331 Nov 18 22:00 15.txt [06:22] schestowitz >> -rw-r--r-- 1 roy roy 277998 Nov 16 00:02 ./irc-log-techrights-151120.html [06:22] schestowitz >> [06:22] schestowitz > Must be denser than average web pages then. The average web page has [06:22] schestowitz > 99% cruft and < 1% information. [06:23] schestowitz > [06:23] schestowitz > The web pages themselves could be trimmed by eliminating the inline [06:23] schestowitz > styles plus perhaps a few other tweaks, but by and large XHTML is going [06:23] schestowitz > to take more place than raw, unstructured text. [06:23] schestowitz Should we start uploading these? I was told that, if we do go ahead, then separate file for each channel. [06:42] *Blakereeate (~jaqueline@45.87.213.20) has joined #boycottnovell [06:43] *Blakereeate has quit (K-Lined) [06:52] schestowitz I have begun implementing this. While testing, I noticed encoding anomalies in two output files (you will see this as soon of you open these). Any idea how to overcome that? Once done, what remains is linking them in the HTML bit template that goes into WordPress (I think you have your own program for that), then worry about all the IPFS bits. [06:53] schestowitz Keeping thunderbird open for a bit if you can reply asap. [06:55] schestowitz | [06:55] schestowitz > [06:55] schestowitz Yes, separate files would be good. [06:55] schestowitz for f in ./irc-log-*$(date -d "-1 day" +"%d%m%y").html; [06:55] schestowitz do [06:55] schestowitz echo $f; [06:55] schestowitz t=${f%.html}.txt; [06:55] schestowitz echo $t; [06:55] schestowitz ./xhtml-log-to-text.pl < $f > $t; [06:55] schestowitz done [06:55] schestowitz " [06:55] schestowitz > [06:55] schestowitz Yes, separate files would be good. [06:55] schestowitz for f in ./irc-log-*$(date -d "-1 day" +"%d%m%y").html; [06:55] schestowitz do [06:55] schestowitz echo $f; [06:55] schestowitz t=${f%.html}.txt; [06:55] schestowitz echo $t; [06:55] schestowitz ./xhtml-log-to-text.pl < $f > $t; [06:55] schestowitz done [06:55] schestowitz " ● Nov 20 [07:01] schestowitz > Do you mean the \xa0? Those were as HTML I can map those to [07:01] schestowitz > normal spaces. [07:01] schestowitz If those are the culprits, as per the output files, then yes, please. [07:01] schestowitz I can start by making text versions for the past ~3 weeks, then upload those to ipfs, update index etc. [07:04] schestowitz
[07:05] schestowitzThe entry level to the list moved up to 1.32 petaflops on the High Performance Linpack (HPL) benchmark, a small increase from 1.23 petaflops recorded in the June 2020 rankings. In a similar vein, the aggregate performance of all 500 systems grew from 2.22 exaflops in June to just 2.43 exaflops on the latest list. Likewise, average concurrency per system barely increased at all, growing from 145,363 cores six [07:05] schestowitz months ago to 145,465 cores in the current list.
[07:05] schestowitzThere were, however, a few notable developments in the top 10, including two new systems, as well as a new highwater mark set by the top-ranked Fugaku supercomputer. Thanks to additional hardware, Fugaku grew its HPL performance to 442 petaflops, a modest increase from the 416 petaflops the system achieved when it debuted in June 2020. More significantly, Fugaku increased its performance on the new mixed [07:05] schestowitz precision HPC-AI benchmark to 2.0 exaflops, besting its 1.4 exaflops mark recorded six months ago. These represents the first benchmark measurements above one exaflop for any precision on any type of hardware.
-viera/#techrights-Tux Machines: Fedora 33 elections voting now open http://www.tuxmachines.org/node/144533 [https://pleroma.site/objects/d9fd49b9-80fb-4eec-8588-1be28716a55b] | http://www.tuxmachines.org/node/144533https://pleroma.site/objects/d9fd49b9-80fb-4eec-8588-1be28716a55b] | Nov 19 01:55 |