Revision history [back]
 | 1 | initial version | posted 2015-02-07 23:57:56 +0200  |
What extra value can about: pages add to the user experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they are not recognised as links in the Jolla browser in webpages, e.g. <a href="about:about">about:about</a>. Will this condition change for the browser?
The following about pages may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers who elect to routinely and automatically upload their browser statistics to the developers.
about:me, about:you, `about:nemo```````
| | 2 | No.2 Revision |
What extra value can about: pages add to the user experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they are not recognised as links in the Jolla browser in webpages, e.g. <a href="about:about">about:about</a>. Will this condition change for the browser?
The following about pages may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers who elect to routinely and automatically upload their browser statistics to the developers.
developers: about:me, about:you, `about:nemo```````about:nemo, about:us, about:jolla, standards, about:bash-command, about:anonymous-statistics.
| | 3 | No.3 Revision |
What extra value can about: pages add to the user browser experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they are not recognised as links in the Jolla browser in webpages, e.g. <a href="about:about">about:about</a>. Will this condition change for the browser?
The following about may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers who elect to routinely and automatically upload their browser statistics to the developers: about:me, about:you, about:nemo, about:us, about:jolla, standards, about:bash-command, about:anonymous-statistics.
| | 4 | No.4 Revision |
What extra value can about: pages add to the browser experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they are not recognised fail as links in the Jolla browser in webpages, e.g. <a . Will this condition change for the browser?href="about:about">about:about</a>href="about:about">about</a>
The following about s may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers who elect to routinely and automatically upload their browser statistics to the developers: about:me, about:you, about:nemo, about:us, about:jolla, standards, about:bash-command, about:anonymous-statistics, about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 5 | No.5 Revision |
What extra value can about: pages add to the browser experience?
About about pages in the browser:
- browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this condition change for the browser?
The following abouts may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers who elect to routinely and automatically upload their browser statistics to the developers: about:me, about:you, about:nemo, about:us, about:jolla, standards, about:bash-command, about:anonymous-statistics, about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 6 | No.6 Revision |
What extra value can about: pages add to the browser experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this condition change for the browser?
The following abouts may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers who elect to routinely and automatically upload their browser statistics to the developers:
about:me,about:you,about:nemo,about:us,,about:jolla,standards,,about:bash-command,about:anonymous-statistics,about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 7 | No.7 Revision |
What extra value can about: pages add to the browser experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this condition change for the browser?
The following abouts may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-user customers end-users who elect to routinely and automatically upload their browser statistics to the developers:
about:me,about:you,about:nemo,about:us,about:jolla,standards,about:bash-command,about:anonymous-statistics,about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 8 | No.8 Revision |
What extra value can about: pages add to the browser experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this condition change for the browser?
The following abouts pages/modules may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:me,about:you,about:nemo,about:us,about:jolla,standards,about:bash-command,about:anonymous-statistics,about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 9 | No.9 Revision |
What extra value can about: pages add to the browser experience?
About about pages in the browser:
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this condition change for the browser?
The following about pages/modules may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:d3js about:revealjs about:reactjs
about:me,about:you,about:nemo,about:us,about:jolla,standards,about:bash-command,about:anonymous-statistics,about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 10 | No.10 Revision |
What extra value can about: pages add to the browser experience?
About On about pages in the browser:browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
- https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this condition change at some point? Some about info modules may be worth including, aiming for the browser?
The following about pages/modules may be worth implementing, with the objectives of a better, marginally-but-usefully improved browsing better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:d3js about:revealjs
- about:d3js
- about:revealjs
about:me, about:you, about:nemo, about:us,about:jolla, standards,about:bash-command, about:anonymous-statistics, about:workflows.Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 11 | No.11 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguideabout:d3jsabout:revealjsabout:reactjs- about:together
about:me,about:you,about:nemo,about:us,about:jolla,standards,about:bash-command,about:anonymous-statistics,about:workflows.
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 12 | No.12 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguideabout:d3jsabout:revealjsabout:reactjsabout:meabout:youabout:nemoabout:usabout:jollastandards,about:standards about:otherness about:bash-commandabout:anonymous-statisticsabout:workflowsabout:xdg-open Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 13 | No.13 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:togetherabout:(together)[https://together.jolla.com]about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 14 | No.14 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:(together)[https://together.jolla.com]about:[together](https://together.jolla.com/)about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 15 | No.15 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:[together](https://together.jolla.com/) about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 16 | No.16 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
'''about:dbus-userguide''' about:dbus-userguide about:d3js about:revealjs about:reactjs '''about:about:together''' about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 17 | No.17 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:about:me about:you about:us about:jolla about:standards about:otherness about:bash *-command about:anonymous-statistics* about:workflows about:xdg-openabout:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 18 | No.18 Revision |
What extra value can about: pages add to the browser experience?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:together about:me about:you about:nemoabout:nemo about:us about:jolla about:standards about:otherness about:bash *-command about:bash-command about:anonymous-statistics* about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 19 | No.19 Revision |
What extra added value can do about: pages add to the browser experience?provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 20 | retagged |
What added value do about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:revealjs about:reactjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 21 | No.21 Revision |
What added value do about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:reactjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 22 | No.22 Revision |
What added value do about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:reactjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 23 | No.23 Revision |
What added value do about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:codingout:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:reactjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 24 | No.24 Revision |
What added value do about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:codingout: about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 25 | No.25 Revision |
What added value do about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 26 | No.26 Revision |
What added value do can about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 27 | No.27 Revision |
What added value can about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail as links in the browser in webpages, e.g. <a href="about:about">about</a>. Will this change at some point? Some about info modules may be worth including, aiming for a better user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
developers:
about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 28 | No.28 Revision |
What added value can about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Currently, they fail Fail as links hrefattributes in the HTML on Jolla browser in webpages, e.g. (<a href="about:about">about</a>. Will ), will this change at some point? Some change? The tech behind about info modules may be worth including, aiming for a better is underused to improve the user experience and potentially a tighter feedback loop between Jolla and its end-users who elect to automatically upload browser statistics to the developers:
about:regular-expressions experience.
about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 29 | No.29 Revision |
What added value can about: pages provide?
On about pages in the browser: https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Fail Failing as hrefattributes in HTML on Jolla browser (browser, <a href="about:about">about</a>), , will this change? The tech behind about is underused to improve the user experience.
about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 30 | No.30 Revision |
What added value can about: pages provide?
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech behind about is underused to where it could significantly improve the user experience.experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways, that my future input can be better more, useful and more immediately clear and actionable.
about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 31 | No.31 Revision |
What added value can about: pages provide?
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech behind for about is underused where it and could significantly improve the user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways, that my future input can be better more, useful and more immediately ways so futurework is clear and actionable.
actionable.
about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 32 | No.32 Revision |
What added value can about: pages provide?
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so futurework future work is clear and actionable.
about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 33 | No.33 Revision |
What added value can about: pages provide?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices, or comment, answer or downvote )
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 34 | No.34 Revision |
What added value can about: pages provide?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. users. (Please upvote for a better help system on Jolla devices, or comment, answer or downvote )downvote.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
| | 35 | No.35 Revision |
What added value can about: pages provide?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices, or comment, answer or downvote.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:bookmarks about:templates about:shell >> <<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
| | 36 | No.36 Revision |
What added value can about: pages provide?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices, or comment, answer or downvote.)devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:bookmarks about:templates about:shell >> <<<shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
| | 37 | No.37 Revision |
What added value can about: pages provide?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 38 | No.38 Revision |
What added value can about: pages provide?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content about:this#named_content to hook into local (downloaded) info pages.
| | 39 | No.39 Revision |
What added value can How about: pages provide?add value?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 40 | No.40 Revision |
How can about: pages add value?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 41 | No.41 Revision |
How can about: pages add value?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
about:clock about:calendar about:calculator about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 42 | No.42 Revision |
How can about: pages add value?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
Imagine about pages with embedded videos, audio, or text-to-speech configuration and implementation.
about:recorded-phonemes about:clock about:calendar about:calculator about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 43 | No.43 Revision |
How can about: pages add value?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
Imagine about pages with embedded videos, audio, or text-to-speech configuration and implementation.
about:recorded-phonemes about:clock about:calendar about:calculator about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations* about:clipboard** text-operations about:clipboard about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or pushd, popd and dirs, but for net links, not just directories, to give context and greater utility to the browser. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 44 | No.44 Revision |
How can about: pages add value?
tldr; The undertapped about: browser address prefix is good to provide help and info to users. (Please upvote for a better help system on Jolla devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
Imagine about pages with embedded videos, audio, or text-to-speech configuration and implementation.
about:app[lications] about:recorded-phonemes about:clock about:calendar about:calculator about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations about:clipboard about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like a bookmark list-style link group, or grouped bookmarks with manipulation semblant of pushd, popd and dirs, but for net links, not just directories, to give and program links and their descriptions (not only directories). This may make browser context and greater utility to the browser. have more relevance in different activities' phases. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s).example(s). Test a terminal-based version to define steps and allow alternative or fallback capability.
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.
| | 45 | No.45 Revision |
How can about: pages add value?
tldr; The undertapped about:* browser about:you are useful, because you're here.
Browser address prefix about: is good to provide help and info to users. (Please upvote users.** (upvote for a better help system and info on Jolla Jolla's Sailfish devices.)
On about pages in the browser:
https://developer.mozilla.org/en-US/docs/Custom_about:_URLs
Failing as hrefattributes in HTML on Jolla browser, <a href="about:about">about</a>, will this change? The tech for about is underused and could significantly improve user experience, with addition of informative content, and little or no added code.
If this is untrue, please detail the ways so future work is clear and actionable.
Imagine about pages with embedded videos, audio, or text-to-speech configuration and implementation.
about:app[lications] about:recorded-phonemes about:clock about:calendar about:calculator about:bookmarks about:templates about:shell>><<< about:shell-heredocs about:this about:productivity about:multimedia-operations about:text-operations about:clipboard about:ipcs about:regular-expressions about:coding about:documentation about:display-scaling about:feedback about:localisation about:dbus-userguide about:d3js about:dmesg about:fingerterm about:revealjs about:together about:me about:you about:nemo about:us about:jolla about:standards about:otherness about:bash-command about:anonymous-statistics about:workflows about:xdg-open
Workflows would be an collection of URLs with tags, which users could edit like grouped bookmarks with manipulation semblant of pushd, popd and dirs, but for net and program links and their descriptions (not only directories). This may make browser context have more relevance in different activities' phases. The same could be done with page navigation session logs, so that activity histories would not only be merged into one list.
TODO Set up useful working example(s). Test a terminal-based version to define steps and allow alternative or fallback capability.
NOTE If code additions are required, consider using the form about:this#named_content to hook into local (downloaded) info pages.