[GitHub] [incubator-ponymail] Humbedooh commented on issue #468: Working on *just* the UX?
Humbedooh commented on issue #468: Working on *just* the UX? URL: https://github.com/apache/incubator-ponymail/issues/468#issuecomment-486783210 I agree, and there is some work in progress on porting it all to python, with an OpenAPI specification instead, but work is progressing very slowly on that front. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] BigBlueHat commented on issue #468: Working on *just* the UX?
BigBlueHat commented on issue #468: Working on *just* the UX? URL: https://github.com/apache/incubator-ponymail/issues/468#issuecomment-486780226 @Humbedooh actually, thanks to [this infra ticket](https://issues.apache.org/jira/browse/INFRA-15587), I probably have what I need from the CORS side of things (at least for this running instance). The next step (using option A above) would be build a simple/alternate UX that uses that API and is built as a "standalone" web app (which could run on a different server/host, but still serve the same data). The goal was to make UX iteration simpler/faster by separating it from server-side concerns using the API as the "glue" between them. 😃 So, I suppose this is partly possible already, and would just need a 👍 and a more "visible" (via API docs or similar) API. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] sebbASF commented on issue #486: Enh: store message arrival time for use in sorting
sebbASF commented on issue #486: Enh: store message arrival time for use in sorting URL: https://github.com/apache/incubator-ponymail/issues/486#issuecomment-486746164 I don't think the discrepancy needs to be displayed. Just sorting by arrival time would help to show which messages have arrived recently. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #469: Bug: Javascript URLs must always use URL_BASE
Humbedooh commented on issue #469: Bug: Javascript URLs must always use URL_BASE URL: https://github.com/apache/incubator-ponymail/issues/469#issuecomment-486744992 sorry, wrong PR number in that commit. it is for #465 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] sebbASF commented on issue #471: Flagging Active and Inactive Mailing Lists
sebbASF commented on issue #471: Flagging Active and Inactive Mailing Lists URL: https://github.com/apache/incubator-ponymail/issues/471#issuecomment-486742980 I agree that list activity cannot be used to determine whether a list is still active or not. Some lists have very little activity, and a list with recent activity may have been closed down. There may be other reasons for disallowing posting, e.g. for list archives that are aliases. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #468: Working on *just* the UX?
Humbedooh commented on issue #468: Working on *just* the UX? URL: https://github.com/apache/incubator-ponymail/issues/468#issuecomment-486739449 You can use remote API calls, if CORS allows. I would suggest setting up a proxy at home that tweaks CORS to allow for credentials if needed, I don't think it's gonna happen on lists.a.o :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #471: Flagging Active and Inactive Mailing Lists
Humbedooh commented on issue #471: Flagging Active and Inactive Mailing Lists URL: https://github.com/apache/incubator-ponymail/issues/471#issuecomment-486736853 There isn't really a way for PM to know if a list is active or inactive other than whether it is getting emails. We *could* have some sort of tests for activity and suggest that a list *may* be inactive if below a certain threshold, but doing more than that would require either manual intervention (perhaps a CLI script to mark lists?) or tying it into the mailing list service itself. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] sebbASF commented on issue #487: Bug: drop 'archived-at' header generation
sebbASF commented on issue #487: Bug: drop 'archived-at' header generation URL: https://github.com/apache/incubator-ponymail/issues/487#issuecomment-486736028 No, I think Ponymail should not change the emails that it stores. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #474: Bug: plain text mails lose spacing and alignment
Humbedooh commented on issue #474: Bug: plain text mails lose spacing and alignment URL: https://github.com/apache/incubator-ponymail/issues/474#issuecomment-486736043 Pony Mail uses the Hack monospace font, which should take spacing into account. Can you share an email where this causes issues? Is it a width issue? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #476: Issues with display of binary data in mails
Humbedooh commented on issue #476: Issues with display of binary data in mails URL: https://github.com/apache/incubator-ponymail/issues/476#issuecomment-486735605 Has this issue been addressed sufficiently? :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #480: Add support for Twitter Cards and Open Grapf metadata
Humbedooh commented on issue #480: Add support for Twitter Cards and Open Grapf metadata URL: https://github.com/apache/incubator-ponymail/issues/480#issuecomment-486735398 I think we can, currently, display a generic card and metadata, but not specific to the email, as that is JS powered - I am not sure how the twitter/ogp handlers would parse that. Going forward, we could move towards a scripted page instead of a static html, for handling threads, I guess? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #486: Enh: store message arrival time for use in sorting
Humbedooh commented on issue #486: Enh: store message arrival time for use in sorting URL: https://github.com/apache/incubator-ponymail/issues/486#issuecomment-486734759 that is typically what archived-at is for, with most MTAs (postfix et al) storing that as the email gets punted to the archiver. While I am in favor of keeping a separate record of this, I wonder how we would display the discrepancy in the UI? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #487: Bug: drop 'archived-at' header generation
Humbedooh commented on issue #487: Bug: drop 'archived-at' header generation URL: https://github.com/apache/incubator-ponymail/issues/487#issuecomment-486733807 Would it make more sense to prefix it with 'X-' (thus X-Archived-At) and have Pony Mail disregard X-* when digesting the email, going forward? I think this could solve some other theoretical inconsistencies in emails depending on the path they took. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] Humbedooh commented on issue #489: Errors with Elasticsearch 5.x
Humbedooh commented on issue #489: Errors with Elasticsearch 5.x URL: https://github.com/apache/incubator-ponymail/issues/489#issuecomment-486712204 I've added the scan_and_scroll type (while keeping the original scan as it was), and revamped edit-lists.py by spliting the process into distinct functions. @ilgrosso can you please test that this works on your system? It works on mine, but I was only testing with a handful of emails. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-ponymail] sebbASF commented on issue #489: Errors with Elasticsearch 5.x
sebbASF commented on issue #489: Errors with Elasticsearch 5.x URL: https://github.com/apache/incubator-ponymail/issues/489#issuecomment-486588658 Good idea to create an iterator. As with any API change, I think it would be better to change the method name. This makes it easier to update the callers (and more obvious when all callers has been found/fixed), and means it is possible to directly test the new behaviour against the old. It's also kinder to 3rd parties who may have written their own scripts using elastic.py. We should deprecate the existing method in favour of the new one. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
