* re: LARTC.org site
@ 2018-06-16 14:04 Rich Brown
2018-09-07 22:08 ` Carl-Daniel Hailfinger
2018-09-07 23:03 ` Rich Brown
0 siblings, 2 replies; 3+ messages in thread
From: Rich Brown @ 2018-06-16 14:04 UTC (permalink / raw
To: lartc
Hi folks - two comments:
1) lartc.org seems to be off the air. It pings, but neither port 80 or port 443 accept connections.
2) About two years ago, I pulled the content from github, and re-organized and modernized it. The current version is at http://lartc.richb-hanover.com - its git repo is at https://github.com/richb-hanover/lartc-redesign I make this available to the community.
Best regards,
Rich Brown
Lyme, NH USA
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: LARTC.org site
2018-06-16 14:04 LARTC.org site Rich Brown
@ 2018-09-07 22:08 ` Carl-Daniel Hailfinger
2018-09-07 23:03 ` Rich Brown
1 sibling, 0 replies; 3+ messages in thread
From: Carl-Daniel Hailfinger @ 2018-09-07 22:08 UTC (permalink / raw
To: lartc
Hi folks,
my apologies for the late response, I had not seen this mail earlier.
On 16.06.2018 16:04, Rich Brown wrote:
> 1) lartc.org seems to be off the air. It pings, but neither port 80 or port 443 accept connections.
The hosting provider (domainfactory) of lartc.org was hacked, and the
info received from the provider was sparse at best. This seems to have
caused a script to run amok and take the whole site offline.
Thanks for alerting me. I'll try to get the site back up over the
weekend. If anyone can suggest a reliable (i.e. taking security
seriously) hosting provider in Germany, I'd appreciate an email off-list.
> 2) About two years ago, I pulled the content from github, and re-organized and modernized it. The current version is at http://lartc.richb-hanover.com - its git repo is at https://github.com/richb-hanover/lartc-redesign I make this available to the community.
The redesign looks nice. Do you have any objections if I base the
resurrected lartc.org on your work?
Best regards,
Carl-Daniel Hailfinger
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: LARTC.org site
2018-06-16 14:04 LARTC.org site Rich Brown
2018-09-07 22:08 ` Carl-Daniel Hailfinger
@ 2018-09-07 23:03 ` Rich Brown
1 sibling, 0 replies; 3+ messages in thread
From: Rich Brown @ 2018-09-07 23:03 UTC (permalink / raw
To: lartc
Hi Carl-Daniel,
I would be delighted to have you use the redesigned template as a basis for the new lartc.org site.
Feel free to pull from my repo.
Best regards,
Rich Brown
> On Sep 7, 2018, at 6:08 PM, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> wrote:
>
> Hi folks,
>
> my apologies for the late response, I had not seen this mail earlier.
>
> On 16.06.2018 16:04, Rich Brown wrote:
>> 1) lartc.org seems to be off the air. It pings, but neither port 80 or port 443 accept connections.
>
> The hosting provider (domainfactory) of lartc.org was hacked, and the
> info received from the provider was sparse at best. This seems to have
> caused a script to run amok and take the whole site offline.
>
> Thanks for alerting me. I'll try to get the site back up over the
> weekend. If anyone can suggest a reliable (i.e. taking security
> seriously) hosting provider in Germany, I'd appreciate an email off-list.
>
>
>> 2) About two years ago, I pulled the content from github, and re-organized and modernized it. The current version is at http://lartc.richb-hanover.com - its git repo is at https://github.com/richb-hanover/lartc-redesign I make this available to the community.
>
> The redesign looks nice. Do you have any objections if I base the
> resurrected lartc.org on your work?
>
>
> Best regards,
> Carl-Daniel Hailfinger
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-09-07 23:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-06-16 14:04 LARTC.org site Rich Brown
2018-09-07 22:08 ` Carl-Daniel Hailfinger
2018-09-07 23:03 ` Rich Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).