Mat and Mohammad:
Love the ideas! My main concern right now is supporting more conversations 
(only converts 30 as of right now), or allowing the user to select the 
number they would like to convert. Auto-formatting might be difficult, 
since everything is stored in JSON. However, I am wondering if TW will 
automatically format them if the symbols are replaced by valid TW syntax. 

Mat, I'm a bit confused as to what you mean by "thread title." Do you mean 
the titles it is automatically giving already, or something else?

Tags will be easy, and I had planned on adding them, as well as authors. 
These can be made with new fields in the JSON!

Lastly, storing these files could prove difficult. One such way would be to 
create a program on an unused computer, and having it run the GG2TW program 
at a certain interval and stimulate a download of the data, where another 
way (more difficult), would listen to the GG conversation and run only when 
30 new posts were added. This idea is worthy of its own repo!

Thanks!
     Finn Lancaster 

BTW, there is already a GitHub conversation going on in the TW5 
discussions. A link to it 
is: https://github.com/Jermolene/TiddlyWiki5/discussions/5793

On Tuesday, June 15, 2021 at 8:17:21 AM UTC-4 Mohammad wrote:

> Great job! Really useful!
>
> I am thinking how we can automatically convert code sections into code 
> blocks and tagify posts?
>
>
> Keep going on!
>
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Jun 15, 2021 at 5:30 AM Finn Lancaster <[email protected]> wrote:
>
>> Fixed the illegible text issue! I added a few replace() and got rid of 
>> the method to escape I was using. Just tested the TW import, and works 
>> perfectly! Of course, this could all change if there happens to be a 
>> character that the program doesn't escape somewhere in the GG. However, I 
>> deem this rare, as I don't think there are any chars that I've forgot. Keep 
>> me informed of any issues; I intend to make the UI better soon. 
>>
>> P.S.: I have encountered a crash in Chrome upon running the program. If 
>> anyone else has the issue, it is the program. So far, however, I'm thinking 
>> it's just my PC, as Chrome doesn't seem to like my outdated Linux version :)
>>
>> On Sunday, June 13, 2021 at 9:50:36 PM UTC-4 Finn Lancaster wrote:
>>
>>> Yes. The 90 into 28 is taking into account responses to the 
>>> conversations, which will lower the count. GG just likes to make things 
>>> difficult, so it split them all up. Since the loading thing was not planned 
>>> for at first, I just connected it to my counter variable that is added to 
>>> after every successful request, hence the 90. In the code, there is an if 
>>> statement with a comment "code goes here." In the future, this part will 
>>> deal with the repeats.
>>>
>>> On Sunday, June 13, 2021 at 8:59:51 PM UTC-4 [email protected] wrote:
>>>
>>>> Random chars as you also found. But that was not the only thing. 90 of 
>>>> 90 conversations ended up in 28 imported tiddlers. 
>>>>
>>>> The good news is that it kind of worked - as I am using a low end 12 
>>>> year old laptop with 8 gb ram.
>>>>
>>>> Birthe
>>>> On Monday, June 14, 2021 at 2:39:23 AM UTC+2 [email protected] wrote:
>>>>
>>>>> Huh. Mine always glitches-out before TW successfully imports, so I've 
>>>>> never seen the actual output in TW. I'd always assumed it would have no 
>>>>> issues, since I've run the code through various JSON-checking sites, and 
>>>>> it 
>>>>> has been labeled valid. Were the words legible with just random chars in 
>>>>> between, or was it just a jumble?
>>>>>
>>>>> On Sunday, June 13, 2021 at 7:36:17 PM UTC-4 [email protected] 
>>>>> wrote:
>>>>>
>>>>>> I did get 90/90 conversations - it really did not take that long.I 
>>>>>> exported the json and tried to drag and drop it into my tiddlywiki. It 
>>>>>> worked - but totally unreadable.
>>>>>>
>>>>>> Still it is exciting news. What a good idea you had.
>>>>>>
>>>>>> Birthe
>>>>>> On Sunday, June 13, 2021 at 10:37:35 PM UTC+2 [email protected] 
>>>>>> wrote:
>>>>>>
>>>>>>> Strange, it works for me. I added a loading message telling of how 
>>>>>>> many conversations were successfully loaded. If it stays at 0/90, then 
>>>>>>> it 
>>>>>>> is truly an issue. Possibly it was just taking a long time (takes 
>>>>>>> around a 
>>>>>>> minute generally to fully finish, I find.) Let me know if it helps you! 
>>>>>>>
>>>>>>> *Another idea could be to clear history, cookies, etc. for all time, 
>>>>>>> and try again. If this works, it is an issue with the CORS proxy API I 
>>>>>>> am 
>>>>>>> using. *
>>>>>>>
>>>>>>> To address Mat, yes, it does scrape the GG FIRST page (1-90 
>>>>>>> conversations, but some repeats). The output is an array of valid JSON 
>>>>>>> data, which is recognized by TW as JSON tiddlers, and TW will then 
>>>>>>> import 
>>>>>>> them (drag and drop works best).
>>>>>>>
>>>>>>> On Sunday, June 13, 2021 at 1:42:35 PM UTC-4 TiddlyTweeter wrote:
>>>>>>>
>>>>>>>> Ciao flanc...
>>>>>>>>
>>>>>>>> The idea sounds neat! Unfortunately nothing happens for me :-(. I 
>>>>>>>> get this but no results appear on click ... :-( ...
>>>>>>>>
>>>>>>>>
>>>>>>>> [image: Screenshot 2021-06-13 194045.jpg]
>>>>>>>>
>>>>>>>> Best wishes
>>>>>>>> TT
>>>>>>>>
>>>>>>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/41327824-83f2-4785-a226-92611c784ba7n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/41327824-83f2-4785-a226-92611c784ba7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fec6f5d0-7d3b-432f-9581-131f4df4e7bcn%40googlegroups.com.

Reply via email to