I am please to announce that MATLAB Central has a new Newsreader available for your use. This entirely new application was built and is hosted by the MathWorks, Inc. Access this application by going to MATLAB Central and clicking on Newsgroup or by going http://www.mathworks.com/matlabcentral/newsreader/.
The new newsreader has many new features including:
- Ability to filter discussion content by a variety of different time periods: all, 7 days, 30 days, last year. - Ability to track discussion threads using your own personal “watch lists” - Ability to organize threads by "tagging" with a word or phrase that are meaningful to you - Ability to select content for viewing using single or multiple tags - Ability to select content by author - Ability to set—up RSS feeds to have your site updates delivered to your desktop using your favorite RSS feed reader. - Decreased newsgroup spam (due to required login to your MathWorks Account)
Please log in in order to post or to tag. You will be prompted to add a Newsreader email address to your community profile before your first post or tag. Click on the "Post a Message" button to send a new message. If you are reading a message and want to reply, click on the "Reply to this message" link. To tag, simply enter your tags in the Tag block.
> I am please to announce that MATLAB Central has a new Newsreader > available for your use. This entirely new application was built and > is hosted by the MathWorks, Inc. Access this application by going > to MATLAB Central and clicking on Newsgroup or by going <http://www.mathworks.com/matlabcentral/newsreader/>.
> he new newsreader has many new features including:
> - Ability to filter discussion content by a variety of different > time periods: all, 7 days, 30 days, last year. > - Ability to track discussion threads using your own personal > “watch lists” > - Ability to organize threads by "tagging" with a word or phrase > that are meaningful to you > - Ability to select content for viewing using single or multiple > tags > - Ability to select content by author > - Ability to set—up RSS feeds to have your site updates > delivered to your desktop using your favorite RSS feed reader. > - Decreased newsgroup spam (due to required login to your MathWorks > Account)
> Please log in in order to post or to tag. You will be prompted to > add a Newsreader email address to your community profile before > your first post or tag. Click on the "Post a Message" button to > send a new message. If you are reading a message and want to reply, > click on the "Reply to this message" link. To tag, simply enter > your tags in the Tag block.
> Send your questions, comments or feedback to us either via the > newsgroup or to newsrea...@mathworks.com.
> See you online! > Helen Chen and the MATLAB Central Team
ok, lets try it here... i got errors when trying to reply to this message, or when trying to post a new message on the new app.
My suggestion on the new app is to try to get the subject wider. maybe wrap the date and narrow down some of the other columns so the subjects don't wrap as much. having them scrunched up like they are now makes them hard to read and means more scrolling to view the page.
One very useful feature of the new newsreader is the "flag as spam" link for posts. I think its currently set so that when 5 different readers all flag a post as spam, then that post is expunged.
So as users of the group, this allows us to help reduce the clutter. Spend a minute or so of your time to help clear up the spam.
Nice work on the functionality, Helen & team. The spam solution is a good compromise between conflicting requirements, IMHO.
However, a critically important feature of any newsreader, that was available in the old newsreader but not the new one, is the ability to obfuscate the poster's real email address, in order to prevent spam from internet email harvesters. I sign as altmany...@gmailDEL.comDEL (and others have similar methods) so that automated harvesters will not get my email, whereas human users would. Until the new newsreader enables this, I will be forced to keep using the old one for my posts.
> Can you give me more detail on what type of error you received when > posting/replying?
> Helen
it just went to a page that said 'an error has occured' and said that you have been notified... so i assume it put something in a log somewhere. my 2 attempts were within 5 or 10 minutes of the successful one through the old reader.
ok, that time it worked... i think the only difference was that i didn't check the box to add the thread to my watch list. so this time i'll check that option. all my tries have set the email me option to 'never'... personally i would prefer that to be the default.
> I can't see any of the text I'm repyling to and no obvious "quote" button. This is my first post so I wonder how it'll look.
Steve,
I've been pushing to allow quotes back in. I think they are quite important for reference. The only way to quote at this moment is to copy and paste it in. I have done that when I felt it important.
<steve said... > I can't see any of the text I'm repyling to and no obvious "quote" button. This is my first post so I wonder how it'll look. </steve>
You are right that there is no quoting functionality in the current newsreader. The design objective was to try to reduce message clutter in threads.
What you can do is, right click on the reply button and open up the reply window separately. You can easily copy and paste any piece of the original message into the new window.
Helen Chen <helen.c...@mathworks.com> wrote: >You are right that there is no quoting functionality in the current newsreader. The design objective was to try to reduce message clutter in threads.
Then someone got the wrong design objective. That design objective might perhaps be okay in something like a vBulletin forum, inherently graphical, but proper quoting is ESSENTIAL in Usenet discussions, which are asynchronous -text- entities of inconsistent delivery and inconsistent retention. If the goal was to design something for use only with messages that stay on one site, then the designers may do whatever they think will "work" for the site, but if the goal is to produce messages gatewayed to Usenet, then the quoting must be not just possible, and not just practical: it must be the default.
Google groups took tons of flack from Usenet users until it fixed quoting to be obvious and default. There were write in campaigns and people had their signature lines set for months and months to text advising readers to complain to google about the quoting.
I note, by the way, that what I quoted is all one long line, not two lines, as was the quote from the poster you were replying to. That suggests that the online reader is doing visible word wrap but that that word wrap is not being translated into newlines when the message is sent out to Usenet. The result will likely often be in technical violation of the NNTP RFCs, which place a limit (not particularily high) on the number of characters permitted per line. NNTP servers which detect longer lines are, under the RFCs, justified in rejecting the message as being technically non-conforming, just as much as if it were missing essential headers. -- If you lie to the compiler, it will get its revenge. -- Henry Spencer
> In article <f72mr7$bs...@fred.mathworks.com>, > Helen Chen <helen.c...@mathworks.com> wrote:
> >You are right that there is no quoting functionality in the current > >newsreader. The design objective was to try to reduce message clutter in > >threads.
> Then someone got the wrong design objective. That design objective > might perhaps be okay in something like a vBulletin forum, inherently > graphical, but proper quoting is ESSENTIAL in Usenet discussions, > which are asynchronous -text- entities of inconsistent delivery > and inconsistent retention. If the goal was to design something for > use only with messages that stay on one site, then the designers > may do whatever they think will "work" for the site, but if the goal > is to produce messages gatewayed to Usenet, then the quoting must be > not just possible, and not just practical: it must be the default.
[snip]
> I note, by the way, that what I quoted is all one long line, not > two lines, as was the quote from the poster you were replying to. > That suggests that the online reader is doing visible word wrap > but that that word wrap is not being translated into newlines when > the message is sent out to Usenet. The result will likely often > be in technical violation of the NNTP RFCs, which place a limit > (not particularily high) on the number of characters permitted per line. > NNTP servers which detect longer lines are, under the RFCs, > justified in rejecting the message as being technically non-conforming, > just as much as if it were missing essential headers.
I was just about to address exactly these two issues so thank you Walter for doing it for me.
I completely agree -- quoting is absolutely essential and must be the default. While we're at it, how about putting the cursor at the end of the quoted material so as to discourage top posting?
Note the way my newsreader does quoting above (I am not using the new interface).
-- Doug Schwarz dmschwarz&ieee,org Make obvious changes to get real email address.
On Wed, 11 Jul 2007 16:19:01 +0000, Doug Schwarz wrote:
> I completely agree -- quoting is absolutely essential and must be the > default. While we're at it, how about putting the cursor at the end of > the quoted material so as to discourage top posting?
Better yet, right after the 1st paragraph, to discourage bottom posting without snipping.
I just noticed that posts done using the new interface are apparently not listed on the usenet (good-ol' CSSM). If I'm right, then perhaps TMW is trying to move away from usenet and into a proprietary forum format. I'm not saying that's bad, but some users might have strong feelings about it, so FYI. In any case, if my finding is correct then I think TMW should state this clearly and openly.
Then again, I may be wrong. If so, apologies in advance.
Yair Altman wrote: > I just noticed that posts done using the new interface are apparently > not listed on the usenet (good-ol' CSSM).
Hu? I seem to receive all the posts here...
> If I'm right, then perhaps > TMW is trying to move away from usenet and into a proprietary forum > format. I'm not saying that's bad, but some users might have strong > feelings about it, so FYI.
Yep, you can bet on that. I for one wouldn't be very pleased...
and here's an example of a post that only appeared on the new app, whereas Steve Lord's answer also appeared on CSSM (I could not find the original post on CSSM, only on the new app):
Another clear example: compare the number of replies seen for this thread on the new app (22 by now) with those on Google (18) or the old app (16).
There are numerous other examples. None of my posts submitted using the new app appear on Google Groups. Maybe Google Groups started having hickups, but for some reason I doubt it... I'm posting this one on the old app, so everyone will get it...
Yair Altman wrote: > Michael Wild wrote: >> Yair Altman wrote: >>> I just noticed that posts done using the new interface >>> are apparently not listed on the usenet (good-ol' CSSM). >> Hu? I seem to receive all the posts here...
[snip ample proof]
that's really strange! some of the posts seem to appear, some don't! take this thread: some of the posts i see here in my newsreader (thunderbird) are clearly from the new app. before this post, it was 19 entries long. that's the same as google tells me. but the new app tells me there are 24 of them!
you're right, something's fishy... or rather buggy.
