--
You received this message because you are subscribed to the Privly development mailing list. To post to this list, send email to pri...@googlegroups.com. To unsubscribe from this group, send email to privly+un...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/privly?hl=en
Privly testers should also sign up for this list: https://groups.google.com/forum/#!forum/privly-test
---
You received this message because you are subscribed to the Google Groups "privly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to privly+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Yes. (2) can be modified to do that. I had that idea too. Although, say I'm chatting with you over Facebook chat or hangouts or something similar, then in an IM the privly link would go as soon as we press submit (or at least it should happen like that. We shouldn't include too much delay). There's a chance by then, our request for updating the content on the link hasn't been acknowledged yet. This would mean, perhaps the user on the other side may see an empty iframe.
This is why I wanted to send an update request every second or so.
One question. Does the iframe injected from the links update dynamically?
Say I loaded twitter and there's a privly link there which gets converted to corresponding iframe. Now, I open a new tab and open history app, and change the content for that link.
Would I need to refresh my twitter page to see the change getting reflected?
If iframe is not reloaded dynamically, then we can face the issue I'm talking about above.
Yes. (2) can be modified to do that. I had that idea too. Although, say I'm chatting with you over Facebook chat or hangouts or something similar, then in an IM the privly link would go as soon as we press submit (or at least it should happen like that. We shouldn't include too much delay). There's a chance by then, our request for updating the content on the link hasn't been acknowledged yet. This would mean, perhaps the user on the other side may see an empty iframe.
This is why I wanted to send an update request every second or so.
One question. Does the iframe injected from the links update dynamically?
Say I loaded twitter and there's a privly link there which gets converted to corresponding iframe. Now, I open a new tab and open history app, and change the content for that link.
Would I need to refresh my twitter page to see the change getting reflected?
If iframe is not reloaded dynamically, then we can face the issue I'm talking about above.
On 24 Mar 2015 22:10, "Sean McGregor" <smcg...@seanbmcgregor.com> wrote:
>
>
>
> On Tue, Mar 24, 2015 at 9:32 AM, Bhavul Gauri <bhav...@gmail.com> wrote:
>>
>> Yes. (2) can be modified to do that. I had that idea too. Although, say I'm chatting with you over Facebook chat or hangouts or something similar, then in an IM the privly link would go as soon as we press submit (or at least it should happen like that. We shouldn't include too much delay). There's a chance by then, our request for updating the content on the link hasn't been acknowledged yet. This would mean, perhaps the user on the other side may see an empty iframe.
>> This is why I wanted to send an update request every second or so.
>
> Our iframe will control when the host page's content is submitted, so it can wait for the remote content to be updated. Also, the starting content will be blank, so there is no risk of exposure.
Yes. But that would add a delay in submission.
Later on, when used a lot, privly server might be congested, and what I thought we could do is simultaneously submit the link and send a request for updating content that was captured prior to submission.
But, this also requires dynamic reloading of iframes.
I can do that as a post gsoc thing, perhaps if I get selected for this project as a student. I am studying Networks and enjoying it so far. I would like implementing the websockets thing. We'll discuss more on that later on, maybe.