Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation
@MarkGraham, @InternetArchive had previously collaborated with WP Broken Link Checker https:/
Is there someone there who could nudge this suggestion which could increase submissions? #DtMH2017
https:/
@jimmymansaray I'm sure it's not an Independent Publisher issue. You might also ask Colin where he got it and if it had actually worked for him. I think I saw that snippet floating around last week. I think Colin has ultimately changed to the following instead: https:/
It adds the kind of date/time stamp you're looking for (or is modifiable with some research) and has the added benefit that micro.blog should ignore the time stamp and just import the_content() of your status update instead.
Honestly, I'd recommend going without a title if you can manage it. If you need something in your admin UI, you might try this suggestion as well: http:/
I notice that https:/
@swissmiss Delving into @adactio's suggestion a bit deeper, here's a whole list: http:/
Mobile UI suggestion: Chat bubble or menu option to create post from home screen · Issue #24 · microdotblog/issues https:/
The Timeline, Mentions, and Favorites all have a "chat" icon in the upper right to allow one to create a status update. Why not also include this on the main homescreen (or a "Create Post" button just above Timeline) so there's one less step to posting? It also makes it easier for new users to figure out how to post.
UX/UI Suggestion: Meta box in the admin UI with PressForward metadata and comments · Issue #902 · PressForward/pressforward https:/
I'd suggest that it would be worthwhile and convenient to have a meta box in the admin UI for editing the final draft that contained all of the pre-existing PressForward metadata.
Bits and pieces of it appear in other portions of the PressForward UI throughout the vetting (reading, nominating) process (typically hidden under the "info" button which pops up the details), but having portions of it while actually editing the draft of the post would be very handy/useful. In particular, it would be nice to have access to the comments which are added to the particular piece in the earlier parts of the process.
, and it was driving me bonkers still.
Ultimately I dug back through some records and tried using
`<link rel="feed" type="text/html" title="BoffoSocko Blog feed" href="http://boffosocko.com/blog/" />`
which I had some months ago. Things now seem to be back on track. Apparently (??) it was using `href `and not `src `which may have been the more recent issue if you need to make the suggestion in the future.
I still think it's kind of odd that the issue was only with Instagram and didn't seem to affect Twitter or Facebook.
Thanks again for helping to save my sanity!
Link to see nomination/draft from Bookmarklet finish screen · Issue #881 · PressForward/pressforward https:/
UI suggestion
When using the bookmarklet to nominate/draft an article or source, it would be nice if the final page of the process in the modal would/could include direct links to open the interface to see the nomination, the draft, or the page for the RSS nominations respectively depending on the action taken.
In small(er) organizations this could help cut down on several seconds of workflow for those who might then begin work on the next step in the process immediately.
. This way one can cut and paste the log, clear it out for the next session/day/other while not needing to re-enter all the speaker data back into the system redundantly - particularly when one may need to look up all the data again.
While the Twitter look-up is useful as a stopgap toward re-populating , the data return doesn't always do the best job as some Twitter bios don't use full names and may or may not include websites, or when users (Tantek for example) have an emoji as their "name" Noterlive doesn't allow modifying (and re-saving) corrected versions of the name (though the workaround for this appears to be to save the speaker, delete the the speaker, modify the text and then resave.)
Mostly these type of fit & finish ideas are meant to serve livetweeters who don't necessarily have lists/data on speakers pre-entered prior to an event and are forced to do the searching on-the-fly during which they are missing potential content.
UI suggestion: Synopsis labeled in parallel with other data · Issue #24 · donnapep/book-review https:/
Given the way the standard data in "book info" (except the star rating) is scrapped based on ISBN, it would be nice if the word "Synopsis" appeared in bold in front of the synopsis to provide a similar parallelism between it and the book title, author, etc.
This tweak to the UI would help to indicate a more parallel structure for the base book data and help to separate it from the user's actual review. Without it, some readers of reviews may mistakenly assume the reviewer wrote the text rather than it more likely being scraped from the publisher's description.
Similarly it might make better UI to have the star rating separated from the rest or possibly preceded by "My rating" (in bold) to indicate it as separate from the rest of the bulk data as well? Perhaps adding fields for other User specific data like "date started" and "date completed" would aid in this separation from basic book data and user generated data.
Feature suggestion: Site Owner push notifications · Issue #1 · pushpad/pushpad-wordpress https:/
WordPress.com announced push notifications for site owners regarding likes/comments yesterday: https:/
Given the infrastructure you've got, it would be cool to have this as an engagement option too... I don't think many of the current push plugins have this type of functionality, so this could be a nice differentiator.
UI suggestion: Sort M/F or F/M · Issue #11 · lynnandtonic/hollywood-age-gap https:/
Given the prevalence of older men with younger women and the fact that currently the largest gap is actually a MUCH older woman and a younger man, it would be interesting if the sort could be done on a gender basis with the +# indicating one direction and a -# indicating the reverse. This way one could more easily emphasize the larger M/F gap and the way in which it skews. It would also more easily highlight the far fewer cases in which women exceed men in age.
UX Suggestion · Issue #3 · kshaffer/hypothesis_aggregator https:/
Towards the end of using this plugin as part of an online "notebook" or commonplace book, it would be nice to have finer control over the listings of the annotations.
As an example, look at: http:/
The original post was a "bookmark" to an article which was then annotated, solely by me. When embedding the annotations (in this case the shortcode included one author and one specific tag), it becomes overly redundant to repeatedly include that the annotations were by me, that they're from the same article, and including the picture multiple times. As this is likely a frequent use case for such a plug in, perhaps when the same annotator is repeated all the annotations could come under one heading and similarly if it's the same article, those could be concatenated along with just one photo as well.
Suggested output:
TITLE OF PAGE1 | #
PHOTO from PAGE1
Annotations by AUTHOR1:
- annotation 1 from PAGE1
- highlight 2 from PAGE1
- highlight 3 from PAGE1
- annotation to go with highlight 3 from PAGE1
TITLE OF PAGE2 | #
PHOTO from PAGE2
Annotations by AUTHOR1:
- annotation 1 from PAGE2
Annotations by AUTHOR2:
- annotation 2 from PAGE2
- annotation 3 from PAGE2
This type of logic isn't too difficult given the current configuration though it may require some thought for the pending changes to add and/or functionality for multiple authors and multiple tags.
One particular hurdle may be cases where the order of annotations could potentially tell a "story" and even more so when there are multiple authors providing multiple annotations (for example when using this in a classroom setting versus a single-author notebook.)
Providing a visual indicator like # which includes a wrapped permalink URL for the particular article could allow the user to also quickly jump to that page and see the broader flow of annotations on a single page, especially in a classroom type setting where dozens of students may have made hundreds of annotations which may provide a slightly better contextual UI experience, while still allowing the (shortcoded) web page to include all of the annotations for historical purposes.
Potential future features · Issue #2 · kshaffer/hypothesis_aggregator https:/
This plugin is spectacular by the way... Here are some thoughts on future development:
It would be great if the displayed text output from the shortcode included a permalink to the original annotation on Hypothesis. As a UI suggestion, perhaps you could place it after the title of the annotated page thusly:
URL WRAPPED TITLE | < a href="permalinkhere">#</a>
Being able to circumscribe dates for displayed annotations could be useful, particularly in cases where one wants to highlight only a handful of annotations from a particular user with a particular tag but specific ones within certain time parameters. Additionally pages with embeds could, over time, require importing huge numbers of annotations which may not be ideal, or the context may change with significant future annotations that aren't relevant to what could be a static post that's trying to highlight just a few particular annotations. Time parameters could also prevent future possible spam on unwatched embeds with only "tag" parameters that could be targeted by bad actors.
I owe you a recommendation (or more) for your suggestion that I read Joanne Harris's Gentlemen & Players a while back. In roughly the same genre, you might take a look at The Rule of Four (http:/
Hope all is well!