Re: Leo Node Move Error

2020-09-03 Thread k-hen
As a follow up: I figured out the grey box, it's just the unsaved/dirty nodes, so it's not that. Regarding the file size for the DB, I assume this is because the version I sent you doesn't have any content. So I think this is a legitimate size for the doc, but it probably needs to be

Re: Leo Node Move Error

2020-09-03 Thread perceptiblelogic
Hmm ... well at least it seems reproduceable. I did run across at least one set of nodse after filing this that were behaving as clones but not flagged as clones, and it's probably the same ones. Not sure if it matters but the box icon was grey instead of black, I thought that was unusual as

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

2020-09-03 Thread Thomas Passin
The pylint message about an undefined variable was mistaken because that variable can only be used after the condition has been met. Tested to confirm. I have created a PR for this updated version. Unless someone reports anything seriously wrong or trivial to fix in the next few days, I will

Re: Wow: wasmtime

2020-09-03 Thread Edward K. Ream
On Thursday, September 3, 2020 at 11:00:38 AM UTC-5, vitalije wrote: > By definition wasm code can't do anything that ordinary javascript in the browser can't do... > Concerning user tracking, all major social networks use it all the time, regardless of wasm... > Comparison with the Flash

Re: Leo Node Move Error

2020-09-03 Thread Edward K. Ream
On Wednesday, September 2, 2020 at 3:24:45 PM UTC-5, k-hen wrote: Ok, got it, will need a bit of time, but will get back to you soon. > Something strange is going on. Here is what I think I know: The unpacked original file is leo_error_test_01 - cleared - Copy.db. It is about 28.1 MB in size.

Re: Wow: wasmtime

2020-09-03 Thread vitalije
> > I forgot to include the potential for malware. Some links: > According to the research mentioned in your third link that claims half of the web sites using wasm use it maliciously, the malicious usage consist in obfuscating and mining. According to the first link, from the figure 4 it

Re: Wow: wasmtime

2020-09-03 Thread Edward K. Ream
On Thu, Sep 3, 2020 at 10:23 AM Thomas Passin wrote: > I forgot to include the potential for malware. Some links: https://www.virusbulletin.com/virusbulletin/2018/10/dark-side-webassembly/#h4-webassemblys-date-malware

Re: Wow: wasmtime

2020-09-03 Thread Thomas Passin
Yes, that's so, and I understand that web assemblies are basically a Google effort to do that. On Thursday, September 3, 2020 at 11:20:12 AM UTC-4, lun...@gmail.com wrote: > > You're giving technology and standards too much credit. Corporations are > going to create closed systems and implement

Re: Wow: wasmtime

2020-09-03 Thread Thomas Passin
On Thursday, September 3, 2020 at 11:00:48 AM UTC-4, Edward K. Ream wrote: > > > > On Thu, Sep 3, 2020 at 7:41 AM Thomas Passin > wrote: > >> I am so opposed to webassemblies that I don't want to work on them. Web >> assemblies if widespread will encourage the trend towards breaking the web >>

Re: Wow: wasmtime

2020-09-03 Thread lun...@gmail.com
You're giving technology and standards too much credit. Corporations are going to create closed systems and implement data hiding no matter the tools they have at hand and they're going to continue to do it mercilessly unless socially/culturally disincentivized to do so. Web assemblies will

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

2020-09-03 Thread Thomas Passin
On Thursday, September 3, 2020 at 10:59:41 AM UTC-4, Edward K. Ream wrote: > > >> Actually, I knew about it. I'm not sure if it's real or something that >> pylint doesn't understand (I think it's this). >> > > If it's a pylint mistake, please disable the message. > I will once I'm sure. I

Re: Wow: wasmtime

2020-09-03 Thread Edward K. Ream
On Thu, Sep 3, 2020 at 7:41 AM Thomas Passin wrote: > I am so opposed to webassemblies that I don't want to work on them. Web > assemblies if widespread will encourage the trend towards breaking the web > by making URLs meaningless, and will promote more closed silos and data > hiding. > I

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

2020-09-03 Thread Edward K. Ream
On Thu, Sep 3, 2020 at 7:30 AM Thomas Passin wrote: > > pylint gives this complaint: >> >> * Module leo.plugins.viewrendered3 >> leo\plugins\viewrendered3.py:1803:23: E0602: Undefined variable >> 'AsciiDocError' (undefined-variable) >> >> Do you get the same complaint? If so, please

Re: Wow: wasmtime

2020-09-03 Thread Thomas Passin
I am so opposed to webassemblies that I don't want to work on them. Web assemblies if widespread will encourage the trend towards breaking the web by making URLs meaningless, and will promote more closed silos and data hiding. I do see that they could be very good in non-web use, but that's

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

2020-09-03 Thread Thomas Passin
On Thursday, September 3, 2020 at 7:20:39 AM UTC-4, Edward K. Ream wrote: > > > > On Wednesday, September 2, 2020 at 10:30:08 PM UTC-5, Thomas Passin wrote: >> >> I've just submitted a pull request for viewsarendered3 v3.0b14 >> > > I've merged the PR. pylint gives this complaint: > >

Wow: wasmtime

2020-09-03 Thread Edward K. Ream
As part of my "what's next for Leo" project, I decided to check in on what's new with webassembly. Here is my google trail: webAssembly: https://webassembly.org/ non-web Embeddings (because Leo doesn't run on the web): https://webassembly.org/docs/non-web/ WebAssembly High-level goals:

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

2020-09-03 Thread Edward K. Ream
On Wednesday, September 2, 2020 at 10:30:08 PM UTC-5, Thomas Passin wrote: > > I've just submitted a pull request for viewsarendered3 v3.0b14 > I've merged the PR. pylint gives this complaint: * Module leo.plugins.viewrendered3 leo\plugins\viewrendered3.py:1803:23: E0602: