...@example.net/uri
/author
idurn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6/id
/feed
/item
It that item we can also have some metadata about the node. Number of
comments for example or a link to a root comment in comments node.
--
With best regards,
Sergey Dobrov,
XMPP Developer
from it so the
tag will be look as this:
tag:montague.lit,2008-05-08:posts-1cb57d9c-1c46-11dd-838c-001143d5d5db. That's
right for any example in the XEP.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
in the web interface?
Thanks,
Valérian Saliou
Jappix founder
Le jeudi 05 mai 2011 à 00:55 +0700, Sergey Dobrov a écrit :
On 04/21/2011 11:44 PM, Dobrov Sergey wrote:
1. in all examples atom:id are incorrect.
http://tools.ietf.org/html/rfc4151#section-2 says that tag scheme url
syntax
subscribers?
Justin
Why to do that? I think that it is enough to retrieve it by request with
node's metadata. Suddenly I don't know if any pubsub implementation
support it.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
think XEP-0277 should require item ids and atom
ids to match, unless someone can explain why this is not a good idea.
Thanks,
Justin
I think so too. And I think that pubsub should have a possibility to
track changes of items.
--
With best regards,
Sergey Dobrov,
XMPP Developer
On 05/11/2011 01:46 AM, Justin Karneges wrote:
On Tuesday, May 10, 2011 11:14:04 AM Sergey Dobrov wrote:
I think that it is enough to retrieve it by request with
node's metadata.
The problem there is that you cannot track updates to the count without
polling.
Every event adds
On 05/11/2011 02:44 AM, Justin Karneges wrote:
On Tuesday, May 10, 2011 11:57:19 AM Sergey Dobrov wrote:
On 05/11/2011 01:46 AM, Justin Karneges wrote:
On Tuesday, May 10, 2011 11:14:04 AM Sergey Dobrov wrote:
I think that it is enough to retrieve it by request with
node's metadata
On 05/11/2011 03:16 AM, Justin Karneges wrote:
On Tuesday, May 10, 2011 12:57:22 PM Sergey Dobrov wrote:
On 05/11/2011 02:44 AM, Justin Karneges wrote:
On Tuesday, May 10, 2011 11:57:19 AM Sergey Dobrov wrote:
On 05/11/2011 01:46 AM, Justin Karneges wrote:
On Tuesday, May 10, 2011 11:14:04 AM
blog storage)
3. Change pubsub#access_model to open to allow any user to comment
to a post. (Or restrict this property in accordance to user's settings)
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
mercredi 11 mai 2011 à 18:25 +0700, Sergey Dobrov a écrit :
I don't agree that we should use standard node configuration for
microblogs nodes. That's my suggestions:
For microblog node itself:
1. We should change pubsub#notify_retract to true to track removed
items to remove them from UI.
2. Change
for a node but I don't think that this is really
easy way to retrieve such a basic information. (I don't know how it will
be efficient for server side)
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
side)
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
On 06/02/2011 10:39 PM, Arc Riley wrote:
On Thu, Jun 2, 2011 at 7:03 AM, Sergey Dobrov bin...@jrudevels.org
mailto:bin...@jrudevels.org wrote:
some files. But I never heard of the XEP-0135, will read it as soon as
possible. Anyway, by looking at it quickly, it gives me some ideas
On 06/03/2011 12:01 AM, Arc Riley wrote:
On Thu, Jun 2, 2011 at 12:30 PM, Sergey Dobrov bin...@jrudevels.org
mailto:bin...@jrudevels.org wrote:
I agree but if file attachment already in XEP we have to specify how
client could upload it. Am I wrong?
The XEP is in experimental
I think that we should add an ability to add categories (e.g. tags) to
the posts (and/or comments). That is easy using entry:category Atom element:
category term=xmpp/
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
content type=textMy post/content
...
/entry
Obviously, implementations should parse both variants of placement of
atom:author but I think that we should suggest the simplest variant in
our examples.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
and will be sent with each event to detect
such changes.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
such a basic information. (I don't know how it will
be efficient for server side). Partially the problem can be solved with
RSM but it's impossible to know count of items without node retrieving.
I already heard here the suggestion to include this value in each pubsub
event.
--
With best regards,
Sergey
think that we need to
return some metadata too including creation and modification times as
well as item publisher.
What do others think? And where do we document this?
Add a Item ordering paragraph to XEP-0060?
Justin
--
With best regards,
Sergey Dobrov,
XMPP Developer
On 07/08/2011 11:51 PM, Justin Karneges wrote:
On Friday, July 08, 2011 04:44:20 AM Sergey Dobrov wrote:
On 07/08/2011 04:37 AM, Justin Karneges wrote:
b) if RSM is used by the server, then items are returned in a
node-specific
order.
What means node-specific?
I just mean
, there is this email from Sergey Dobrov that has not any answer:
http://mail.jabber.org/pipermail/standards/2011-June/024618.html . It's a
pity
'cause there are many interesting remarks in it. For example, I agree that
adding tags would be nice, or the need to have a way to get items count.
I
On 08/18/2011 08:09 PM, Goffi wrote:
Le Jeudi 18 Août 2011 19:29:21, Sergey Dobrov a écrit :
first, here are my main needs for microblogging:
- the possibility to have several nodes with different access models,
and for a user to subscribe to them automatically
Could you give some example
that we need to know about item retraction as well as about
item publishing. The same thing about item update. The possibility to
get items by date and time is good but it's not cover these problems and
it's not necessary at this time from my point of view.
--
With best regards,
Sergey Dobrov
On 08/18/2011 09:47 PM, Goffi wrote:
Le Jeudi 18 Août 2011 20:40:05, Sergey Dobrov a écrit :
It's a bad idea to append the number to the namespace since it reserved
for different revisions of XEP and not for your purpose. Again, I think
that this should be solved by some privacy lists
On 08/23/2011 09:14 AM, Justin Karneges wrote:
On Monday, August 22, 2011 05:12:54 AM Sergey Dobrov wrote:
On 08/19/2011 04:55 AM, Justin Karneges wrote:
On Thursday, August 18, 2011 05:10:58 AM Goffi wrote:
- the ability to get missed items between the last time a contact was
disconnected
On 08/24/2011 01:38 AM, Justin Karneges wrote:
On Tuesday, August 23, 2011 04:34:12 AM Sergey Dobrov wrote:
On 08/23/2011 09:14 AM, Justin Karneges wrote:
The basic solve for item retraction is for the server to keep deletion
markers around. For example the server could clear all content
On 08/25/2011 03:36 AM, Justin Karneges wrote:
On Wednesday, August 24, 2011 03:34:27 AM Sergey Dobrov wrote:
On 08/24/2011 01:38 AM, Justin Karneges wrote:
On Tuesday, August 23, 2011 04:34:12 AM Sergey Dobrov wrote:
On 08/23/2011 09:14 AM, Justin Karneges wrote:
The basic solve for item
On 08/26/2011 01:08 AM, Justin Karneges wrote:
On Thursday, August 25, 2011 07:27:16 AM Sergey Dobrov wrote:
On 08/25/2011 03:36 AM, Justin Karneges wrote:
Yes, if tracking changes is needed then the node should have a way of
offering items ordered by modified time.
Being able to query
On 08/31/2011 02:56 AM, Justin Karneges wrote:
On Tuesday, August 30, 2011 04:16:29 AM Sergey Dobrov wrote:
By dynamic node, I just mean the node can accept parameters when fulfilling
requests.
I guess you could write some reusable code that marshals the parameters (i.e.
popping them
On 09/01/2011 03:21 AM, Justin Karneges wrote:
On Wednesday, August 31, 2011 11:32:53 AM Sergey Dobrov wrote:
IMO, the commenting approach described in XEP-277 is too simple and rather
uninspired (full disclaimer: I work at a company whose sole product is
commenting). Commenting is similar
On 09/02/2011 01:22 AM, Sergey Dobrov wrote:
On 09/01/2011 03:21 AM, Justin Karneges wrote:
On Wednesday, August 31, 2011 11:32:53 AM Sergey Dobrov wrote:
IMO, the commenting approach described in XEP-277 is too simple and
rather
uninspired (full disclaimer: I work at a company whose sole
On 09/02/2011 03:32 AM, Justin Karneges wrote:
On Thursday, September 01, 2011 11:22:30 AM Sergey Dobrov wrote:
Then, my questions about XEP-303:
1) Why to use three nodes? Info node can be replaced by some item with
some constant id. about necessity of activity node I don't understood
On 09/03/2011 12:41 AM, Justin Karneges wrote:
On Friday, September 02, 2011 04:29:25 AM Sergey Dobrov wrote:
On 09/02/2011 03:32 AM, Justin Karneges wrote:
On Thursday, September 01, 2011 11:22:30 AM Sergey Dobrov wrote:
Then, my questions about XEP-303:
1) Why to use three nodes? Info node
On 09/05/2011 12:17 PM, Justin Karneges wrote:
On Saturday, September 03, 2011 03:07:45 AM Sergey Dobrov wrote:
On 09/03/2011 12:41 AM, Justin Karneges wrote:
The drawback to node metadata is it does not support update
notifications. I have the need to track this data, particularly
On 09/07/2011 07:40 AM, Justin Karneges wrote:
On Sunday, September 04, 2011 11:47:55 PM Sergey Dobrov wrote:
On 09/05/2011 12:17 PM, Justin Karneges wrote:
On Saturday, September 03, 2011 03:07:45 AM Sergey Dobrov wrote:
On 09/03/2011 12:41 AM, Justin Karneges wrote:
The drawback to node
isn't
needed and can't be solved with the current caps behavior.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
Please discuss the problem.
On 09/27/2011 11:35 PM, Sergey Dobrov wrote:
The problem have it's begging in this ejabberd ticket:
https://support.process-one.net/browse/EJAB-1473
I have small microblogging experimental project based on XEP-277, when
user wants to read some user, he sends
On 10/19/2011 10:25 PM, Kevin Smith wrote:
On Tue, Sep 27, 2011 at 5:35 PM, Sergey Dobrov bin...@jrudevels.org wrote:
The behaviour here is pretty much by design - the PEP defaults are
there for mutually shared information (e.g. extended presence) between
people with mutual presence subs
On 10/19/2011 10:56 PM, Kevin Smith wrote:
On Wed, Oct 19, 2011 at 4:51 PM, Sergey Dobrov bin...@jrudevels.org wrote:
On 10/19/2011 10:25 PM, Kevin Smith wrote:
On Tue, Sep 27, 2011 at 5:35 PM, Sergey Dobrov bin...@jrudevels.org wrote:
The behaviour here is pretty much by design - the PEP
? After each connect and to each user
with the to subscription state?
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
On 10/19/2011 11:33 PM, Dave Cridland wrote:
On Wed Oct 19 17:24:21 2011, Sergey Dobrov wrote:
On 10/19/2011 11:15 PM, Kevin Smith wrote:
On Wed, Oct 19, 2011 at 5:07 PM, Joe Hildebrand jhild...@cisco.com
wrote:
On 10/19/11 9:25 AM, Kevin Smith ke...@kismith.co.uk wrote:
The behaviour
On 10/20/2011 03:56 AM, Dave Cridland wrote:
On Wed Oct 19 19:27:01 2011, Sergey Dobrov wrote:
The difference is that presence will be sent by server without client's
participation. And it's good from the point of traffic economy view. As
I can understand, the central target of entity
On 10/20/2011 03:43 PM, Dave Cridland wrote:
On Thu Oct 20 09:19:06 2011, Sergey Dobrov wrote:
On 10/20/2011 03:56 AM, Dave Cridland wrote:
a) Probes are sent from the bare jid.
b) Probes don't have an unavailable equivalent, needed to later remove
the subscription.
How this solved
Could anyone tell me if that problem will be solved somewhere or it's
destiny predetermined? I really blocked by this bug and have to make a
choice to follow XSF's documents or drop them and build my own system.
On 09/27/2011 11:35 PM, Sergey Dobrov wrote:
The problem have it's begging
all users capabilities, it can store only capabilities of
it's own users. Also, events can be sent only once to bare jid and not
to each full jid, etc.
On 09/27/2011 11:35 PM, Sergey Dobrov wrote:
The problem have it's begging in this ejabberd ticket:
https://support.process-one.net/browse/EJAB
On 12/13/2011 01:42 AM, Peter Saint-Andre wrote:
On 12/12/11 1:43 AM, Sergey Dobrov wrote:
On 12/12/2011 02:37 AM, Kevin Smith wrote:
On Fri, Dec 9, 2011 at 12:15 PM, Sergey Dobrov bin...@jrudevels.org wrote:
snip/
9. How A's server can know that it don't have to send statuses to B
anymore
On 12/13/2011 02:28 PM, Kevin Smith wrote:
On Tue, Dec 13, 2011 at 7:23 AM, Sergey Dobrov bin...@jrudevels.org wrote:
The problem I have now is to understand the process to understand how
can be done the same process for the PEP. And I testing on two ejabberds
(2.1.7/2.1.9) that installed
On 12/13/2011 10:01 PM, Matthew Wild wrote:
On 13 December 2011 14:16, Sergey Dobrov bin...@jrudevels.org wrote:
On 12/13/2011 02:28 PM, Kevin Smith wrote:
On Tue, Dec 13, 2011 at 7:23 AM, Sergey Dobrov bin...@jrudevels.org wrote:
The problem I have now is to understand the process
On 12/09/2011 07:59 PM, Dave Cridland wrote:
On Fri Dec 9 12:18:14 2011, Sergey Dobrov wrote:
Guys, don't you think that it might be reasonable to filter messages on
receiver's server side and not on sender's side. I understand that it
will break compatibility and will no work if receiver's
On 12/14/2011 06:32 PM, Kevin Smith wrote:
On Wed, Dec 14, 2011 at 9:23 AM, Sergey Dobrov bin...@jrudevels.org wrote:
On 12/09/2011 07:59 PM, Dave Cridland wrote:
On Fri Dec 9 12:18:14 2011, Sergey Dobrov wrote:
Guys, don't you think that it might be reasonable to filter messages
On 12/14/2011 07:19 PM, Dave Cridland wrote:
On Wed Dec 14 11:53:50 2011, Sergey Dobrov wrote:
You can query the PEP service and it'll tell you the subscribed nodes,
so you only need to store the services - in your described scenario
these services would be stored in your roster, which
On 12/14/2011 10:39 PM, Dave Cridland wrote:
On Wed Dec 14 12:51:22 2011, Sergey Dobrov wrote:
On 12/14/2011 07:19 PM, Dave Cridland wrote:
On Wed Dec 14 11:53:50 2011, Sergey Dobrov wrote:
You can query the PEP service and it'll tell you the subscribed nodes,
so you only need to store
On 12/15/2011 01:05 AM, Dave Cridland wrote:
On Wed Dec 14 16:54:55 2011, Sergey Dobrov wrote:
On 12/14/2011 10:39 PM, Dave Cridland wrote:
On Wed Dec 14 12:51:22 2011, Sergey Dobrov wrote:
On 12/14/2011 07:19 PM, Dave Cridland wrote:
On Wed Dec 14 11:53:50 2011, Sergey Dobrov wrote
On 12/16/2011 01:02 AM, Dave Cridland wrote:
On Thu Dec 15 12:54:28 2011, Sergey Dobrov wrote:
I meant that if I have a contact in my roster with from subscription
then I will receive it's events but I don't want to receive them because
I did not request it's subscription. I have to filter
On 12/16/2011 11:27 PM, Dave Cridland wrote:
On Fri Dec 16 09:41:11 2011, Sergey Dobrov wrote:
And will increase traffic for clients which don't support microblogging.
The PEP protocol is again loss. The things that it was designed for are
work well only for very simple protocols like moods
On 12/20/2011 06:04 PM, Dave Cridland wrote:
On Tue Dec 20 09:06:07 2011, Sergey Dobrov wrote:
We have the same disadvantages here:
I'm not convinced, but even if this is the case, it limits the scope.
1. node ACLs can't be used (but it can for filtering on destination
server)
I
Buddycloud's standards are very far of generic pubsub. The problem with
them is that them never will be implemented widely because of them
complexity.
ok, sorry for wasting your time, i am closing the project.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
will be suitable if we need
to know which author published which item. Such problems NEED to be
solved too because, really, pubsub has great idea inside but it's
impossible to build more high level protocols with such approach.
Regards,
Florian Florob Zeitz
--
With best regards,
Sergey Dobrov
On 12/27/2011 01:12 AM, Tuomas Koski wrote:
Hello all and specially Sergey,
On 22 December 2011 12:38, Sergey Dobrov bin...@jrudevels.org wrote:
Buddycloud's standards are very far of generic pubsub. The problem with
them is that them never will be implemented widely because of them
On 12/29/2011 12:01 AM, Matthew Wild wrote:
On 28 December 2011 10:33, Sergey Dobrov bin...@jrudevels.org wrote:
On 12/27/2011 01:12 AM, Tuomas Koski wrote:
On 22 December 2011 12:38, Sergey Dobrov bin...@jrudevels.org wrote:
ok, sorry for wasting your time, i am closing the project
agree - we should ensure
there's some better specification on those - but it's worth noting that
the form field standardizations certainly should be normative (but
should be pointing to more discussion where needed).
What else were you missing?
Dave.
--
With best regards,
Sergey Dobrov
On 01/09/2012 08:46 PM, Dave Cridland wrote:
On Mon Jan 9 13:28:48 2012, Sergey Dobrov wrote:
As I can understand, you just have a service which tracks other users
locations. For such reason, current PEP is really suitable. But if you
will try to track one's location by many users you
On 01/10/2012 12:44 AM, Stephen Pendleton wrote:
-Original Message-
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org] On
Behalf Of Sergey Dobrov
Sent: Monday, January 09, 2012 8:29 AM
To: standards@xmpp.org
Subject: Re: [Standards] PEP and PubSub
On 01/06
On 01/10/2012 04:04 PM, Kevin Smith wrote:
On Tue, Jan 10, 2012 at 8:00 AM, Sergey Dobrov bin...@jrudevels.org wrote:
But there's more than that, too - you'd want to get the microblog in
total, rather than having to be online to keep track of it - that is,
you don't want to miss any posts. So
On 01/10/2012 10:03 PM, Stephen Pendleton wrote:
-Original Message-
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org] On
Behalf Of Sergey Dobrov
Sent: Tuesday, January 10, 2012 3:06 AM
To: standards@xmpp.org
Subject: Re: [Standards] PEP and PubSub
1. No, I
On 01/11/2012 10:20 PM, Stephen Pendleton wrote:
-Original Message-
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org]
On
Behalf Of Sergey Dobrov
Sent: Tuesday, January 10, 2012 3:06 AM
To: standards@xmpp.org
Subject: Re: [Standards] PEP and PubSub
Anyway, what
On 01/11/2012 10:37 PM, Dave Cridland wrote:
On Wed Jan 11 15:33:29 2012, Sergey Dobrov wrote:
I will say it again: the solution may be implemented with transition
period which will support both methods. The second thing I already said
that it will not broke clients at all. Servers upgrade
On 01/11/2012 10:57 PM, Dave Cridland wrote:
On Wed Jan 11 15:49:58 2012, Sergey Dobrov wrote:
On 01/11/2012 10:37 PM, Dave Cridland wrote:
On Wed Jan 11 15:33:29 2012, Sergey Dobrov wrote:
I will say it again: the solution may be implemented with transition
period which will support both
On 01/11/2012 11:19 PM, Kevin Smith wrote:
On Wed, Jan 11, 2012 at 4:06 PM, Sergey Dobrov bin...@jrudevels.org wrote:
At least, it has no real disadvantages except of this one which, I
agree, is important. But I will ask again, what can I do except of
invent YAX?
Perhaps it would be helpful
On 01/12/2012 12:54 AM, Stephen Pendleton wrote:
-Original Message-
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org] On
Behalf Of Sergey Dobrov
Sent: Wednesday, January 11, 2012 11:48 AM
To: standards@xmpp.org
Subject: Re: [Standards] PEP and PubSub
(Arrows
On 01/12/2012 01:41 AM, Kim Alvefur wrote:
On Tue, 2012-01-10 at 17:33 +0700, Sergey Dobrov wrote:
Matt Wild's upcoming archiving spec is a good candidate for this.
/K
Where I can take a look on it?
Here: http://matthewwild.co.uk/uploads/message-archive-management.html
I've read
not? That's really unclear with the current XEP.
The second thing is: maybe we should to remove the requirement to
support both socks5 and ibb? Because it's not carried out de-facto by
several implementations and not each platform can easily implement both
bytestreams.
--
With best regards,
Sergey Dobrov
On 01/12/2012 03:39 PM, Dave Cridland wrote:
On Thu Jan 12 08:09:23 2012, Sergey Dobrov wrote:
2) Filter by xpath and maybe regex.
I am highly averse to anything that requires xpath or regex on the server.
Both are big chunks of code, and regex for sure has unbounded execution
time
On 01/12/2012 03:57 PM, Marcus Lundblad wrote:
tor 2012-01-12 klockan 15:47 +0700 skrev Sergey Dobrov:
Hello, I am reading the XEP-96 and see in the requirements section:
Enable seamless file transfer, including fall-back mechanisms as
appropriate, then I see that socks5 and IBB are must
.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
On 01/12/2012 09:43 PM, Matthew Miller wrote:
On Jan 12, 2012, at 02:56, Sergey Dobrov wrote:
On 01/12/2012 03:57 PM, Marcus Lundblad wrote:
tor 2012-01-12 klockan 15:47 +0700 skrev Sergey Dobrov:
Hello, I am reading the XEP-96 and see in the requirements section:
Enable seamless file
On 01/12/2012 08:57 PM, Kim Alvefur wrote:
On Thu, 2012-01-12 at 15:09 +0700, Sergey Dobrov wrote:
Then, I understand that the XEP will be useful for current Pubsub but
it will not be useful for current PEP because filtering on a sender
side will prevent these events to be archived
On 01/12/2012 10:47 PM, Dave Cridland wrote:
On Thu Jan 12 15:37:59 2012, Sergey Dobrov wrote:
On 01/12/2012 08:57 PM, Kim Alvefur wrote:
On Thu, 2012-01-12 at 15:09 +0700, Sergey Dobrov wrote:
Then, I understand that the XEP will be useful for current Pubsub but
it will not be useful
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
changed the item id. Then it will be possible to do serial items ids
also.
Do anyone know if this will be a problem for anything?
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
the one gateway
to another one.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
and not from the posted item.
Dave.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
. Unfortunately, I can't use prosody, when
it's expected to be accepted as an experimental XEP so I can ask to
implement that to ejabberd?
--
Waqas Hussain
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
with any other.
The http://xmpp.org/extensions/xep-0060.html#impl-association doesn't
reply to the question because it describes another behavior of the
attribute and not switching it on or off.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
enough.
Have a good weekend, btw. :)
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
to the specific entry in the feed by it's atom:id. Then, should we point
to the node there and not to the specific item in the node? Then we can
exclude atom:id from entries as superfluous. Have we to change Atom's
xmlns then?
Any opinions?
On 02/24/2012 08:10 PM, Sergey Dobrov wrote:
Hello,
Pubsub
On 02/28/2012 06:36 AM, Peter Saint-Andre wrote:
On 2/27/12 12:36 AM, Sergey Dobrov wrote:
The other thing here is linking: atom:link needs attributes ref and
href, but href usually points to the atom feed at all and ref points
to the specific entry in the feed by it's atom:id. Then, should we
and PEP notifications since the
last logout time of a specific resource.
Changelog: Initial published version. (psa)
Diff: N/A
URL: http://xmpp.org/extensions/xep-0312.html
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
result in
duplication within a single stream.
/K
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
which seems to work well too.
But I don't sure if my decisions are right and suitable for anyone.
Could you hint me what have I to do in such situations?
On 02/29/2012 02:29 AM, Peter Saint-Andre wrote:
On 2/28/12 1:56 AM, Sergey Dobrov wrote:
On 02/28/2012 06:36 AM, Peter Saint-Andre wrote:
On 2
URL: http://xmpp.org/extensions/xep-0312.html
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
URL: http://xmpp.org/extensions/xep-0312.html
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
of pubsub
(and not presence) subscription.
And again the XEP will have problems with from/to subscription states..
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
or they will not be able to be the high-grade and then the
situation will lead to PEP reinvention if many protocols will depend on
that PEP's issue.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
On 03/15/2012 09:06 AM, Joe Hildebrand wrote:
On 3/14/12 10:42 AM, Sergey Dobrov bin...@jrudevels.org wrote:
Please make sure you've seen the contacts portion of XEP-292 as well:
http://xmpp.org/extensions/xep-0292.html#contacts
This part is about storing a list of contacts for *myself
On 03/15/2012 06:30 AM, Peter Saint-Andre wrote:
On 3/14/12 10:42 AM, Sergey Dobrov wrote:
On 03/14/2012 09:28 PM, Joe Hildebrand wrote:
It could be used by non-PEP pubsub, by, for example, sending an ago stanza
in your subscribe, or by translating it into a subscription option.
Yeah, I
with SRTP support, I will be grateful.
Anyone interested in the project is welcomed for the discussion.
--
With best regards,
Sergey Dobrov,
XMPP Developer and JRuDevels.org founder.
On 05/15/2012 07:30 PM, Sergey Dobrov wrote:
Hello,
I am trying to implement Jingle in my habahaba project
(http://habahaba.im/) and trying to find another Jingle implementation
to test with and see that the situation with them is awful.
To establish a connection, WebRTC requires to use
On 05/23/2012 12:55 AM, Peter Saint-Andre wrote:
On 5/22/12 11:56 AM, XMPP Extensions Editor wrote:
Version 0.6 of XEP-0277 (Microblogging over XMPP) has been released.
Abstract: This specification defines a method for microblogging over XMPP.
Changelog: Added node configuration suggestions;
in the XEP. (The feature consisted in just addition of a link to a post).
Jaussoin Timothée
2012/5/22 Peter Saint-Andre stpe...@stpeter.im mailto:stpe...@stpeter.im
On 5/22/12 12:40 PM, Sergey Dobrov wrote:
On 05/23/2012 12:55 AM, Peter Saint-Andre wrote:
On 5/22/12 11:56 AM, XMPP
1 - 100 of 205 matches
Mail list logo
