Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    sssjjjnnn
    @sssjjjnnn
    I'm out of town for a week, so I can't make it this weekend
    Curt J. Sampson
    @0cjs
    Ah well. I'll have a look at your applicative parser anyway, and try to finish the monadic parser explanation.
    Commit messages on your branch look good, at least. :-)
    sssjjjnnn
    @sssjjjnnn
    Your commit message standards are pretty high but I'm trying :)
    Curt J. Sampson
    @0cjs
    I just keep in mind the audience for the message, and what they really need from it. That would be me, six months later. :-)
    Curt J. Sampson
    @0cjs

    Also, I often find that, when cleaing up a series of WIP ("Work In Progress," for any others who are listening in) commits to ready them for integration to the master branch, the work of writing up a commit message that actually explains things well often finds problems and prompts me to go back and fix them. I guess it's along the same lines as the Readme Driven Development idea. I notice it particularly now because I keep meeting up with situations where someone's done a commit to make some tests pass, with no real explanation.* and when I ask them they don't really know what they did.


    *My favourite commit message from today: "What the heck?" When I asked the guy, he said the tool he was using to comit wouldn't let him use "WTF?" as a commit message because it was too short.

    Curt J. Sampson
    @0cjs
    So, maybe we'd better get back to hacking on the website this weekend, or this coming week?
    sssjjjnnn
    @sssjjjnnn
    I just got back in town. How about tomorrow afternoon?
    Curt J. Sampson
    @0cjs
    Works for me. How does around 15:00 sound?
    Curt J. Sampson
    @0cjs
    I also notice that [TGIFreeCodeCamp[ https://www.meetup.com/Thank-God-Its-FreeCodeCamp-Friday/] is opening their room in Akihabara 10:00-18:00 Mon-Thu this week for free "self-study." I guess what we do pretty nearly qualifies, so this might make it more convenient (or less inconvenient :-)) for @yaseppochi to come in, if he wanted to....
    sssjjjnnn
    @sssjjjnnn
    That works for me
    Curt J. Sampson
    @0cjs
    Right-o. See you at Lodge tomorrow at 15:00.
    Curt J. Sampson
    @0cjs
    Hey dude. Hate to break our appointment, but I've come down with something and am feeling pretty ill and have to bail on today. Maybe later this week?
    sssjjjnnn
    @sssjjjnnn
    Ok, no problem. BTW,
    Lodge is closed for golden week
    Curt J. Sampson
    @0cjs
    Oh! Well, that would have gone badly anyway.
    Curt J. Sampson
    @0cjs
    Oh my! Seems I'm the only one here at Co-edo?
    Curt J. Sampson
    @0cjs
    Ok, the new branch with what's approaching the final version of the wiki content generation code is dev/cjs/190511/wiki.
    Curt J. Sampson
    @0cjs
    For those keeping up remotely, the master branch now has separate --prod-release and --dev-release options so you can test your branch on your Netlify account, and we now have four sample wiki pages being served properly under the exact same /wiki/... URLs as the current site uses, though we don't have links to pages with : in the working (probably a fairly easy fix) or transcludes working (a more difficult fix, but in progress). The dev/ejdm/wiki-files has the work we've started on a template for the Wiki pages. (Currently they display as very, very boring HTML with basically no markup.)
    Curt J. Sampson
    @0cjs
    Ok, I've just pushed up doc/hosting.md on master branch describing the new hosting configuration and listing a few things we have to change. One is "Configure new.tlug.jp as a CNAME to tlug-jp.netlify.com." @E14n_twitter, can we get that done in the near future? Or can anybody else do it?
    Curt J. Sampson
    @0cjs

    @E14n_twitter Can you have a look at my changes on dev/cjs/190512/wiki-ns-link-fix? (These can currently be seen on https://cjs-tlug.netlify.com/.) There are two changes:

    1. Fix the broken links to namespaced pages. You don't need to worry about the actual Haskell code itself (unless you want to), just check that you think the solution I picked (prefix things we know are namespace URLs with /wiki/) is correct.
    2. Redirect /wiki and /wiki/ to the main page, as MediaWiki does.
      If this looks good to you, I'll put these commits on master and you can rebase your branch on to that at your convenience.

    Comments from anybody else are welcome as well, of course.

    Curt J. Sampson
    @0cjs
    Hm. https://lists.tlug.jp is not small. 605 MB and 72K files and still downloading....
    Edward Middleton
    @E14n_twitter
    @0cjs I have found the issues with pages showing up as code when loaded from cache. netlify is sending two content type headers, one with the original content type and one with the html type. It appears the cache is only storing the text type.
    Curt J. Sampson
    @0cjs
    Ooof! That's not good.
    Feel like putting in a support request and asking them about this? Sounds like a bug in their system; I'm pretty sure sending two Content-type headers is a violation of the standard (because Content-type is not a list of values).
    Curt J. Sampson
    @0cjs
    Two other things that might be worth trying, just in case it's silly code bugs:
    1. Change the capital-C to a small-c in our [headers.values] section.
    2. Try moving that config to a _headers file.
    And, probably a pretty hacky workaround, but I wonder if setting a META content-type or whatever it is in the HTML <HEAD> would help convince Firefox to do what we desire.
    Edward Middleton
    @E14n_twitter
    @0cjs I changed the T for type to upper case and that fixed the issue.
    Curt J. Sampson
    @0cjs
    Wow! Well, cool!
    It would be a good idea to squash those two test commits and make sure the commit message documents exactly what's going on there.
    Did the all-lower-case version still have the issue?
    Edward Middleton
    @E14n_twitter
    I don't know, I was looking at the wrong site when I checked ;)
    Curt J. Sampson
    @0cjs
    Ah. Oh! I know what we should do: update our netlify-test site to have subdirs that do all three versions, so that we can demo it.
    I'm throwing together something right now.
    Curt J. Sampson
    @0cjs
    On what URL is netlify-test.git being served?
    Edward Middleton
    @E14n_twitter
    Curt J. Sampson
    @0cjs
    Not so easy to remember. :-) I've created a site in the TLUG Netlify account and put it on https://tlug-netlify-test.netlify.com, serving master, and documented this in the README.
    Curt J. Sampson
    @0cjs
    Ok, bug demonstrated and described in netlify-test. If you want to have a look and let me know if that all looks ok, that would be great. I'm going to report the bug.
    Curt J. Sampson
    @0cjs
    Ok, it's filed. Thanks for doing the hard work on figuring out the problem and solution!
    Curt J. Sampson
    @0cjs
    I've also just created https://github.com/tlug/lists.tlug.jp-scrape and pushed up a scrape of the current contents of https://lists.tlug.jp.
    Henri "Ragga" Servomaa
    @ragga
    Hi all.
    Curt J. Sampson
    @0cjs
    Hey, you made it here! Good to see you.
    Curt J. Sampson
    @0cjs
    So, while I have no opinion about how the mailing lists should be hosted (though I am willing to throw in a few bucks to help cover hosting charges if we decide to go with paid hosting of some sort), I am happy to help out with whatever we need to do to host the website with the list archives.
    One option (I don't know how good it is) is to simply serve the current scrape as a Netlify site, either as the "legacy" archive with another site serving an archive of messages from after that change or continuing on as the main archive with new messages being added to it. (I can help program the means to do that.)
    It would help if someone here could explain how the current archiving system is working. I know it's using MHonArc, but I don't know any more than that.
    Henri "Ragga" Servomaa
    @ragga
    Well, I think there are 3 components to the mailing lists
    1. ability to send and receive via SMTP
    2. list management: (un)subscribe, recipient list, distribution trigger etc
    3. archives
      My feeling is that we need to tackle #2 first. That will determine how to do the archiving going forward. Also, I'm strongly in favor of keeping everything under the tlug.jp domain, so I guess that means either paying for it or hosting ourselves.
    Curt J. Sampson
    @0cjs
    Yes, I agree how we do (3) will depend somewhat on how we do (2). Still, knowing how the current system works would be useful background for me.
    Curt J. Sampson
    @0cjs

    @E14n_twitter Can you have a look at my changes on dev/cjs/190512/wiki-ns-link-fix...

    1. Fix the broken links to namespaced pages....
    2. Redirect /wiki and /wiki/ to the main page, as MediaWiki does.

    Apparently nobody has any comments on this, so I've just put this change on master. You can now see it on https://new.tlug.jp.

    Henri "Ragga" Servomaa
    @ragga
    new.tlug.jp looks fine to me. I assume all the public wiki contents has been scraped as well. Some pages, like "next event", will have to be removed or handled differently, I guess.
    Curt J. Sampson
    @0cjs
    The content, public and private, has all been pulled from the server; it's wiki markup, not scrapes. (Though I think we have some content as scrapes as well.) It's in the akari.tlug.jp repo; send me a PM if you think you should have access to it.
    Very little of that content has been copied over to the tlug.jp repo.
    Oh, and it occurs to me, to help avoid confusion, that repo should be renamed to www.tlug.jp unless we're going to merge lists.tlug.jp into it (which off-hand doesn't strike me as a good idea).
    Curt J. Sampson
    @0cjs
    Anybody up for a hacking meetup this weekend? At Lodge, Co-edo, or just a Starbucks somewhere?