●● IRC: #techbytes @ FreeNode: Friday, January 15, 2021 ●● ● Jan 15 [00:03] *Techrights-sec has quit (*.net *.split) [00:03] *hook54321 has quit (*.net *.split) [00:05] *hook54321 (sid149355@gateway/web/irccloud.com/x-doftibnowizrzpao) has joined #techbytes [00:06] *Techrights-sec (~quassel@host81-154-171-38.range81-154.btcentralplus.com) has joined #techbytes [00:07] *hook54321 has quit (Ping timeout: 272 seconds) [00:11] *hook54321 (sid149355@gateway/web/irccloud.com/x-wpctizkmwlnpwwmd) has joined #techbytes [00:37] *liberty_box (~liberty@host81-154-171-38.range81-154.btcentralplus.com) has joined #techbytes [00:37] *rianne_ (~rianne@host81-154-171-38.range81-154.btcentralplus.com) has joined #techbytes ● Jan 15 [03:14] *Techrights-sec has quit (Quit: No Ping reply in 180 seconds.) [03:14] *Techrights-sec (~quassel@host81-154-171-38.range81-154.btcentralplus.com) has joined #techbytes ● Jan 15 [04:14] *randomgry (~test@unaffiliated/gryllida) has joined #techbytes [04:14] *gry has quit (Ping timeout: 240 seconds) [04:18] *randomgry is now known as gry [04:20] *acer-box__ has quit (Remote host closed the connection) [04:21] *acer-box__ (~acer-box@unaffiliated/schestowitz) has joined #techbytes ● Jan 15 [06:40] *GNUmoon has quit (Ping timeout: 240 seconds) ● Jan 15 [07:24] Techrights-sec gm [07:24] Techrights-sec The IPFS bandwidh reports in IRC are still "" and not ASCII graphics. [07:24] Techrights-sec http://techrights.org/irc-archives/irc-log-techrights-140121.html#tJan%2014%2023:20:02 [07:24] -TechBytesBot/#techbytes-techrights.org | IRC: #techrights @ FreeNode: Thursday, January 14, 2021 [07:27] schestowitz I got those to work OK in most IRC clients that I have tested with. However, the python program I use for HTML logs does not cope. It's something in the encoding. One option I have is to write some program to convert, but an easier workaround is leaving out all those lines, or blanking out bits of them. Those are standard unicode characters, so another option is to experiment with another type of indicator for volume. What can be used [07:27] schestowitz other than horizontal bars? Hex? [07:28] Techrights-sec https://theasciicode.com.ar/extended-ascii-code/graphic-character-low-density-dotted-ascii-code-176.html [07:28] -TechBytesBot/#techbytes-theasciicode.com.ar | ASCII code Graphic character, low density dotted, American Standard Code for Information Interchange, The complete ASCII table, characters,letters, vowels with accents, consonants, signs, symbols, numbers graphic, character, low, density, dotted,ascii,176, ascii art, ascii table, code ascii, ascii character, ascii text, ascii chart, ascii characters, ascii codes, characters, codes, tables, symbols, list, alt, keys, keyb [07:29] schestowitz I considered those, but the gradients are 3 or 4 in scale, unlike 0-8 [07:30] Techrights-sec https://theasciicode.com.ar/extended-ascii-code/graphic-character-low-density-dotted-ascii-code-176.html [07:30] Techrights-sec That has 219 and 220 and32 -- in decimal [07:30] Techrights-sec Otherwise python's unicode support needs to be figured to get 0 to 8 scale [07:31] schestowitz I am going to experiment this morning, we start workout shortly, then I need to record InteLeaks (my new routine) [07:31] Techrights-sec It might be tricker to stack them in two rows. That would give 0 to 8 but [07:31] Techrights-sec only if they line up. [07:31] schestowitz That would add more clutter to IRC, doubling it [07:32] schestowitz I also wrote a 100-line python program to make the LEDs pulsate 24/7 to show up/down traffic [07:33] Techrights-sec I haven't used python3 for text processing at all. I was going to [07:33] Techrights-sec move to rakulang from perl5 instead. [07:34] schestowitz In the page you have cited, the chars I use and the ones you have highlighted (and I had originally considered) are both under "Extended ASCII", so good chance is, python would choke on those too [07:35] Techrights-sec U+2581 through U+2588 would work, but those are what you are trying? [07:36] schestowitz What I really die for right now is a GOOD, proper image->unicode covertor, for images in bulletins. I know some exist, but nothing on Debian and not free software. The ones I found are dumb and shitty algos [07:36] Techrights-sec I presume you've seen the main documentation? [07:36] Techrights-sec https://docs.python.org/3/howto/unicode.html [07:36] -TechBytesBot/#techbytes-docs.python.org | Unicode HOWTO Python 3.9.1 documentation [07:37] schestowitz I did not check python docs. One option is to sed those 8 symbols [07:37] Techrights-sec Sed would be a bad choice, it is a matter of setting the encoding / decoding [07:37] Techrights-sec correctly for input, I would guess. [07:37] Techrights-sec \ [07:38] schestowitz That might introduce new side issues, so I am reluctant, let me check the code... [07:39] schestowitz #!/usr/bin/env python [07:39] schestowitz # -*- coding: utf-8 -*- [07:40] schestowitz funny thing is, one original author was jeff waugh (yeah, that one) [07:42] Techrights-sec https://docs.python.org/3/howto/unicode.html#reading-and-writing-unicode-data [07:42] -TechBytesBot/#techbytes-docs.python.org | Unicode HOWTO Python 3.9.1 documentation [07:45] schestowitz (to self) TODO: 1) bulletin image->unicode (did lots of searching, installed programs, used web-based stuff... all crap), 2) encoding issue for bot, 3) connection issues. [07:46] schestowitz I think I'm OK with the tools I use for videos now. OBS wasn't explored, but I'm fine with what already works anyway and it's actively maintained, too... [07:47] schestowitz I've just grepped logs, over 50,000 hits on videos in techrights over the past 5 days [07:52] schestowitz seems the issue boils down to xchat, not python [07:53] schestowitz Jan 14 02:20:02 IPFS downstream, 60 minutes: ^a$ [07:53] schestowitz Jan 14 02:36:41 * mmu_man has quit (Ping timeout: 256 seconds) [07:53] schestowitz This is strange as originally those things showed up fine in xchat, but not in konversation, and now it is the opposite [07:55] schestowitz yes stranger: on another machine of mine xchat handles fine with it, maybe it's an issue with my local configs in xchat ● Jan 15 [08:04] schestowitz test: [08:04] schestowitz [08:04] schestowitz [07:20] IPFS downstream, 60 minutes: IPFS upstream, 60 minutes: [08:07] Techrights-sec I am not familiar enough with the parts to guess. I would otherwise check [08:07] Techrights-sec the data at each stage of work to see what is actually present. [08:07] schestowitz I have just checked on 3 laptops. xchat-gnome deals OK with it, not 2019 build for debian buster [08:07] schestowitz I at least narrowed that down to the IRC client itself, the input files that go into python are already garbage [08:07] schestowitz I will experiment for a bit [08:08] schestowitz http://xchat.org/encoding/ [08:08] -TechBytesBot/#techbytes-xchat.org | XChat - IRC (chat) client for UNIX ● Jan 15 [10:02] schestowitz I think I've fixed this, we'll know tomorrow, fastest way to check is to see noticed past 10am [10:02] schestowitz I think I've fixed this, we'll know tomorrow, fastest way to check is to see notices past 10am ● Jan 15 [11:08] *Techrights-sec has quit (Quit: No Ping reply in 180 seconds.) [11:08] *Techrights-sec (~quassel@host81-154-171-38.range81-154.btcentralplus.com) has joined #techbytes [11:25] *GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) has joined #techbytes [11:27] *GNUmoon has quit (Remote host closed the connection) [11:27] *GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) has joined #techbytes ● Jan 15 [15:46] schestowitz [15:42] The same Nazi tool, AIfied: determine political views with facial recognition https://www.nature.com/articles/s41598-020-79310-1 [15:46] -TechBytesBot/#techbytes-www.nature.com | Facial recognition technology can expose political orientation from naturalistic facial images | Scientific Reports