Re: A different approach for bookmarks.

[belg4mit]

While not a bad solution I personally prefer Roaming access via mod_roaming. Though I still end up shoving around 280k of bookmarks.

Recently to alleviate some of this load I have been trying to not bookmark software (the biggest culprit). Instead (horrors!) I use this as a link on my personal toolbar.

javascript:document.location='https://pthbb.org:3160/snarf/add.cgi?Nam
+e='+escape(document.title)+'&URL='+escape(document.location)

This sends the relevant data in a query string to a custom Webmin module I wrote. Where I can expound upon the link in more detail and finally dump into MySQL (uses EZDBI/EZDBI, tres cool). The final results of which can be accessed here. I think it's a pretty good solution though not complete as I currently do not have a system for managing links in the database.

So in the end I guess the releavnt bit is, why not allow posting of the links via CGI? (If SSL w/ 401 authentication or trusted IP dump them straight in, else queue them in a spool to be verified). For me the biggest obstacle in using any other bookmark system is that it must be not much more complicated; read different from accquired habits; than C-d (or whaterver the add bookmark shortcut is for you browser/platform combo). If you allow CGI submissions as well then you use a similar bookmark. Come to think of it how about this for a personal toolbar link for your system as it is:

javascript:document.location='mailto:[e-mail]?subject='+doc
+ument.location

UPDATE: Changed mocha: to javascript:

--
perl -p -e "s/(?:\w);([st])/'\$1/mg"

[belg4mit]

jeffa's node made me realize I missed a few things.

First, why do a substitution on the body string, it is unnecessary, a match is all you need.

To use that javascript example you'd need to support URL's in the subject. So all in all I'd imagine you'd want to support a single URL in the subject (and use the body for annotation?), or one+ URL in the body (you currently support):

Untested

my $URL = qr/(http:\/\/[^\s]*)/;
#Since we use the expression twice it's nice to have it
#as a variable.
#[TheDamian]'s [cpan://Regexp::Common] would be useful once it
#supplies URL matching
#Until then you might want to expand this, it doesn't
#support port numbers or FTP.


for (my $i=1; $i <= $pop->Count(); $i++) # Loop through messages
{
    #Support personal toolbar button for spontaneity linking
    foreach( $pop->Head($i) ) {
    #If you wanted to get fancy you could use Head in scalar
    #context with multi-line regexp and avoid the foreach
      if( /^Subject:\s+$RE/i ){;
          push @linkList, $1;
      print "$1\n";
          #fetch body for description here if you want
          next;
      }
    }
    my $body = $pop->Body($i);
    #Just a match ma'am
    while ($body =~ /$RE/)
    {
       push @linkList, $1;
       print "$1\n";
    }

    $pop->Delete($i);
 }
 $pop->Close();

--
perl -p -e "s/(?:\w);([st])/'\$1/mg"