O grupo no qual você está postando é um grupo da Usenet. As mensagens postadas neste grupo farão com que o seu e-mail fique visível para qualquer pessoa na internet.
Eric Grange wrote: > > A news site also implies corporate endorsement. Blogs are never > > official company communication.
> Indeed. hint hint
If you think for a moment that the Borland corporate office is going to start running daily press releases on technical topics, dream on. Press releases are reserved for financial information disclosure as required by federal regulations. Reuters and BusinessWeek newswire services absolutely do not want companies spamming their inboxes with technical garbage. It doesn't matter how insanely wonderful the technical content is, the non-technical audience of the press release doesn't care and doesn't want it.
> But my point is that were the average joe to look for news or word > of mouth about D9, and luckily enough get to your page via google, > you wouldn't (as "Danny Thorpe") be rated much higher than "John > Smith" (because unknown).
Try a google search on "delphi compiler". Can't get much higher than #1. ;> I'm still working on getting dcc into the top ten for "delphi language" and "delphi programming".
> And were he to go look on BDN, he wouldn't find anything, [..]
> JK mentionned placing blog links on BDN, that would certainly help,
BDN is a side branch off the Borland corporate root. For the few people who don't automatically start with a search engine, they will most likely start with the Borland corporate web site (www.borland.com). They then have to discover BDN through a navigation bar link, and then further discover the blog list through a navigation link on BDN, and then figure out which of the dozens or hundreds of blogs listed that they should look at. So, no matter how you slice it, if you're not using a search engine, you've got a bit of digging to do.
So while I agree that having a list of blogs available on BDN would help the visibility of those bloggers, I don't think it will be an enormous help to arbitrary viewers who aren't really sure what to ask for.
> but then, it might be preferable to have distinction between personal > and technical blogs/posts (I've noticed in a purely non-scientifical > study that the more off-topic and personal blogs get, the more posts > and replies they tend to produce...).
That could be read as meaning that only the blogs that stoop to sensationalism and personal attacks get as much attention as the newsgroups, where much of the same is found. ;>
I would never host a personal blog on an employer's web site, even if I were self employed. Business and career are separate from personal life.
> Reuters and BusinessWeek newswire services absolutely do not want > companies spamming their inboxes with technical garbage.
Don't know about BusinessWeek, but Reuters is quite happily maintaining technical section and publishing MS, Oracle or Apple technical news (latest I remember). Even read a VS.Net article on Reuters a few months ago.
> It doesn't matter how insanely wonderful the technical content is,
> the non-technical audience of the press release doesn't care and > doesn't want it.
That may qualify for BusinessWeek or NewsWeek, but Reuters is a general news agency, I know for a fact that Scientific American gets some of their short news from them ;)
> Try a google search on "delphi compiler". Can't get much higher than > #1. ;> I'm still working on getting dcc into the top ten for "delphi > language" and "delphi programming".
Hehe, I know, and you're also one of the few whose name entered in google refers to the 'good' Danny Thorpe (even though there is an obscure Greenwich councilor stalking spot 10), but would someone interested in the future of Delphi enter 'Delphi compiler' instead of 'Delphi news' or 'Delphi future'? For 'delphi news' f.i., first link is dead since 1999, 2nd & 3rd are a german site that resulted in a 404 here, 4th is a Borland page where eBay and Delphi 7 release are latest news...
> BDN is a side branch off the Borland corporate root. [...]
> So, no matter how you slice it, if you're not using a search > engine, you've got a bit of digging to do.
That's just a presentation issue. I have much less trouble finding relevant info on MSDN. Just requires to arrange links and topics in a meaningful and useful fashion.
> That could be read as meaning that only the blogs that stoop to > sensationalism and personal attacks get as much attention as the > newsgroups, where much of the same is found. ;>
Danny Thorpe wrote: > It's a blog about the Delphi compiler and products which could > be contributed to by other people besides me, and hopefully will be > after I'm gone.
Hopefully you won't be gone anytime soon. While Borland could probably handle it ( although they never could replace you) I don't think the community could handle another person leaving Borland.
Don't hint at things like that.
-- -Jim McKeeth "Anything is possible with enough programmers, time and pizza!" (Substitute caffeine for time as necessary.) http://www.bsdg.org/ and http://www.mckeeth.org/
Captain Jake wrote: > Well, NNTP is limited in this respect only because of the bigotry of > old fogies from the Unix days that insist on using 1950's technology > instead of allowing HTML and using newsreaders that can actually > display HTML. The answer to this problem is for people to simply > start using HTML in newsgroups enough that the troglodytes have to > join the modern world.
I couldn't agree more. I've been saying this for years...
Colin Wilson wrote: > I couldn't agree more. I've been saying this for years...
I'm very interested in this topic. Personally, I'm very much in favour of keeping newsgroups 'text only'. Here's why:
1. It speeds download times for readers.
2. It reduces storage space requirements on servers (Using HTML requires many more bytes to say the same thing)
3. Searching an off-line message store becomes harder / slower (if only because the database has got much larger whilst the word content remains the same as if it were text only).
Now, all that said, I'm very much up for being convinced of the need for HTML if anyone wants to engage the debate?
-- Derek Davidson http://www.enterpriseblue.com For the world's EASIEST Help Desk software Now Verified for Microsoft Windows Server 2003
> > I couldn't agree more. I've been saying this for years...
> I'm very interested in this topic. Personally, I'm very much in favour > of keeping newsgroups 'text only'. Here's why:
> 1. It speeds download times for readers.
That depends on how much markup a person puts in their post.
But this argument is kind of a non-starter anyway, because text is probably the LEAST efficient way to transmit anything other than raw text. Most of the newsgroup bandwidth on servers is used on transfers of binary files translated into text via Base64 encoding, not on text messages. Base64 encoding increases the bandwidth required relative to a simple binary transfer.
Also, with broadband the time required to download the typical text or HTML message is negligible.
> 2. It reduces storage space requirements on servers (Using HTML > requires many more bytes to say the same thing)
As I stated above, binaries take up most of the space on usenet news servers and they are stored in a manner that actually increases their bulk rather than compressing it.
> 3. Searching an off-line message store becomes harder / slower (if only > because the database has got much larger whilst the word content > remains the same as if it were text only).
With apologies to Colin and other authors of n ewsreaders that store their messages in a text file, I very strongly think that newsreaders ought to store their messages in an encrypted form so that viruses can not read them for email addresses and URL's. I repeat: newsreaders should not store messages in a readable form. In any event the search argument is a non-starter because any good search engine will simply strip out extraneous characters like markup, punctuation, etc anyway.
If people really were concerned about bandwidth waste, they would chuck the current NNTP standard in the trash anyway. It is very wasteful to require everything to be expressed in text. Nowadays when you attach an attachment to an newsgroup message it gets bulked up by roughly 33% if not more. What would really be needed to reduce bandwidth requirements would be compressed HTML for text, and compressed binary transfers for attachments. But that violates the sacrosanct RFC 877.
Everything contained in this post that is not quoted from others, is merely an opinion. It may be a well-informed opinion motivated by an uncanny grasp of facts and amazingly well-formulated theories, but it remains opinion nevertheless. I speak for nobody but myself, and even then I may get it wrong from time to time.
Captain Jake wrote: > Well, NNTP is limited in this respect only because of the bigotry > of old fogies from the Unix days that insist on using 1950's > technology instead of allowing HTML and using newsreaders that > can actually display HTML. The answer to this problem is for > people to simply start using HTML in newsgroups enough that the > troglodytes have to join the modern world.
Reading what you & Colin have said about HTML - the security holes in HTML scare me, especially since everybody and their mother seems to use the IE html renderer to display those posts. Now, if Delphi shipped with TffBrowser (TFireFoxBrowser) or something, I'd be a *little* more inclined to display posts as HTML, but even there it just feels like playing a waiting game until the next auto-execute exploit is discovered.
> Reading what you & Colin have said about HTML - the security holes > in HTML scare me, especially since everybody and their mother seems > to use the IE html renderer to display those posts. Now, if Delphi > shipped with TffBrowser (TFireFoxBrowser) or something, I'd be a > *little* more inclined to display posts as HTML, but even there it > just feels like playing a waiting game until the next auto-execute > exploit is discovered.
It doesn't require a full browser just to render HTML. See Dave Baldwin's THTMLViewer and the JVCL for a couple of examples.
The above components can lessen the security risks that IE (and FF for that matter) persent when used with mail (and NNTP postings). The security problems stem from the browser implementations, not the HTML markup.
Don't misunderstand me... I dislike HTML in mail (and I'm sure I'd hate it in NNTP too). It's the HTML bloat factor that I dislike.
> Reading what you & Colin have said about HTML - the security holes > in HTML scare me, especially since everybody and their mother seems > to use the IE html renderer to display those posts. Now, if Delphi > shipped with TffBrowser (TFireFoxBrowser) or something, I'd be a > *little* more inclined to display posts as HTML, but even there it > just feels like playing a waiting game until the next auto-execute > exploit is discovered.
I don't intend to use IE as the HTML renderer in my newsreader when I add the ability to read HTML messages. I think that using IE to render HTML is very irresponsible, TBH. My plan is to use something like the HTML from pBear.
Everything contained in this post that is not quoted from others, is merely an opinion. It may be a well-informed opinion motivated by an uncanny grasp of facts and amazingly well-formulated theories, but it remains opinion nevertheless. I speak for nobody but myself, and even then I may get it wrong from time to time.
Everything contained in this post that is not quoted from others, is merely an opinion. It may be a well-informed opinion motivated by an uncanny grasp of facts and amazingly well-formulated theories, but it remains opinion nevertheless. I speak for nobody but myself, and even then I may get it wrong from time to time.
Captain Jake wrote: > "Marco Caspers" <hexorha...@vaxor.com> wrote in message > news:41361e1c$1@newsgroups.borland.com... > > 5. Text only is not vulnerable for the viri, spyware and other > > baddies that can be hidden in HTML files.
> This is not true. MIME attachments are text only, not HTML, and they > can easily contain viruses, spyware, etc.
Yes and no. A MIME attachment can contain a virus, yes. But you'd have to open it for anything bad to happen. An HTML message can exploit browser vulnerabilities to remove that need. As OE is still the most popular newsreader, AFAICS, there's a real risk here -- and XanaNews is no better in this regard.
> Yes and no. A MIME attachment can contain a virus, yes. But you'd > have to open it for anything bad to happen. An HTML message can > exploit browser vulnerabilities to remove that need. As OE is still > the most popular newsreader, AFAICS, there's a real risk here -- and > XanaNews is no better in this regard.
You can turn off the display of HTML message previews in OE.
As for Xananews, this vulnerability exists only because Xananews uses IE to display HTML. There's no reason why Colin could not rewrite this part of Xananews to use something else, like pBear's HTML renderer.
Everything contained in this post that is not quoted from others, is merely an opinion. It may be a well-informed opinion motivated by an uncanny grasp of facts and amazingly well-formulated theories, but it remains opinion nevertheless. I speak for nobody but myself, and even then I may get it wrong from time to time.
Captain Jake wrote: > You can turn off the display of HTML message previews in OE.
You can turn this off in XanaNews, too. But if your solution to the problems with HTML is to have people not use it, what is the point of advocating it?
Craig Stuntz [TeamB] wrote: > You can turn this off in XanaNews, too. But if your solution to > the problems with HTML is to have people not use it, what is the > point of advocating it?
I think Jake's solution is to avoid using the IE HTML renderer (which is unfortunately the default Delphi TWebBrowser control too).
Something which can display HTML but not integrate with the shell as much should, in theory, be safe?
Captain Jake wrote: > You can turn off the display of HTML message previews in OE.
... and in XanaNews!
> As for Xananews, this vulnerability exists only because Xananews uses > IE to display HTML. There's no reason why Colin could not rewrite > this part of Xananews to use something else, like pBear's HTML > renderer.
At the moment, XanaNews disables scripting, java and downloading ActiveX controls when it displays HTML messages. I should probably make it disable running ActiveX controls too.
|
