 | | | | | | |
| |
|
Request to Todd to have this added to the implementation queue (perhaps
with a relatively lower priority)
I think having a way to cancel a message from the web (which perhaps was
reviewed by a human to verify bonafides) would be a good thing. I would
make the interface such that one could request the cancel even if one
was not set up to web post...
What I mean by that is that I'd like the ability to point to a
particular message, and submit a cancel request, along with a
certification "this message was submitted by me, although it was via
mail from my old ID that is defunct" which gets validated by a human who
passes judgement on whether it really is me the author requesting the
cancel. The standard automated way of allowing cancels only with strict
byte for byte identity matches is too restrictive as it completely
disallows cancels of web or mail originated posts.
Note that this does not veer into editorial control because it is only
honoring requests from the original author, not exercising judgement
about what should be edited or removed. The judgement merely is about
the supplied bonafides that the requestor is actually the author.
Robert Munafo wrote:
>
> Thank you for that excellent and appropriately formatted reply!
>
> I use the web interface to do everything because I'm not going to bother my
> firewall administrator with a request to set up NNTP proxy (or whatever he'd
> have to do to get it to work).
>
> - Robert Munafo
>
> In lugnet.faq, Larry Pieniazek writes:
> > [...]
> > How to cancel a message depends on how you submitted it. If you
> > submitted it via the web or mail interfaces, I believe currently there
> > is no way to cancel. If you submitted via the news interface [...]
--
Larry Pieniazek larryp@novera.com http://my.voyager.net/lar
- - - Web Application Integration! http://www.novera.com
fund Lugnet(tm): http://www.ebates.com/ Member ref: lar, 1/2 $$ to
lugnet.
NOTE: I have left CTP, effective 18 June 99, and my CTP email
will not work after then. Please switch to my Novera ID.
| | | | | | | | | | | | | | | |
| |
|
That doesn't sound secure enough. I would suggest that when a user "registers"
to use the web interface, their browser should be send a random unique "user
ID", and the user ID should also be sent to the email address they registered
with. If they cancel the message via NNTP or email, their email address serves
as their identity, and if they cancel via their web browser the cookie is their
identity -- but if they have changed their email address or lost their cookies,
they could type in the ID. So the ID verifies their identity and only has to be
used in rare cases.
On a related note, I just had to "register" again today because I am accessing
the web from a different machine, and it annoyed me that I couldn't log in to
LUGNET with a user ID and password to get my cookies reinstated.
- Robert
In lugnet.faq, Larry Pieniazek writes:
> [...] I think having a way to cancel a message from the web (which
> perhaps was reviewed by a human to verify bonafides) would be a good
> thing. I would make the interface such that one could request the cancel
> even if one was not set up to web post...
> [...]
| | | | | | | | | | | | | | | | | |
Boy, that was stupid. I really do wish I could cancel messages.
I just realized that there is a "confirmation code", which right now is used
when you request having a newsgroup sent to you via email (the page where this
happens is http://lugnet.com/news/mail/setup/ )
So I'll modify my suggestion and say, if you want to cancel a message you
should either have the confirmation code already in your browser as a cookie,
or you should be sending email from the email address that the message is
currently linked to (the email address you had when you posted the message), or
you should manually supply the confirmation code.
In lugnet.faq, Robert Munafo writes:
> That doesn't sound secure enough. I would suggest that when a user "registers"
> to use the web interface, their browser should be send a random unique "user
> ID", [...]
| | | | | | | | | | | | | | | | | |
In lugnet.faq, "Robert Munafo" <munafo@gcctech.com> writes:
> On a related note, I just had to "register" again today because I am accessing
> the web from a different machine, and it annoyed me that I couldn't log in to
> LUGNET with a user ID and password to get my cookies reinstated.
This is because there aren't any "user accounts" on the server...everything
is stored in on the client (just like a newsreader). However, with
memberships, we can store all of that neat stuff on the server and only
burden the client with a tiny ID cookie.
--Todd
| | | | | | |
