Flock, the New Browser on the Block
^tamago^ writes to tell us BusinessWeek Online is reporting that a new browser is stepping into the arena. This new competitor, Flock, hopes to change the face of web browsing by turning their's into the swiss army knife of browsers. From the article: "Flock's browser is built specifically for a new, emerging generation of Web users, one that isn't satisfied passively browsing media online. Flock hopes to turn the browser into a dashboard for collaborating, blogging, sharing photos, reveling in a raft of other group activities that have recently caught fire online"
Instead of telling someone to visit a website, I can tell them to "Flock This!"
I what proactive MBA envisioned the synergies that would allow flock to become a knowledge portal center of excellence for podcasting core competencies of leveraging mindshare and paradigm shifts to achieve superlinear ROI.
Expect Flock to crash and, from time to time, lose all your data.
OK, so apparently it's at least as stable as IE.
I've seen this feature before, but I can't recall where...
they can't develop a web page worth a crud...
:)
They probably spent all of their website design budget on this slashvertisement.
"You're older than you've ever been, and now you're even older."
Oh and hey, wanna join the flock? We're hiring! So guess what? Send us your resume! ...Meet the Flockers?
Guy asked me for a quarter for a cup of coffee. So I bit him.
SPOILER: flock.com kills eyes!
The Farewell Tour II
FLOCK(2) Linux Programmer's Manual FLOCK(2)
NAME
flock - apply or remove an advisory lock on an open file
SYNOPSIS
#include <sys/file.h>
int flock(int fd, int operation)
DESCRIPTION
Apply or remove an advisory lock on an open file. The
file is specified by fd. Valid operations are given
below:
LOCK_SH Shared lock. More than one process may
hold a shared lock for a given file at a
given time.
LOCK_EX Exclusive lock. Only one process may
hold an exclusive lock for a given file
at a given time.
LOCK_UN Unlock.
LOCK_NB Don't block when locking. May be speci­
fied (by or'ing) along with one of the
other operations.
A single file may not simultaneously have both shared and
exclusive locks.
A file is locked (i.e., the inode), not the file descrip­
tor. So, dup(2) and fork(2) do not create multiple
instances of a lock.
RETURN VALUE
On success, zero is returned. On error, -1 is returned,
and errno is set appropriately.
ERRORS
EWOULDBLOCK
The file is locked and the LOCK_NB flag was
selected.
CONFORMING TO
4.4BSD (the flock(2) call first appeared in 4.2BSD).
NOTES
flock(2) does not lock files over NFS. Use fcntl(2)
instead: that does work over NFS, given a sufficiently
recent version of Linux and a server which supports lock­
ing.
flock(2) and fcntl(2) locks have different semantics with
respect to forked processes and dup(2).
SEE ALSO
open(2), close(2), dup(2), execve(2), fcntl(2), fork(2),
lockf(3)
There are also locks.txt and mandatory.txt in
/usr/src/linux/Documentation.
Linux 1998-12-11 FLOCK(2)
That's why I only install stuff like this at school.