Re: [twdev] Re: Tiddloid - A new android editor is to be released

[TonyM]

donmor I will try and get hold of the app and provide any feedback

Tony

On Monday, May 20, 2019 at 2:33:56 PM UTC+10, donmor3000 wrote:
>
> Thanks. I sent the PR minutes ago.
> BTW I uploaded an apk to my repository on github so that everyone can get 
> it before included into app stores.
>
> 在 2019年5月19日星期日 UTC+8下午7:05:53，Jeremy Ruston写道：
>>
>> Hi Donmor
>>
>> Congratulations. Do feel free to send a PR to add a new “Resources” 
>> tiddler to tiddlywiki.com.
>>
>> Best wishes
>>
>> Jeremy.
>>
>> On 19 May 2019, at 07:50, TonyM  wrote:
>>
>> donmor3000
>>
>> Sounds like we are lucky to have you in the community.
>>
>> Regards
>> Tony
>>
>> On Sunday, May 19, 2019 at 3:26:53 PM UTC+10, donmor3000 wrote:
>>>
>>> Thanks a lot!
>>> BTW I created a pull request to Jermolene/TiddlyWiki5 a few days ago. I 
>>> added an attribute to videoparser.js and audioparser.js to scale videos and 
>>> audios to fit the parent frame.
>>>
>>> 在 2019年5月19日星期日 UTC+8上午9:27:42，TonyM写道：

 donmor3000

 *Thanks for your contribution. I posted in the GitHub issues as anthony 
 in relation to a single wiki app method.*

 *Regards*

 *Tony*
 On Sunday, May 19, 2019 at 4:11:45 AM UTC+10, donmor3000 wrote:
>
> [image: img01.png][image: img02.png]
>
> Finally it is ready to be published...after about two months.
>
>
> Project on GitHub: https://github.com/donmor/Tiddloid
>
>
> Currently you can clone it and build by yourself. For binaries, these 
> links are preserved that will be accessible after the apk is included.
>
> Nightly Build (could be seldom updated, though):
> [image: Get it on F-Droid] 
> (Built by F-Droid)
>
> Release Build (not updating for a long time unless critical bugs 
> reported):
> [image: 酷安] (Built 
> by myself)
>
> Please note that the signature of the apk could differs between the 
> two builds that you have to uninstall the app before changing the build.
>
>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWikiDev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddly...@googlegroups.com.
>> To post to this group, send email to tiddly...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/tiddlywikidev.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywikidev/b81f240f-eb24-4595-b6f4-b70cc422e4f9%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/dba1884a-f14b-47d9-83b2-9dd2bcf242f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Tiddloid - A new android editor is to be released

[donmor3000]

Thanks. I sent the PR minutes ago.
BTW I uploaded an apk to my repository on github so that everyone can get 
it before included into app stores.

在 2019年5月19日星期日 UTC+8下午7:05:53，Jeremy Ruston写道：
>
> Hi Donmor
>
> Congratulations. Do feel free to send a PR to add a new “Resources” 
> tiddler to tiddlywiki.com.
>
> Best wishes
>
> Jeremy.
>
> On 19 May 2019, at 07:50, TonyM > wrote:
>
> donmor3000
>
> Sounds like we are lucky to have you in the community.
>
> Regards
> Tony
>
> On Sunday, May 19, 2019 at 3:26:53 PM UTC+10, donmor3000 wrote:
>>
>> Thanks a lot!
>> BTW I created a pull request to Jermolene/TiddlyWiki5 a few days ago. I 
>> added an attribute to videoparser.js and audioparser.js to scale videos and 
>> audios to fit the parent frame.
>>
>> 在 2019年5月19日星期日 UTC+8上午9:27:42，TonyM写道：
>>>
>>> donmor3000
>>>
>>> *Thanks for your contribution. I posted in the GitHub issues as anthony 
>>> in relation to a single wiki app method.*
>>>
>>> *Regards*
>>>
>>> *Tony*
>>> On Sunday, May 19, 2019 at 4:11:45 AM UTC+10, donmor3000 wrote:

 [image: img01.png][image: img02.png]

 Finally it is ready to be published...after about two months.


 Project on GitHub: https://github.com/donmor/Tiddloid


 Currently you can clone it and build by yourself. For binaries, these 
 links are preserved that will be accessible after the apk is included.

 Nightly Build (could be seldom updated, though):
 [image: Get it on F-Droid] 
 (Built by F-Droid)

 Release Build (not updating for a long time unless critical bugs 
 reported):
 [image: 酷安] (Built by 
 myself)

 Please note that the signature of the apk could differs between the two 
 builds that you have to uninstall the app before changing the build.


> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddly...@googlegroups.com .
> To post to this group, send email to tiddly...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/b81f240f-eb24-4595-b6f4-b70cc422e4f9%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/de0e4626-7dac-4f9b-99ba-4c17e4a9fffe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Warning: Potential Security Risk Ahead - accessing upgrade page

[TonyM]

Jeremy,

Thanks. I would not normally add www to such a link myself, so perhaps it 
is coded somewhere and should be changed.

Just FYI

Regards
Tony

On Sunday, May 19, 2019 at 8:28:55 PM UTC+10, Jeremy Ruston wrote:
>
> Hi Tony
>
> The problem appears when you use www.tiddlywiki.com instead of plain 
> tiddlywiki.com; if you try https://tiddlywiki.com/upgrade.html then 
> things work OK.
>
> I think this is something to do with GitHub Pages hosting; it is supposed 
> to redirect www. to the plain URL, but it seems to only do that properly 
> when accessing the top level URI
>
> Best wishes
>
> Jeremy.
>
> On 19 May 2019, at 08:48, TonyM > wrote:
>
> I detected this in the latest General release of FireFox accessing 
> https://www.tiddlywiki.com/upgrade.html
>
> Firefox detected a potential security threat and did not continue to 
> www.tiddlywiki.com. If you visit this site, attackers could try to steal 
> information like your passwords, emails, or credit card details.
>
> Websites prove their identity via certificates. Firefox does not trust 
> this site because it uses a certificate that is not valid for 
> www.tiddlywiki.com. The certificate is only valid for the following 
> names: www.github.com, *.github.io, *.githubusercontent.com, *.github.com, 
> github.com, github.io, githubusercontent.com Error code: 
> SSL_ERROR_BAD_CERT_DOMAIN
>
> Snapshot of certificate attached
>
> Regards
> Tony
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddly...@googlegroups.com .
> To post to this group, send email to tiddly...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/5156cf8a-fa52-4e55-8d0e-e1082174f28e%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
> 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/86bb6d2e-187a-4bf6-b227-a9618c8f6253%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Adding indexes to the tiddler store

[TonyM]

Jeremy,

One other question of clarification;


>- Will the indexes be saved in tiddlers for the next reload?, perhaps 
>this could be optional allowing indexes to be forced to be regenerated in 
>wikis on reload in cases where there are external/federated wikis, and 
>stored for large indexes on wikis primarily used for search and lookups 
>(with less changes).
>
> No, I don’t think it’s worth it. These are very simple indexes that are 
> pretty fast to build. It’s only if we were doing full text indexing that I 
> think we might want to persistently cache the indexes.
>
>
>- Perhaps an option to store such indexes in local storage and 
>regenerate them if missing would help keep total size down for wikis.
>
>
My interest here is not only or even for performance, it is leveraging the 
indexing process for my own use. For example I have an application I am 
building on tiddlywiki for a client. Each of there 30+ Offices have 1 to 30 
post codes associated with each office. If there were a way to access the 
indexed array and copy it to a tiddler, ie surface the result, it could 
prove useful for various applications.   I know I can build equivalents 
myself but they will be wikitext based and never as efficient as the ones 
in the indexing system you propose. Perhaps providing a widget or variable 
name that can reference the content of the indexed array. Extracting such 
arrays at a point in time would allow new lists to be created with 
additions and deletions for further use. In effect capturing the result in 
an index in a moment in time, useful for database, reporting and dashboard 
applications that can highlight new and deleted items/relationships 
relative to a prior state.

Regards
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/c187f03c-ee3f-47db-a95d-5a72c648c389%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Adding indexes to the tiddler store

[TonyM]

Jeremy,

My bad saying [is[current] vs [all[current] however the english would 
suggest it is the other way around. Ie is is a specific case, all means 
from all get current. 


>- In many cases [is[current] is the first operator in filters 
>especially on view tiddler, should this be included in the application of 
>the tagindexer? 
>
> Yes, as you know it is much less efficient to start with [is[current]] 
> than [all[current]] because the former scans each tiddler to check whether 
> it is the current tiddler, while the second just selects the current 
> tiddler without scanning.
>

It is a subtle difference that most will miss and they must read or never 
know. Perhaps it would make sense to provide an alternate *here[] *operator 
that is equivalent to all[current]. The parameter could also allow 
*here[tiddlername]* or here to override 
currentTiddler. Unlike the all[tiddlername] operation which is bad english 
and does not work.

I think this would make the filters more readable, especially when acting 
on the current tiddler.

So as you say
 

>
> But, we might indeed be able to adapt the indexing mechanism to optimise 
> the is[current] operator, and possibly some of the other variants.
>
>
Perhaps a *here[]* operator could be one of these variants. 

*An aside*
Since the suggested here[] operator by design results in a single title 
perhaps we could explore the use of another operator that handles multiple 
without deduplication for the maths operators. No need to respond, there 
has already being some discussion on this.

*Post Script: *with current and foreshadowed developments in tiddlywiki I 
am looking at making TiddlyWiki a key feature of a business I am starting. 
Perhaps we could start a forum for this and have some hangouts 
(equivalent), becuae there is a lot to discuss, this can inform development 
and help us address open source and licencing issues in advance.

Regards
Tony 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/b9d70937-560c-4a80-b215-871de5c04972%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Progressive Web Apps

[TonyM]

Further to this thread

This article 
https://medium.com/dailyjs/goodbye-electron-hello-desktop-pwas-f316b8f39882
and this google video https://youtu.be/NITk4kXMQDw

Most Browsers are adopting these standards.

The above Explain and promote the idea of PWAs show how if TiddlyWiki can 
embrace this standard it will be easy for people to obtain tiddlywiki 
seamlessly including any edition or instance of a wiki. This gives desktop 
and mobile apps with easy almost invisible install and access to a local 
IndexDB for persistent storage. This would simplify both the distribution 
and savings issues we face with tiddlywiki that offer the greatest 
resistance to adoption. I would expect a new era of app development on top 
of tiddlywiki being democratised. 

Regards
Tony


On Sunday, May 12, 2019 at 12:28:52 AM UTC+10, TonyM wrote:
>
> Ps
>
> There is discussion about being able to ensure persistent local storage to 
> support PWAs and another critical idea is an icon that does not launch 
> another tab in a browser for the same app/site.
>
> Regards
> Tony
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/ffa606ea-4b22-4409-93c0-dfadee86b951%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Adding indexes to the tiddler store

[Jeremy Ruston]

Hi Mario

> Did you test the tag and field dropdown menus in tiddler edit-mode. Any 
> performance points here?

I’ve just done some testing with the tag dropdown on a new tiddler in the 
prerelease; performance improves from 450ms to 350ms — in other words, not a 
great deal. Some quick checks with the browser performance tools suggests that 
most of the rendering time for the tag dropdown is actually spent initialising 
the parser. I’ll have to investigate more.

> I did also post a reply in the github PR. 

Thanks,

Best wishes

Jeremy

> 
> -m
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywikidev+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to tiddlywikidev@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/01f53357-4134-4e5a-af18-d1f3f4a6f7f1%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/9FC680BD-4A67-4E18-AECA-F7CDA9ACF683%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Adding indexes to the tiddler store

[Jeremy Ruston]

Hi Tony

> Will this mechanism be effectively invisible to most users/designers?
Yes. It’s a big change so in due course when the PR is merged we will need 
everyone to pay attention to testing it.

> With the code to support this mechanism in tiddlywiki, could it be also 
> surfaced to provide other indexing methods?
> Such as indexing large data tiddlers, or a subset of tiddlers, tags? A kind 
> of indexedlookup operator?
Yes. The current PR has two indexers for tag and field lookups, but the 
mechanism is extensible so that others can be added.

> In many cases [is[current] is the first operator in filters especially on 
> view tiddler, should this be included in the application of the tagindexer? 
Yes, as you know it is much less efficient to start with [is[current]] than 
[all[current]] because the former scans each tiddler to check whether it is the 
current tiddler, while the second just selects the current tiddler without 
scanning.

But, we might indeed be able to adapt the indexing mechanism to optimise the 
is[current] operator, and possibly some of the other variants.
> Will the indexes be saved in tiddlers for the next reload?, perhaps this 
> could be optional allowing indexes to be forced to be regenerated in wikis on 
> reload in cases where there are external/federated wikis, and stored for 
> large indexes on wikis primarily used for search and lookups (with less 
> changes).
No, I don’t think it’s worth it. These are very simple indexes that are pretty 
fast to build. It’s only if we were doing full text indexing that I think we 
might want to persistently cache the indexes.

> Perhaps an option to store such indexes in local storage and regenerate them 
> if missing would help keep total size down for wikis.
As I say, generating the indexes is pretty fast, even with 60,000 tiddlers. 
It’s only done once, and thereafter it is selectively updated as required.

Best wishes

Jeremy


> Love your work
> Tony
> 
> On Sunday, May 19, 2019 at 3:41:23 AM UTC+10, Jeremy Ruston wrote:
> Apologies for being quiet on the groups over the last week or two. One thing 
> I’ve been working on is exploring performance improvements for large wikis. 
> As part of that work, there’s now a nearly-complete pull request for adding 
> indexes to the tiddler store.
> 
> https://github.com/Jermolene/TiddlyWiki5/pull/3951 
> 
> 
> Currently, the core evaluates a lot of filter expressions like 
> [all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]] to construct 
> the user interface. These filters are slow because the “tag” operator has to 
> iterate through every tiddler in the store to find the tiddlers with that 
> tag. With this PR, the wiki store maintains an index of tiddlers with each 
> tag, updating it every time a tiddler changes. There’s also a fair amount of 
> refactoring to get the filter processing logic using the new indexes.
> 
> The implementation introduces a new type of module called an “indexer”. It 
> has some standard methods: rebuild() for when the entire index must be 
> reconstructed, update(oldTiddler,newTiddler) when a tiddler is modified, 
> created or deleted. There are indexer-specific methods for performing 
> lookups. There is also a new convention whereby tiddler iterators can have 
> additional properties defining “index methods” that perform fast lookups on 
> the tiddlers in the iterator — this is how the filter operators find the 
> indexers that they know about.
> 
> The TagIndexer speeds up the “tag” filter operator when it is used 
> immediately after one of [all[tiddlers]], [all[shadows]], 
> [all[shadows+tiddlers]], [all[tiddlers+shadows]] (note that using the tag 
> operator at the start of a filter run is equivalent to preceding it with 
> [all[tiddlers]]).
> 
> There is also a FieldIndexer which speeds up the “field” and “has” operators, 
> with the same restrictions as to the input selection. The field indexer is 
> reasonably clever, and only constructs indexes for fields for which it has 
> encountered queries.
> 
> On very large wikis (>60,000 tiddlers) I’m seeing startup times reduced by 
> 25% with these optimisations, and refresh time reduced by a factor of three. 
> It will be interesting to get reports from other people working with large or 
> complex wikis.
> 
> Any comments/questions welcome,
> 
> Best wishes
> 
> Jeremy.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywikidev+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to tiddlywikidev@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev 
> .
> To view this discussion on the web visit 
> 

Re: [twdev] Re: Tiddloid - A new android editor is to be released

[Jeremy Ruston]

Hi Donmor

Congratulations. Do feel free to send a PR to add a new “Resources” tiddler to 
tiddlywiki.com.

Best wishes

Jeremy.

> On 19 May 2019, at 07:50, TonyM  wrote:
> 
> donmor3000
> 
> Sounds like we are lucky to have you in the community.
> 
> Regards
> Tony
> 
> On Sunday, May 19, 2019 at 3:26:53 PM UTC+10, donmor3000 wrote:
> Thanks a lot!
> BTW I created a pull request to Jermolene/TiddlyWiki5 a few days ago. I added 
> an attribute to videoparser.js and audioparser.js to scale videos and audios 
> to fit the parent frame.
> 
> 在 2019年5月19日星期日 UTC+8上午9:27:42，TonyM写道：
> donmor3000
> 
> Thanks for your contribution. I posted in the GitHub issues as anthony in 
> relation to a single wiki app method.
> 
> Regards
> Tony
> 
> On Sunday, May 19, 2019 at 4:11:45 AM UTC+10, donmor3000 wrote:
>  <>
> Finally it is ready to be published...after about two months.
> 
> 
> 
> Project on GitHub: https://github.com/donmor/Tiddloid 
> 
> 
> Currently you can clone it and build by yourself. For binaries, these links 
> are preserved that will be accessible after the apk is included.
> 
> Nightly Build (could be seldom updated, though):
>  (Built by F-Droid)
> 
> Release Build (not updating for a long time unless critical bugs reported):
>  (Built by myself)
> 
> Please note that the signature of the apk could differs between the two 
> builds that you have to uninstall the app before changing the build.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywikidev+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to tiddlywikidev@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/b81f240f-eb24-4595-b6f4-b70cc422e4f9%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/F8C7C5A6-D53A-4A26-945B-DE359BAED61D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Warning: Potential Security Risk Ahead - accessing upgrade page

[Jeremy Ruston]

Hi Tony

The problem appears when you use www.tiddlywiki.com 
 instead of plain tiddlywiki.com; if you try 
https://tiddlywiki.com/upgrade.html  then 
things work OK.

I think this is something to do with GitHub Pages hosting; it is supposed to 
redirect www. to the plain URL, but it seems to only do that properly when 
accessing the top level URI

Best wishes

Jeremy.

> On 19 May 2019, at 08:48, TonyM  wrote:
> 
> I detected this in the latest General release of FireFox accessing 
> https://www.tiddlywiki.com/upgrade.html
> 
> Firefox detected a potential security threat and did not continue to 
> www.tiddlywiki.com. If you visit this site, attackers could try to steal 
> information like your passwords, emails, or credit card details.
> 
> Websites prove their identity via certificates. Firefox does not trust this 
> site because it uses a certificate that is not valid for www.tiddlywiki.com. 
> The certificate is only valid for the following names: www.github.com, 
> *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, 
> githubusercontent.com Error code: SSL_ERROR_BAD_CERT_DOMAIN
> 
> Snapshot of certificate attached
> 
> Regards
> Tony
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywikidev+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to tiddlywikidev@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywikidev 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/5156cf8a-fa52-4e55-8d0e-e1082174f28e%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/1E0E7D30-1EDD-4BC9-9D10-7E72227C6FAE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Warning: Potential Security Risk Ahead - accessing upgrade page

[TonyM]

I detected this in the latest General release of FireFox accessing 
https://www.tiddlywiki.com/upgrade.html

Firefox detected a potential security threat and did not continue to 
www.tiddlywiki.com. If you visit this site, attackers could try to steal 
information like your passwords, emails, or credit card details.

Websites prove their identity via certificates. Firefox does not trust this 
site because it uses a certificate that is not valid for 
www.tiddlywiki.com. The certificate is only valid for the following names: 
www.github.com, *.github.io, *.githubusercontent.com, *.github.com, 
github.com, github.io, githubusercontent.com Error code: 
SSL_ERROR_BAD_CERT_DOMAIN

Snapshot of certificate attached

Regards
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/5156cf8a-fa52-4e55-8d0e-e1082174f28e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Tiddloid - A new android editor is to be released

[TonyM]

donmor3000

Sounds like we are lucky to have you in the community.

Regards
Tony

On Sunday, May 19, 2019 at 3:26:53 PM UTC+10, donmor3000 wrote:
>
> Thanks a lot!
> BTW I created a pull request to Jermolene/TiddlyWiki5 a few days ago. I 
> added an attribute to videoparser.js and audioparser.js to scale videos and 
> audios to fit the parent frame.
>
> 在 2019年5月19日星期日 UTC+8上午9:27:42，TonyM写道：
>>
>> donmor3000
>>
>> *Thanks for your contribution. I posted in the GitHub issues as anthony 
>> in relation to a single wiki app method.*
>>
>> *Regards*
>>
>> *Tony*
>> On Sunday, May 19, 2019 at 4:11:45 AM UTC+10, donmor3000 wrote:
>>>
>>> [image: img01.png][image: img02.png]
>>>
>>> Finally it is ready to be published...after about two months.
>>>
>>>
>>> Project on GitHub: https://github.com/donmor/Tiddloid
>>>
>>>
>>> Currently you can clone it and build by yourself. For binaries, these 
>>> links are preserved that will be accessible after the apk is included.
>>>
>>> Nightly Build (could be seldom updated, though):
>>> [image: Get it on F-Droid] 
>>> (Built by F-Droid)
>>>
>>> Release Build (not updating for a long time unless critical bugs 
>>> reported):
>>> [image: 酷安] (Built by 
>>> myself)
>>>
>>> Please note that the signature of the apk could differs between the two 
>>> builds that you have to uninstall the app before changing the build.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/b81f240f-eb24-4595-b6f4-b70cc422e4f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.