16h25 CST
Pages for plugins load and interface processes steps to upload new releases
without generating errors, but procedure completes without adding a new release
to the page.
Tried twice with several refreshes.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post
21h35 CST --
@sourceforge -- "The sourceforge.net website is temporarily in static offline
mode."
Twitter: "SourceForge is experiencing issues. We are investigating."
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
Christian J. Robinson wrote:
> On Sun, 25 Feb 2018, Logan Abbott wrote:
>
> > We're currently responding to a DDOS that's unrelated to the recent
> > issues.
>
> Is this related to OpenDNS blocking www.vim.org due to a security
> threat? See this image:
>
> https://www.dropbox.com/s/n5hj6fua
On Sun, 25 Feb 2018, Logan Abbott wrote:
We're currently responding to a DDOS that's unrelated to the recent
issues.
Is this related to OpenDNS blocking www.vim.org due to a security
threat? See this image:
https://www.dropbox.com/s/n5hj6fua8e6rmrl/Firefox_Screenshot_2018-02-25T20-51-29.203
On Sun, 25 Feb 2018, Manuel Ortega wrote:
In fact, it makes it even worse.
I don't think it's fair to blame SourceForge for something that is
truly out of their control, no matter how many faults they have had in
the past.
That said, if I'm being truly honest I am very wary of SF even unde
On Sunday, February 25, 2018 at 12:31:58 PM UTC-5, Manuel Ortega wrote:
> > We're currently responding to a DDOS that's unrelated to the recent issues.
> > I also don't even own a suit.
>
> It's one thing after another. The fact that the later thing is unrelated to
> the previous thing is no co
> We're currently responding to a DDOS that's unrelated to the recent issues. I
> also don't even own a suit.
It's one thing after another. The fact that the later thing is unrelated to
the previous thing is no comfort, when there keeps on being later things. In
fact, it makes it even worse.
On Sunday, February 25, 2018 at 11:32:48 AM UTC-5, Manuel Ortega wrote:
> The vim website has been unreachable again, all morning. I can't look in the
> scripts section for a syntax file I need.
>
> I was looking forward to a change of provider. Is Vim really staying with
> sourceforge just be
The vim website has been unreachable again, all morning. I can't look in the
scripts section for a syntax file I need.
I was looking forward to a change of provider. Is Vim really staying with
sourceforge just because one of their suits said "pretty please"?
-Manny
--
--
You received this
Logan Abbott wrote:
> > > Logan Abbott, president of SourceForge here. I am sincerely sorry
> > > about hosting and other services being down this week. We ran into a
> > > good deal of unforeseen issues with the new datacenter migration. Most
> > > services are restored now, and we're working on
* François Ingelrest [180222 01:39]:
> For some reason, the person in charge of the DNS (I don't think it's
> Bram) is kind of old-school and dogmatic, and has decided that vim.org
> is the domain name and not the address of the website. While true,
> this was and is still a ridiculous justificati
On 22 February 2018 at 03:55, Christian J. Robinson wrote:
> _Please_ make it possible to use http://vim.org, even if it just
> automatically redirects to http://www.vim.org. Your own reply here shows
> why it's needed.
It's been asked again and again for years, e.g.,
https://groups.google.com/d/
On Wednesday, February 21, 2018 at 9:55:56 PM UTC-5, Heptite wrote:
> On Wed, 21 Feb 2018, Logan Abbott wrote:
>
> > As of a couple hours ago, we've fixed the problems that were causing
> > performance issues on vim.org.
>
> _Please_ make it possible to use http://vim.org, even if it just
> aut
On Wed, 21 Feb 2018, Logan Abbott wrote:
As of a couple hours ago, we've fixed the problems that were causing
performance issues on vim.org.
_Please_ make it possible to use http://vim.org, even if it just
automatically redirects to http://www.vim.org. Your own reply here
shows why it's nee
On Tuesday, February 20, 2018 at 1:28:58 PM UTC-5, Bram Moolenaar wrote:
> Logan -
>
> > Logan Abbott, president of SourceForge here. I am sincerely sorry
> > about hosting and other services being down this week. We ran into a
> > good deal of unforeseen issues with the new datacenter migration.
Logan -
> Logan Abbott, president of SourceForge here. I am sincerely sorry
> about hosting and other services being down this week. We ran into a
> good deal of unforeseen issues with the new datacenter migration. Most
> services are restored now, and we're working on getting web hosting up
> to
Also, maybe we could add a DNS entry for vim.org ? Today only *www*.vim.org
works, and I've already seen several people mistakenly using URLs starting
with https://vim.org.
Unless of course there's a reason not too, I think it would be a nice
change.
Cheers,
Dimitri
--
--
You received this me
The Vim homepage is indeed back online at both http://www.vim.org/ and
https://vim.sourceforge.io/ (with the same content).
I have no experience with osdn.net, and I trust Bram's enlightened
choice (one, but only one, of the possible options, being of course
the status quo).
Best regards,
Tony.
On Friday, February 16, 2018 at 10:50:53 AM UTC-5, Bram Moolenaar wrote:
> The recent (and ongoing) outage of the Vim website on SourceForge shows
> again that this is not a good place to host Vim.
>
> I have an offer to move to osdn.net, which should provide us with a
> similar service, but bette
On Fr, 16 Feb 2018, Bram Moolenaar wrote:
>
> The recent (and ongoing) outage of the Vim website on SourceForge shows
> again that this is not a good place to host Vim.
>
> I have an offer to move to osdn.net, which should provide us with a
> similar service, but better. It should then also be
George Reilly wrote:
> On Fri, Feb 16, 2018 at 11:17 AM, Christian J. Robinson
> wrote:
>
> > On Fri, 16 Feb 2018, Bram Moolenaar wrote:
> >
> > The recent (and ongoing) outage of the Vim website on SourceForge shows
> >> again that this is not a good place to host Vim.
> >>
> >
> > [...]
> >
>
On Fri, Feb 16, 2018 at 11:17 AM, Christian J. Robinson
wrote:
> On Fri, 16 Feb 2018, Bram Moolenaar wrote:
>
> The recent (and ongoing) outage of the Vim website on SourceForge shows
>> again that this is not a good place to host Vim.
>>
>
> [...]
>
> If you have positive or negative comments ab
On Fri, 16 Feb 2018, Bram Moolenaar wrote:
The recent (and ongoing) outage of the Vim website on SourceForge
shows again that this is not a good place to host Vim.
[...]
If you have positive or negative comments about moving to osdn.net,
let's discuss that.
I think this move is the right c
23 matches
Mail list logo
