Not sure if it helps, but you could also use the w3m browser's mentality of just keeping an HTML file that contains all of your bookmarks. I'm sure there's probably even a way to use 'eww' in the same fashion too.

Maybe even making your own personal wiki of a webring of sorts would help too.

I don't personally bookmark anything anymore but just store links on a webring on my site.

Hope this helps.

Sam

On Mon, Jan 17, 2022, at 8:03 PM, Samuel Wales wrote:
my amazon example was silly and confusing.  the point isn't shopping
for something; it's anything.  science papers, news outlets, nerd
blogs.

On 1/16/22, Samuel Wales <samologist@gmail.com> wrote:
> more below.
>
> On 12/26/20, Maxim Nikulin <manikulin@gmail.com> wrote:
>> On 26/12/2020, Samuel Wales wrote:
>>
>>> [... i can imagine great things possible with such extensions. for
>>> example, you could have sets of tabs, selected by right click in
>>> firefox, to save to a bunch of org entries.  then you could load that
>>> particular set of entries into firefox whenever you want.  and you
>>> could keep notes on each page and move the entries wherever you want.
>>> this would be useful for such things as "i am researching rice
>>> cookers; these are my tabs, but i don't want them cluttering firefox
>>> and i want them with my org notes and to make notes on them and will
>>> re-load them into firefox when i want to revisit".]
>>
>> It should be possible since some tab management extension were used in
>> mozilla to evaluate if webextensions are mature enough and if support of
>> XUL add-ons could be dropped. On the other hand do not expect such
>> feature soon. A kind of semi-blocker is absence of automatic tests to
>> run before every release, and it will require a lot of time.
>
> interesting.  i do note tab selection features in recent firefox-esr
> and i was just assuming something like that.
>
>>
>> In the meanwhile, have you looked at the following comment?
>> https://github.com/sprig/org-capture-extension/issues/12#issuecomment-323569334
>> alphapapa commented Aug 20, 2017
>>
>>> You can do this with the "Copy all URLs" extension (ID:
>>> djdmadneanknadilpjiknlnanaolmbfk). Use this as the custom format (note
>>> the linebreak):
>>>
>>> [[$url][$title]]
>>
>> I am almost sure that similar extension should exist for Firefox as well.
>
> i think this is for copying all tabs, not selected ones.  so a
> workaround for my idea would be to have a fresh firefox window
> dedicated to rice cookers and then save them all.  bit it does not
> save over existing canonical location for each url or similar.
>
> which would be needed for my idea so as to not have duplicates etc.
>
> also i think this extension does not exist any more in firefox.  i
> used to use it for storing as org links.  but it was just to store
> links in case firefox screwed up session restore.  which it usually
> does.  for that purpose, i use one that does not save as orglinks.
>
>>
>> Some points should be clarified in my opinion
>>
>> - Do you expect that metadata should be captured in addition to URLs and
>> titles? Browsers can unload some tabs making page content unavailable.
>
> i wouldn't need this i think.  i'd want page title, just as in
> ordinary org links, but in principle that can be assumed from the
> existing org entry if exists, and if not exists and you are capturing,
> the page is already loaded.  so i think not a metadata issue.
>
>> - Are you going to capture reviews of "rice cookers" that could be
>> considered as ordinary pages or you are going to save items from online
>> stores? I do not current state of affairs but I have heard about some
>> activity for special metadata that allows search engines to display
>> products in a special way. Could you inspect head element of pages in
>> your favorite stores contains desired metadata using page source or
>> inspect element tools?
>
> my web knowledge is too limited to understand your question, but i am
> just hoping it would capture ordinary amazon links, review sites, and
> so on.  and i never use js if i can avoid it so i'm expecting pretty
> normal website stuff i think.  so i'm flexible.
>
> [of course, amazon per se links might need cleaning or uniquification
> of some type for finding the version in org maybe, or maybe for
> improving privacy by removing amazon's data about you in the url, but
> that might not even need any special amazon link knowledge.
> [fanciness might look for the amazon id, if implementer willing or
> somethign exists for that.]]
>
>> - Should tab group be captured as single Org heading or it should be a
>> tree with a section per tab? I am not sure that capture will have no
>> problem with subtree. Certainly Emacs interface for org-protocol +
>> capture are not suitable for sending each tab as a separate link.
>> Another option is to create nested lists, anyway org formatter in my
>> extension need improvements. Are you expecting headings subtree or
>> nested lists?
>
> the status quo is that there is nothing, so using lists would be a
> huge improvement and work great.  but fanciness by using org sections
> if poss [i assume this means header and metadata and content and maybe
> descendents] could be more flexible.
>
>>
>>> [now if i can only debug the extra-blank-lines-in-capture problem.]
>>
>> Fully agree that it is really annoying. It is among high priority items
>> in my TODO list.
>
> we might be talking about different thinks.  i am referring to
> something in org that adds blank lines when my particular org capture
> templates are used.  i think it is outside all of the hooks that are
> available for org capture so not fixable using those.
>
> recent org might fix it dunno.  i am limited in coputer use so i have
> not tried to debug it further.  just delete the extra lines.
>
>>
>> Accidentally I pressed =C-x C-o= and discovered
>> [[help:delete-blank-lines]] innerText is not exactly the same as
>> selection range toString but the rules could work in a similar way.
>> Table rows, floating and absolutely positioned elements require
>> newlines. Such elements are often abused by designers.
>> https://html.spec.whatwg.org/multipage/dom.html#dom-innertext
>
> web stuff is above my knowledge and so i think maybe different things
> we are talking about.
>
>>
>>
>>
>
> you would still keep notes on each thing and org metadata.
>
> then you load all links in an org subtree or list, or all with a
> :firefox: tag, into firefox.  one question is making sure there is a
> canonical place for each topic.  [rice cookers, a research topic,
> etc.]
>
> metadata snags like you mention are best figured out by those who
> undertstand them unlike myself and i'd be flexible.  i'd be pleased
> with anything i think.  i don't need metadata most of the time, just
> link and page title.  this is all just an idea for cogitation.
>
> tldr you'd have a set of canonical tabs that is in org and sometimes
> in firefox as you please.  you can keep org notes on the org links and
> they won't be overwritten when you save from firefox.  you also won't
> create duplicates when you do so.
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com