 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
How do I go back and read very old threads in Thunderbird? I know I can
use the Web interface, but I prefer the news reader. Thanks.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22/07/2018 09:27, Mike Horvath wrote:
> How do I go back and read very old threads in Thunderbird? I know I can
> use the Web interface, but I prefer the news reader. Thanks.
>
>
> Mike
You could un-subscribe then when you re-subscribe you will be asked if
you want to download all the headers. Do it one group at a time or
overnight.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22-7-2018 10:27, Mike Horvath wrote:
> How do I go back and read very old threads in Thunderbird? I know I can
> use the Web interface, but I prefer the news reader. Thanks.
>
>
Have you checked your Account Settings for POV-Ray in Thunderbird? Go to
'View settings for this account' and under POV-Ray go to
'Synchronisation & Storage'. Check how you have set what has to be done
with old messages (to recover disc space). Possibly you have put a limit
there. Set to 'Don't delete any messages'. However, I think that you
need to follow Stephen's advice too nonetheless.
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22/07/2018 12:02, Thomas de Groot wrote:
> On 22-7-2018 10:27, Mike Horvath wrote:
>> How do I go back and read very old threads in Thunderbird? I know I
>> can use the Web interface, but I prefer the news reader. Thanks.
>>
>>
>
> Have you checked your Account Settings for POV-Ray in Thunderbird? Go to
> 'View settings for this account' and under POV-Ray go to
> 'Synchronisation & Storage'. Check how you have set what has to be done
> with old messages (to recover disc space). Possibly you have put a limit
> there. Set to 'Don't delete any messages'. However, I think that you
> need to follow Stephen's advice too nonetheless.
>
And backup your profile.
%APPDATA%\Thunderbird\Profiles\
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks!
Now I just need to figure out how to get TB to turn URLs that are longer
than one line into proper links.
Mike
On 7/22/2018 7:02 AM, Thomas de Groot wrote:
> On 22-7-2018 10:27, Mike Horvath wrote:
>> How do I go back and read very old threads in Thunderbird? I know I
>> can use the Web interface, but I prefer the news reader. Thanks.
>>
>>
>
> Have you checked your Account Settings for POV-Ray in Thunderbird? Go to
> 'View settings for this account' and under POV-Ray go to
> 'Synchronisation & Storage'. Check how you have set what has to be done
> with old messages (to recover disc space). Possibly you have put a limit
> there. Set to 'Don't delete any messages'. However, I think that you
> need to follow Stephen's advice too nonetheless.
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/23/2018 07:24 PM, Mike Horvath wrote:
> Thanks!
>
> Now I just need to figure out how to get TB to turn URLs that are longer
> than one line into proper links.
>
> Mike
>
Share your secret...
One of my fantasies is to get the newsgroups to emit an url for a
message that is less than 200 chars long.
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/23/2018 8:43 PM, dick balaska wrote:
> On 07/23/2018 07:24 PM, Mike Horvath wrote:
>> Thanks!
>>
>> Now I just need to figure out how to get TB to turn URLs that are longer
>> than one line into proper links.
>>
>> Mike
>>
>
> Share your secret...
>
> One of my fantasies is to get the newsgroups to emit an url for a
> message that is less than 200 chars long.
>
>
Yeah, that is an annoyance. I have to manually copy and paste those
types of URLs.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/23/2018 08:54 PM, Mike Horvath wrote:
> On 7/23/2018 8:43 PM, dick balaska wrote:
>> On 07/23/2018 07:24 PM, Mike Horvath wrote:
>>> Thanks!
>>>
>>> Now I just need to figure out how to get TB to turn URLs that are longer
>>> than one line into proper links.
>>>
>>> Mike
>>>
>>
>> Share your secret...
>>
>> One of my fantasies is to get the newsgroups to emit an url for a
>> message that is less than 200 chars long.
>>
>>
>
> Yeah, that is an annoyance. I have to manually copy and paste those
> types of URLs.
>
>
> Mike
Another weird thing about TB is most times, my new posts don't wrap. I
wondered if other people saw them like that. I assumed no. But when I
reply like this, it is wrapping while I type.
And *another* weird thing, often the povray newsgroup links work even if
the last 3-4 characters wrap. I always do the tinyurl thing to help my
fellow povers avoid the wrapping nonsense. (which is annoying because it
anonymizes the url. I'm really sending you to pornhub.)
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 04:17 schrieb dick balaska:
>>> One of my fantasies is to get the newsgroups to emit an url for a
>>> message that is less than 200 chars long.
...
> And *another* weird thing, often the povray newsgroup links work even if
> the last 3-4 characters wrap. I always do the tinyurl thing to help my
> fellow povers avoid the wrapping nonsense. (which is annoying because it
> anonymizes the url. I'm really sending you to pornhub.)
The anatomy of a link to a message in the web interface is as follows:
http://news.povray.org/<GROUP>/message/<ID>/#<ID>
where <GROUP> is the name of the newsgroup, and <ID> is the message ID
(always starting with `%3C` and ending with `%3E`, which represent the
characters `<` and `>`, respectively).
Note that the last portion of the URL is a /fragment/ (recognizable by
the leading `#`), i.e. a specific location within the referenced page,
instructing the browser to scroll down on that page accordingly.
If only the fragment portion is garbled, the web page will still load
fine; the browser will just not scroll down to the fragment because it
can't find it. (As a matter of fact, in practice that's even the
behaviour when the fragment `#<ID>` is present and intact: The
single-message pages do not have any fragments at all.)
This also means that you can strip the fragment portion from the URL
entirely to make it shorter.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/24/2018 4:38 AM, clipka wrote:
> The anatomy of a link to a message in the web interface is as follows:
>
> http://news.povray.org/<GROUP>/message/<ID>/#<ID>
>
> where <GROUP> is the name of the newsgroup, and <ID> is the message ID
> (always starting with `%3C` and ending with `%3E`, which represent the
> characters `<` and `>`, respectively).
The '<' and '>' are superfluous IMO, but it's probably not worth the
trouble of removing them.
Who is the webmaster, by the way?
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 10:46 schrieb Mike Horvath:
> On 7/24/2018 4:38 AM, clipka wrote:
>> The anatomy of a link to a message in the web interface is as follows:
>>
>> http://news.povray.org/<GROUP>/message/<ID>/#<ID>
>>
>> where <GROUP> is the name of the newsgroup, and <ID> is the message ID
>> (always starting with `%3C` and ending with `%3E`, which represent the
>> characters `<` and `>`, respectively).
>
> The '<' and '>' are superfluous IMO, but it's probably not worth the
> trouble of removing them.
Technically, the URL scheme could be shortened to
http://news.povray.org/<ID>
without loss of information, provided that the leading `%3C` and
trailing `%3E` are retained as a pattern by which to recognize message
IDs and differentiate them from other links.
Note however that any change to the URL scheme would break links posted
in existing messages, unless the old URL scheme is also retained for
compatibility.
> Who is the webmaster, by the way?
The closest thing to a webmaster we currently have would be Chris Cason.
He has full access to everything, though I'm not sure whether he'd find
the time or energy to change it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 24/07/2018 19:14, clipka wrote:
> Technically, the URL scheme could be shortened to
>
> http://news.povray.org/<ID>
>
> without loss of information, provided that the leading `%3C` and
> trailing `%3E` are retained as a pattern by which to recognize message
> IDs and differentiate them from other links.
You mean like this? http://news.povray.org/5b56ede4$1@news.povray.org
It doesn't bring up the thread, but it does at least link to the message.
> The closest thing to a webmaster we currently have would be Chris Cason.
> He has full access to everything, though I'm not sure whether he'd find
> the time or energy to change it.
I try not to touch that code too much as it's legacy (though it works
currently of course) and wasn't written by me. I do fix things from time
to time if it's important, but at some point we will have to face
changing it completely. The NNTP server we are using is a long
discontinued commercial product and I don't feel confident that it will
still work (or even be re-installable) when this server is finally
retired (the hardware is over ten years old now).
While technically I could install a new open-source NNTP server and suck
all the messages across then there's the issue of interfacing it with
the existing forum software and whether any of the features we use in
the commercial server that aren't in an OSS one matter or not. It's been
a long time since I had to tweak it.
What I'm saying basically is that when this machine eventually has to be
replaced and I replace the OS and everything with shiny new bits, it's
likely the NNTP server will not be part of it and we'll migrate
everything to some sort of standard forum software (or just keep the
existing one without the NNTP link).
If enough people feel strongly about it I would attempt to keep the NNTP
server, though.
PS I don't normally read P.O.T, just happened to be subscribed due to
the Moray question that came up recently and so did see this thread.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22/07/2018 18:27, Mike Horvath wrote:
> How do I go back and read very old threads in Thunderbird? I know I can
> use the Web interface, but I prefer the news reader. Thanks.
Note that povray.off-topic is (or was) 'special' in that when we set it
up some 20 years ago we intentionally set the article retention period
to only two weeks (from memory). It was intended to keep things fresh,
avoid using up too much storage, and pretty much replicated how most
NNTP servers worked in those days.
Sometime in the last decade or so I decided the storage issue was no
longer important (new server, more disk space ...) so changed it.
There's possibly still some limit on it but it's certainly not two weeks
like it used to be.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 11:45 schrieb Chris Cason:
> On 24/07/2018 19:14, clipka wrote:
>> Technically, the URL scheme could be shortened to
>>
>> http://news.povray.org/<ID>
>>
>> without loss of information, provided that the leading `%3C` and
>> trailing `%3E` are retained as a pattern by which to recognize message
>> IDs and differentiate them from other links.
>
> You mean like this? http://news.povray.org/5b56ede4$1@news.povray.org
>
> It doesn't bring up the thread, but it does at least link to the message.
Um... yeah... I guess ;)
Now what we need is some elegant way to /get/ that link from any given
message.
> What I'm saying basically is that when this machine eventually has to be
> replaced and I replace the OS and everything with shiny new bits, it's
> likely the NNTP server will not be part of it and we'll migrate
> everything to some sort of standard forum software (or just keep the
> existing one without the NNTP link).
You mean the web interface without newsreader access?
That would be pathologically perverse. The only advantage of the current
system over a modern(!) web-based forum system I see is the newsreader
access. (Well, that and the vast archive of existing messages.) The web
front-end of the current system is maximally crappy by today's standards.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 11:50 schrieb Chris Cason:
> On 22/07/2018 18:27, Mike Horvath wrote:
>> How do I go back and read very old threads in Thunderbird? I know I can
>> use the Web interface, but I prefer the news reader. Thanks.
>
> Note that povray.off-topic is (or was) 'special' in that when we set it
> up some 20 years ago we intentionally set the article retention period
> to only two weeks (from memory). It was intended to keep things fresh,
> avoid using up too much storage, and pretty much replicated how most
> NNTP servers worked in those days.
>
> Sometime in the last decade or so I decided the storage issue was no
> longer important (new server, more disk space ...) so changed it.
> There's possibly still some limit on it but it's certainly not two weeks
> like it used to be.
p.o.t. currently seems to have a retention period of 4 weeks, give or take.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/07/2018 01:27, clipka wrote:
> Um... yeah... I guess ;)
>
> Now what we need is some elegant way to /get/ that link from any given
> message.
From the web view, just right-click on the message ID underneath the
date and copy the link.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 17:34 schrieb Chris Cason:
> On 25/07/2018 01:27, clipka wrote:
>> Um... yeah... I guess ;)
>>
>> Now what we need is some elegant way to /get/ that link from any given
>> message.
>
> From the web view, just right-click on the message ID underneath the
> date and copy the link.
Unfortunately the message ID is only visible in the thread view, not the
single-message view.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 11:45 schrieb Chris Cason:
> You mean like this? http://news.povray.org/5b56ede4$1@news.povray.org
BTW, did you just set this up, or has it always been around?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/07/2018 01:27, clipka wrote:
>> What I'm saying basically is that when this machine eventually has to be
>> replaced and I replace the OS and everything with shiny new bits, it's
>> likely the NNTP server will not be part of it and we'll migrate
>> everything to some sort of standard forum software (or just keep the
>> existing one without the NNTP link).
>
> You mean the web interface without newsreader access?
> That would be pathologically perverse. The only advantage of the current
> system over a modern(!) web-based forum system I see is the newsreader
> access. (Well, that and the vast archive of existing messages.) The web
> front-end of the current system is maximally crappy by today's standards.
Yep, which is why my first preference was for standard forum software,
however that involves a fair bit of work if we want to preserve history
(which I definitely do).
While I could import all the old messages one way or another,
associating them with their original authors (in terms of account setup)
is a bit of a nightmare given that the NNTP interface requires no auth.
Realistically apart from messages known to be posted by those with
logins on the current web interface all the old messages would be
considered 'orphaned' and auto-assigned to dummy accounts, as modern
forum software doesn't really understand the concept of allowing random
people to post messages without accounts :-/
An alternate option is to split the forums into 'old' and 'new' and run
a process which generates a set of static HTML pages from the existing
web view just prior to shutting it down. The static pages can then serve
as a permanent, read-only archive.
While the above is probably the most logical option it's probably only
acceptable if I can ensure the new forum's search function works across
both sets of data.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/07/2018 01:45, clipka wrote:
> Am 24.07.2018 um 11:45 schrieb Chris Cason:
>> You mean like this? http://news.povray.org/5b56ede4$1@news.povray.org
>
> BTW, did you just set this up, or has it always been around?
It's been there for as long as I can remember. I'd have to check the
change history in perforce to see exactly when but it'd be at least ten
years.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/07/2018 01:43, clipka wrote:
> Unfortunately the message ID is only visible in the thread view, not the
> single-message view.
I could probably add that if it was needed.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 24.07.2018 um 11:50 schrieb Chris Cason:
> >
> > Sometime in the last decade or so I decided the storage issue was no
> > longer important (new server, more disk space ...) so changed it.
> > There's possibly still some limit on it but it's certainly not two weeks
> > like it used to be.
>
> p.o.t. currently seems to have a retention period of 4 weeks, give or take.
By that, do you mean that off-topic threads and messages disappear after 4
weeks? Using the web interface, I just pulled up a URL that I saved from
December 2017, and the off-topic thread is still there.
Or maybe I'm completely off-topic with this comment??
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 24.07.2018 um 21:40 schrieb Kenneth:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 24.07.2018 um 11:50 schrieb Chris Cason:
>
>>>
>>> Sometime in the last decade or so I decided the storage issue was no
>>> longer important (new server, more disk space ...) so changed it.
>>> There's possibly still some limit on it but it's certainly not two weeks
>>> like it used to be.
>>
>> p.o.t. currently seems to have a retention period of 4 weeks, give or take.
>
> By that, do you mean that off-topic threads and messages disappear after 4
> weeks? Using the web interface, I just pulled up a URL that I saved from
> December 2017, and the off-topic thread is still there.
Hm... oh, yeah, you're right: That's just my setting in T'bird for this
newsgroup ;)
(And it's 30 days, not 4 weeks.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> I try not to touch that code too much as it's legacy (though it works
> currently of course) and wasn't written by me. I do fix things from time
> to time if it's important, but at some point we will have to face
> changing it completely. The NNTP server we are using is a long
> discontinued commercial product and I don't feel confident that it will
> still work (or even be re-installable) when this server is finally
> retired (the hardware is over ten years old now).
Just out of curiosity, what type of machine is it running on?
You're in Australia, correct?
> What I'm saying basically is that when this machine eventually has to be
> replaced and I replace the OS and everything with shiny new bits, it's
> likely the NNTP server will not be part of it and we'll migrate
> everything to some sort of standard forum software (or just keep the
> existing one without the NNTP link).
What would you like to replace it with? What would be the cost?
Also - how is the server and the electrical cost financed?
I'm asking because we routinely get retired equipment in at work - everything
from loose memory sticks to entire server racks and all the goodies inside. I
doubt shipping to the other side of the globe is cost-effective, but maybe
something could be set up on this side of the sphere{}.
I'd certainly love to set up something more than a laptop to run something
massively CPU and memory intensive on.
Perhaps something to consider for the future is for some of the POV-Ray
development and newsgroup operating costs could be financed with paid accounts,
and access to a server / cloud for intensive supercomputer-level rendering.
8 Xeon processors and 256 GB of memory might just make that thing you've been
wanting to render for the last 5 years feasible.... ;)
Not to mention we have Mr. Balaska. {cough} #hardcorerenderjunkie {cough}
I really am just curious about the behind-the-scenes info.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/24/2018 9:21 PM, Bald Eagle wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
>
>> I try not to touch that code too much as it's legacy (though it works
>> currently of course) and wasn't written by me. I do fix things from time
>> to time if it's important, but at some point we will have to face
>> changing it completely. The NNTP server we are using is a long
>> discontinued commercial product and I don't feel confident that it will
>> still work (or even be re-installable) when this server is finally
>> retired (the hardware is over ten years old now).
>
> Just out of curiosity, what type of machine is it running on?
> You're in Australia, correct?
>
>
>> What I'm saying basically is that when this machine eventually has to be
>> replaced and I replace the OS and everything with shiny new bits, it's
>> likely the NNTP server will not be part of it and we'll migrate
>> everything to some sort of standard forum software (or just keep the
>> existing one without the NNTP link).
>
> What would you like to replace it with? What would be the cost?
> Also - how is the server and the electrical cost financed?
>
> I'm asking because we routinely get retired equipment in at work - everything
> from loose memory sticks to entire server racks and all the goodies inside. I
> doubt shipping to the other side of the globe is cost-effective, but maybe
> something could be set up on this side of the sphere{}.
> I'd certainly love to set up something more than a laptop to run something
> massively CPU and memory intensive on.
>
>
>
> Perhaps something to consider for the future is for some of the POV-Ray
> development and newsgroup operating costs could be financed with paid accounts,
> and access to a server / cloud for intensive supercomputer-level rendering.
>
> 8 Xeon processors and 256 GB of memory might just make that thing you've been
> wanting to render for the last 5 years feasible.... ;)
> Not to mention we have Mr. Balaska. {cough} #hardcorerenderjunkie {cough}
>
> I really am just curious about the behind-the-scenes info.
>
>
If he's starting over from scratch, he could set up a virtual server in
the cloud. Then he wouldn't need to worry about hardware failure. And if
someone were to take over his job, all that person would need is a login
versus the machine itself.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/24/2018 09:21 PM, Bald Eagle wrote:
>
> Just out of curiosity, what type of machine is it running on?
> You're in Australia, correct?
>
>
The machine's in Hartford CT.
I middle-manned one twenty years ago. (Chris shipped it to my house, I
bootstrapped it, he set it up from afar, I dropped it off in Hartford.)
http://www.ntplx.net/
"Andy's house" is this amazing place. A classic 1850s New England
colonial near the Mark Twain house. In the '90s, it was the most
connected building in CT and most CT traffic went through his basement.
(These days Comcast routes most traffic.)
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
