Slashdot Mirror

I also didn't like "If we modify these Terms of Service, we will post the modification on the Site or provide you with notice of the modification". *Or* provide me notification? So they basically can change the terms at any time just by posting a new set to the web site, and they aren't even promising I will be notified? Yeah, let me jump right on agreeing to that.

The main options I'm aware of for hosting your own bookmark server are:

• Cutemarks. Pretty simple, but not maintained anymore I think.
• Firefox Sync Weave server. Seems like it's trying to solve way more complicated problems than I really care about, with the associated complexity that comes with that.
• Firefox Sync server on Google App Engine. Interesting proof of concept, adding another server source compatible with Firefox's API. I don't really trust Google's infrastructure either though, and this hasn't moved much beyond prototype yet.

Perhaps the terrible terms for the relocated Delicious site will finally kickstart more development in this area.

What worries me more about the strange shift in numbering, is that they are planning to axe a number of features to favor sync.

(Source: http://decafbad.com/blog/2011/02/06/pay-phones-and-firefox-features/comment-page-1#comment-467395 )

I can do without the microwhatever, but after all the time I spent tagging and getting the routine of tagging new bookmarks, I am not going to enjoy this. Fortunately there seems to be some vocal support for them.
Same with places queries, they are quite powerful and helped me organize my bookmarks a lot...
If there's anyone with a minimal of "influence" (AKA his/her opinion won't be disregarded as null), please step in and help preventing the browser from being directly wired to the cloud, as many mozilla people is suggesting. They can't axe tags because of sync. (I am not making this up unfortunately, check the bugzilla links in the article and how some suggest the whole bookmark system to rely on web services).

That single programmer probably wouldn't have made much of a dent in the situation, but another pissed off programmer took his work, and made it work on his system, twice and got federation to work, then wrote to tell the rest of us about it.

It was only after this that the blogosphere actually has a snowballs chance in hell of adding any value, by making sure that other people know about the efforts of these two programmers (and all of the ones before them).

As he said over at 0xDECAFBAD, '...ideas are fucking worthless', it's actually adding some value to the ideas, no matter how big or small, that get the snowball rolling in the right direction.

I hope this post helps someone else see how open source really works. If not, it's fucking worthless.

--Mike--

If design allows, use the response handler of the XSLT doc to call the request for the XML data, to ensure XSLT is available when XML arrives. If that won't work (ie, when you need the same XSLT file for a variety of XML docs), have the XSLT handler set a flag to true when fully loaded, then wrap calls to dependent XML docs in functions that are called directly if the flag is true, but otherwise are diverted to a timeout/repeater/timed event that checks the flag each second or so (for a max number of seconds) until the XSLT doc is available. Most Ajax toolkits set up a kind of dependency array where you can queue pointers to the functions that are all waiting on the same condition, so that they get called in script order when the condition becomes true.

If that makes no sense, well, it's a little off-topic, so I probably shouldn't elaborate.

IMHO, XSLT is still not quite ready for prime time (doesn't work right in some of the major browsers) so do a sanity check in Firefox to see if it's your code that's messed up, or just a browser quirk. I have done lots of tests between XML+XSLT and subformats (XML subsets of XHTML based on microformats), and the subformats win hands down every time. For now, I'd advise holding off on client-side XSLT for at least another year. Subformats are full-fledged XML, they're just not quite as "semantic" as freeform XML can be.

I'm not sure if there's a standard microformat for slide presentations, but I use XOXO, a general-purpose hierarchical outine system that has a lot of support (including a WYSIWYG online editor script by Les Orchard). The way I'm using XOXO, scriptless browsers see a familiar bullet list with links to slides, then use the back button to return to the list if they can't handle framesets. Ajax browsers get treated to a full-featured slideshow with cross-fading, simple animations, and an optional hierarchical floating menu to skip to any slide (same XOXO file with different CSS). With the right CSS and JS, the same XOXO-based list can auto-adapt to the client.

I won't be adding the article's version of automatic pan-and-zoom (Ken Burns effect) because it's a little too inflexible and rudimentary. All my project's missing is a flag and a randomizer, so no need for a new approach. The article might be a decent academic tutorial for students unfamiliar with XHR. However, I wouldn't suggest using the article's ideas in any production work, as many better options are readily available.

I've been looking for a decent version of something like this for ages. I've previously investigated Agent Frank, WebMate, IProxy, and I've used WBI. All seem lacking in some way.
PPS looks promising. I'd like to see the search functionality of PPS integrated into the proxy so you can do a search right from the browser and it can show you live links......

Combined with AmphetaOutlines it is really powerfull.

Here is a page describing how to use the DSB-R100 to timeshift radio in OSX.