Use this tool to learn about websites, specifically the one you just entered.
If you find some aspect of it inappropriate it is not our fault.
If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
Is It Cataloged?
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Find out if your site has been cataloged by top search engines for only $8.99.
Below you will see site info taken directly from the URL you entered in real time. This is also known as our URL Breakdown tool and can be used independently of our site info tool.
Page Title
Sam Ruby: FeedMesh
Stripped Text Content
This is just a sample of the content found on this website. Please visit the website to read the entire page.
"intertwingly
Search
It’s just data
FeedMesh
Sat 11 Sep 2004 at 17:19
FeedMesh
is a group working to establish a "peering network" for
decentralized
web(site log) update notifications and content
distribution .
The initial discussion happened on Sept 10th at Foo Camp.
Companies and representatives involved so far are:
Scott Johnson
( Feedster ),
Mark Fletcher
( Bloglines ),
Jim Winstead
( blo.gs ),
Jeremy Zawodny
( Yahoo! ).
The current plans are to stage the implementation into a series
of concrete, tangible steps.
The consensus is that the sharing of weblog update notifications
(" pings ") would be a
good first step. This will have two immediate and tangible benefits
for sites that aggressively crawl feeds: reduced bandwidth (by
sharing the load) and lower latency (e.g., bloglines can get data
in near realtime instead of polling every hour).
A rough sketch of what this would entail is the creation of a
single URI for people to ping (feedmesh.org?) which would be backed
by the members of the "peering network" via
round
robin DNS . The recipient of a ping would be expected to
validate the ping, make a reasonable attempt to normalize the site
name to utf-8, and then pass the ping information to all the other
members of the peer network. Instead of separate HTTP
requests per ping, it is likely that each member of the peering
network will have a socket continuously open with
each of other members across which this information will be
sent.
Follow-on steps may include the sharing of content between the
peers (possibly using
pubsub over XMPP ), and ultimately the sharing content with
aggregators running on end user desktops.
We have a
temporary Yahoo!
Group setup to facilitate e-mail discussion after Foo Camp is
over.
Sat 11 Sep 2004
Sam,
Why don't you finish one thing first? It's been over a year and all Atom has added is more fragmentation in the syndic"
....
read entire page
