The main reason is people didn't know
how to make head of tails of it. The closest thing they could relate
it to was chat, email, etc. Of course it was underwhelming because
they didn't really get the significance of what they were seeing,
because it just wasn't a ready replacement for their
a project by programmers for programmers.
It has barely started to solidify as a coherent project. I think we
should give it some time.:)
Nathan
On Thu, Jan 5, 2012 at 8:12 PM, Paul Thomas dt01pqt...@yahoo.com wrote:
It is different from a forum, however a forum like interface was exactly how
I
It is different from a forum, however a forum like interface was exactly how I
would have got people interested. Instead of going about the wave way of doing
thing an obscurities like blips, users didn't necessarily had to know any of
that. You introduce it slowly, using what user are used
I wonder if its wire protocol can be made compatible with sharejs
+1
From: Joseph Gentle jose...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Thursday, 27 October 2011, 23:02
Subject: Re: Walkaround -- Wave on App Engine
Hey, awesome.
I wonder if its wire
with the common
ways people are used to communicating.
So much of AC is specific to use case. Not having this limits your audience
considerably.
From: Thomas Wrobel darkfl...@gmail.com
To: wave-dev@incubator.apache.org; Paul Thomas dt01pqt...@yahoo.com
Sent: Thursday, 27
darkfl...@gmail.com
To: wave-dev@incubator.apache.org; Paul Thomas dt01pqt...@yahoo.com
Sent: Thursday, 27 October 2011, 16:55
Subject: Re: Walkaround -- Wave on App Engine
, it was nothing to do with advertising or just about the client.
My point was thats its relative success did have to do
Funny I thought I that too, but decided not to post.
From: Upayavira u...@odoko.co.uk
To: wave-dev@incubator.apache.org
Sent: Tue, 6 September, 2011 21:53:42
Subject: Re: Code - SVN
This is me, knowing nothing about Mercurial nor the Wave repo. But I
wonder
Yes there is too much outdated information in too many places. There should
only
be one official wiki on Apache. Google pages, should only refer to it.
From: Daniel Wilkerson daniel.wilker...@gmail.com
To: Yuri Z vega...@gmail.com
Cc:
2p
In terms of saving time. I would go for wordpress. it is not some people's idea
of elegant under the hood, I used to be cynical, but in practice it is the most
versatile CMS, and has a wide selection of plugins, and is easy to develop..
Chances are you have everything you want.
Joolma is
I think they should keep the Apache CMS to meet the basic requirements, but as
a
focal point to pull everything together I don't see a problem with an external
site done well. Interest need to be generated.
At the moment through no fault the project is spread across several sites, and
You could use another interface to generate content privately, the cached
output
could be upload as static html on Apache CMS. Personally I don't think raw html
is a massive hurdle, just it is more convenient, and less likelihood of
malformed code, with a good editor. If it is statically
Epic? WAIB goes under there.
From: Thomas Wrobel darkfl...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Mon, 29 August, 2011 14:30:16
Subject: Re: Update Wiki for Apache Wave
Sure...should I categorise this as just a TASK or maybe a
STORY.kinda new to
It is a little concerning that something that should ordinarily be so trivial
as
auto-linking is considered advanced.
I wonder if it is worth looking again at the overall architecture. From outside
it seems a hard sell, you need developers to want to get involved, both helping
WAIB grow and
how would p2p share the burden? I mean wave isn't like file share. c/s there is
less replication of heavy lifting no? I think if anything cloud technology will
be involved with wave.
I agree the onus is on the person coming up with the potential technology to
demonstrate that it would work.
. Again -
write once but use twice on both server and client.
2011/5/30 Paul Thomas dt01pqt...@yahoo.com
There was talk of getting rid of GWT a while back. I think it is
useful
for
Java
guys to prototype in, but it seems a bit of a monstrosity to me.
There
is
frameworks like
face palm. more firefly references...ominous :/
From: Adrian Cochrane alci...@eml.cc
To: wave-dev@incubator.apache.org
Sent: Sun, 29 May, 2011 9:58:12
Subject: protocols
avid Hearnden hearn...@google.com Wed, May 25, 2011 at 8:36 AM
Reply-To:
Cochrane
alci...@eml.cc
On Sun, 29 May 2011 12:54 +0200, Thomas Wrobel darkfl...@gmail.com
wrote:
Like call it Moya then, from Farscape ;)
(hay, it did last longer)
On 29 May 2011 12:52, Paul Thomas dt01pqt...@yahoo.com wrote:
face palm. more firefly references...ominous
There was talk of getting rid of GWT a while back. I think it is useful for
Java
guys to prototype in, but it seems a bit of a monstrosity to me. There is
frameworks like sproutcore, and you can hand roll with coffescript.
From: Perry Smith
and index based solution, something like Cassandra.
2011/5/9 Paul Thomas dt01pqt...@yahoo.com
I think this was discussed before. folders are a bit old school. tags and
specifically personal tags were suggested.
From: Arne Eggert arne.egg...@googlemail.com
Following Yuri's Poll I noticed that Access control wasn't listed other then
public waves. A while ago that issue was discussed. I'll admit I was probably
the first to caution. That is becuase I didn't want access control to become
inflexible by design, and I was theorising custom access
While Googles own service was limited to a single domain (for obvious
business
reasons)
i always believed there was low incentive for Google to produce a non
centralised system. They want to do well in social networking after all. Non
centralised Facebook, don't think so.
wavelet and the permissions given to the group.
--Nathanael Abbotts
On 22 Apr 2011 14:01, Paul Thomas dt01pqt...@yahoo.com wrote:
I just thought of something. What if you could could be a participant once
with
different options? So therefore if you create blip under edit only than
blip
is only yours
participants of that wavelet access to the wavelet they are
added to. They retain the intersection of their permissions on the addressed
wavelet and the permissions given to the group.
--Nathanael Abbotts
On 22 Apr 2011 14:01, Paul Thomas dt01pqt...@yahoo.com wrote:
I just thought of something
I was wondering how the rewrite of pygowave was going
From: Adrian Cochrane alci...@eml.cc
To: wave-dev@incubator.apache.org
Sent: Fri, 22 April, 2011 21:44:25
Subject: Federation, multiple servers
hello there,
I am the manager of PyOfWave
I thought the video gave a pretty good explanation anyway. Purist XML is pretty
overrated anyway, it creates more problems than it solves. Consider the XHTML
debacle. What if W3C had continued to be stubborn on that issue, and they
hasn't
listened to HTML5 crowd. There was an obsession with
isn't the whole point of the c/s protocol that it allows to you do what you
want? It is not dependent on a particular setup. I'm all for decoupling the
client in the code, but also want an an agnostic application interface so you
can choose how and what you want to design as a client.
Client
personally I think using xmpp for c/s is unnecessary for now.
- Original Message
From: Thomas Wrobel darkfl...@gmail.com
To: wave-dev@incubator.apache.org
Cc: Michael MacFadden michael.macfad...@gmail.com
Sent: Sat, 9 April, 2011 23:32:38
Subject: Re: XMPP over websockets
Remember
can include the updated
logo
in my patch that updates the WIAB login page.
Yuri
2011/3/30 Paul Thomas dt01pqt...@yahoo.com
Ok here is a simplified and rationalised version of the existing logo.
The main change is it is slightly less fussy. The is one vanishing point
and it
actually follows
concur can't wait for the c/s protocol.
- Original Message
From: Thomas Wrobel darkfl...@gmail.com
To: wave-dev@incubator.apache.org
Cc: Alex North a...@alexn.id.au
Sent: Sun, 3 April, 2011 21:35:21
Subject: Re: A change in my contributions
Sorry to hear you left google, but any and
-france.blogspot.com
2011/3/25 Zachary “Gamer_Z.” Yaro zmy...@gmail.com
This is an interesting design. Not that I do not like your logo, but I
prefer the simplicity of the current logo.
--Zachary “Gamer_Z.” Yaro
On Thu, Mar 24, 2011 at 14:12, Paul Thomas dt01pqt...@yahoo.com wrote
.” Yaro zmy...@gmail.com
This is an interesting design. Not that I do not like your logo, but I
prefer the simplicity of the current logo.
--Zachary “Gamer_Z.” Yaro
On Thu, Mar 24, 2011 at 14:12, Paul Thomas dt01pqt...@yahoo.com wrote:
Slight correction
- Original Message
Yeh I was going to say that. However you can't trademark a wave shape. So there
is nothing stopping using a wave in thier design so long as the direct
association is not there.
I'd be up for a logo design comp. I could do it in inkscape as a plain svg.
- Original Message
From: Soren
On Fri, Mar 11, 2011 at 18:55, Paul Thomas dt01pqt...@yahoo.com
wrote:
I like the idea of personal super tags or hashes. However why should
they
just
be personal? I think there should be public hash tags as well.
Folders just doesn't make sense in this day an age, too
...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Sat, 12 March, 2011 19:15:32
Subject: Re: Proposal for organization of waves
How is that different from a saved search?
On Mar 12, 2011 7:58 AM, Paul Thomas dt01pqt...@yahoo.com wrote:
I think there has been a misunderstanding.
I was proposing
I like the idea of personal super tags or hashes. However why should they just
be personal? I think there should be public hash tags as well.
Folders just doesn't make sense in this day an age, too old school
hierarchical.
- Original Message
From: Thomas Wrobel darkfl...@gmail.com
You wouldn't want every feature anyway. Just becuase it was used in Google Wave
doesn't mean it was the best solution for the problem. Don't forget that Google
Wave was a proof of concept.
- Original Message
From: Yuri Z vega...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Wed,
about subwavelets before. Is it in the whitepapers?
On Wed, Feb 23, 2011 at 00:21, Paul Thomas dt01pqt...@yahoo.com wrote:
The simplest would just be to have subwavelts. In that they are two
wavelets
with distinct histories, but one is in the other. But regardless their
histories
are only
Personally I think SMTP is the wrong protocol for Wave. I know that Chris
argues
that it is essential for enterprise, I actually disagree.The wave/email analogy
was always a false one. Currently there is no mature wave services. I know that
frustrates some people, but frankly it has little to
I don't know, but it wasn't too smooth with Gwave.
- Original Message
From: Gerardo Lozano glozan...@gmail.com
To: wave-dev@incubator.apache.org
Sent: Mon, 21 February, 2011 19:31:37
Subject: Re: is wave playback a priority right now?
What would be the best way to approach playback
Large waves are a problem in general. I wonder how WIAB would cope. it is
definitely something that need to be addressed, how to represent large waves.
- Original Message
From: STenyaK sten...@gmail.com
To: wave-dev@incubator.apache.org
Cc: Paul Thomas dt01pqt...@yahoo.com
Sent: Tue
Thanks is interesting.
One point of playback is to quickly get updated on what you have missed. So
therefore you don't really have to have have every singe change.
It is kind of like flicking through the unread blips, except that doesn't have
blip level history. I would be good if you could
, it
should be clear, that solutions of the first kind , most probably will be
provided by 3-rd parties and not by the WIAB community.
2011/2/22 Paul Thomas dt01pqt...@yahoo.com
Personally I think SMTP is the wrong protocol for Wave. I know that Chris
argues
that it is essential
Does it really have to e that complicated? You only really need the fonts and
colour scheme and a logo. There is hardly anything wrong with the theme at the
moment TBH. The current scheme of WAIB is simpler still :)
According to their licence GWave don't wasn't us to use their logo. Presumably
Like is already covered by many existing gadgets and likely (caja like)
distributed agents in the future (and I would suggest an api that has the
ability to add menu items and buttons to common controls of blip and wave
albeit interface agnostic as possible).
--- On Wed, 9/2/11, David
How comes no mention of federation? I would put that in the description.
--- On Tue, 8/2/11, Soren Lassen so...@google.com wrote:
From: Soren Lassen so...@google.com
Subject: Re: Incubator PMC/Board report for February 2011
(wave-dev@incubator.apache.org)
To: wave-dev@incubator.apache.org
...and also graphical client, I would put a brief description of what the
server is. Then a brief description of the point of WAIB as a package.
--- On Wed, 9/2/11, Paul Thomas dt01pqt...@yahoo.com wrote:
From: Paul Thomas dt01pqt...@yahoo.com
Subject: Re: Incubator PMC/Board report
That's what I thought, but maybe it wasn't obvious where to turn to for the
stated reasons.
As for the wave brand. the obscurity or terms like 'wave', 'blip', etc were
king of emblematic of the problem with google wave. Not being relatable to
everyday users.
I think it is too late to change
of
communication would be a great shame.
-Thomas
On 30 January 2011 00:28, Paul Thomas dt01pqt...@yahoo.com
wrote:
That's what I thought, but maybe it wasn't obvious
where to turn to for the stated reasons.
As for the wave brand. the obscurity or terms like
'wave', 'blip', etc were king
Typo XMPP
--- On Fri, 28/1/11, Paul Thomas dt01pqt...@yahoo.com wrote:
From: Paul Thomas dt01pqt...@yahoo.com
Subject: Re: ProcessOne appears to be forking
To: wave-dev@incubator.apache.org
Date: Friday, 28 January, 2011, 9:28
I won't be hard to convince people
that XMTP is superior
Here is my 5p.
I support any
number of persistence implementations, the more the merrier, so long
as it doesn't disrupt WAIB development.
I do
however think that WAIB should support one default implementation
that is hassle free but still
50 matches
Mail list logo
