Øâ¯ã˜â§ã™â€ Ù„ã™ë†ã˜â¯ Øâ³ã˜â±ã›å’ã˜â§ã™â€ž Once and Again 2002
Friday, September 20, 2002 Stock-still: File-uploading for Web log*Spot Plus sites on Pro for Mozilla/Netscape 7.
one:04 PM
Th, September nineteen, 2002
Something just went horribly, horribly wrong. Simply it's all better at present! 1 thousand apologies.
2:29 PM
Lord's day, September xv, 2002
2d postponement of Web log*Spot work: I'm sorry to report that the scheduled Web log*Spot maintenance for today is postponed again. We had a serious hardware failure in another area of the organization related to publishing and are working instead to right that state of affairs. I'll leave an updated condition hither in the near futurity.
10:01 AM
Fri, September 13, 2002
Howdy, again. Blog*Spot maintenance is at present scheduled for Sunday 12:00 p.m. Pacific (3:00 p.chiliad. Eastern) to 3:00 p.k. Pacific (6:00 p.m. Eastern). This is typically the quietest solar day for Blog*Spot and, as originally stated, every endeavor will exist made to minimize the reanimation every bit much equally possible. Thank you very much for your patience, and we hope that you will run across an improvement in Web log*Spot operation and reliability as a result of this work.
5:38 PM
Thursday, September 12, 2002
I promise at that place is not too much thwarting in hearing that Weblog*Spot maintenance has been postponed.
Later getting into the cage it became apparent that the job requires some more complicated work on the file server than we had predictable, including the physical removal of it from the rack. In the interests of minimizing downtime, this will be rescheduled presently when information technology can exist finished as efficiently equally possible. Apologies for whatsoever inconvenience, and I'll post the new maintenance target every bit presently as it is set.
eight:16 PM
Some Pro users were having troubles publishing via FTP. I've just corrected this.
In bigger news, there were a few people who've continuously had troubles with pro2, I've updated the lawmaking on pro2 to fix this. It required rewriting page generation then if anybody notices whatever strange spacing issues, please experience free to let me or the back up site know.
12:34 PM
Wed, September 11, 2002
Important maintenance on the Blog*Spot file server is scheduled for tomorrow evening, 12 September 2002, from ix:00 p.m. to 12:00 p.m. Pacific Time (midnight to iii:00 a.m. Eastern). During this time Blog*Spot blogs will exist unavailable. Please exist assured that every attempt will exist fabricated to minimize this maintenance time as much as possible.
10:35 AM
Fri, August 09, 2002
How we're spending our time at Pyra
The original charter of this blog, as explained over there on the right, was to tell non only almost known issues, outages, etc., but also what we're working on with Blogger. That's an important thing that I believe in doingâ€"and would capeesh at a customer/userâ€"but in the twenty-four hours-to-day stress, gets knocked down on the priority list. So, here'due south an update:
Sometime later on this month, the first public, large-scale, non-Pyra-run installation of Blogger will go alive. It's a unique partnership/licensing deal that we've been working on for a few months. It won't have a direct effect on the Blogger usage of most people reading this. Withal, information technology'southward important for a few reasons: To implement this bargain, we take finally finished the long-in-the-works upgrade to an entirely new codebase (no more ASP). You encounter, a huge bottleneck for the last year-and-a-half when it comes to fixing bugs and calculation features is that much of the code nosotros take in production currently we knew nosotros needed to move away from in order to go where we wanted to go. Then at that place accept been a lot of quick fixes or band-aid approaches or don't-know-how-solve problems because we tin can't invest in the code and get new stuff written at the same fourth dimension. That, and much of the current code was just sucky and when nosotros started writing it, we of course didn't have nearly as articulate a picture of how it should piece of work as we at present practise.
And then, we've got an all-new and improved base of operations on which we want to actually invest (and that was written by people currently working for the company). That's huge. And information technology'due south being thoroughly tested correct at present (as I write this, in fact) past the QA (quality assurance) department of a big company who is non going to be easy on us about things breaking.
The next task, of course, is to motion this code into production on blogger.com. Parts of it already are. The new publishing engine in Pro, for case, is related to that. There are currently some issues with it, which we're figuring out, just it's in general much faster and better. And, importantly, it clears the style for some bitchin' new features and improvements. Just the chief transition of the interface (both complimentary and Pro) and everything will get-go happening within a couple weeks. This won't be painless. Replacing a organization that tens of thousands of people, with all kinds of unlike client and server-side configurations cannot exist painless. But we'll try to go far as shine every bit possible (and since things aren't exactly error-complimentary right now, information technology'll probably exist an improvement no matter what). Also, the database, backside everything, will stay the same, and then we can accept concurrent versions running at the same time.
In the infrastructure realm, we're continuing to make upgrades that perhaps aren't very noticeable, merely are, all the same, a big comeback. Our organization ambassador (yes, nosotros have a dedicated arrangement administrator nowâ€"let'southward here information technology for Rudy!) has been kicking some ass in making things more than reliable and faster. Reliability and operation, of class, have never been our strong point. And Rudy didn't take an piece of cake task coming in, just things have been getting amend. And because that nosotros're treatment an every increasing load (about 1,800 new user sign ups a day right), and he's had near no budget, that'south pretty good.
One of the things Rudy did recently, for instance, was move Blog*Spot to some new servers, which are now redundant and handling the load much more meliorate. Though information technology'south not equally complicated as Blogger, Blog*Spot is an increasingly big percentage of our traffic, and the one server it was on was definitely at its limit (or beyond on some days). Not merely is information technology more reliable now, the new setup allows united states of america to add more servers as needed.
What else? Well, speaking of infrastructure, something that plays a major role in determining all of this, of course, is the visitor infrastructure. Besides Rudy and myself, at that place are currently four other people spending almost or all of their work time on Pyra stuff. With the customer service person nosotros're about to hire, it'll be five. And there are a couple other developers working on projects for us on the side.
Except for the couple other developers, who don't become paid at all (even so), the thing that's paying all these people, more or less (in some cases, way less ;), is the revenue from Blogger Pro, Advert-Free Web log*Spot and pyRads (in that orderâ€"by a long ways). Plus the licensing deal I mentioned above, which will exist a significant, but non huge part of our income this year. And that's the style nosotros similar it. Jason and I have adamant that we definitely want to focus on tools and services adult for and paid for by finish users. Information technology's the nearly fun, to the lowest degree frustrating, most scalable manner to exercise absurd stuff when y'all're company as tiny similar ours (that doesn't ever want to be quite so tiny).
Anyway, that's a rant for some other time. The point is, nosotros're making progress. Sometimes I recollect nosotros're not, but we are. Sometimes I'grand banging my head against the wall wondering how we're e'er going to get done the things nosotros need to (let alone want to) get done. But then I remember that at the get-go of this year, I was the merely one in the whole company, and nosotros had virtually no revenue. And I wasn't having much fun. And then I recollect, yep, things ever take longer than you lot recollect. Simply we're making progress.
And then our plan, if you lot were wondering our plan, is to improve our electric current stuff and build more useful services and tools that you will like and some of which you'll pay for. We hope. Nosotros're pretty confident, actually, that enough people will.
And thanks for your support. And I don't hateful that in a Bartles & Jaymes sort of way. Because those guys weren't real. Just I am thirsty...
1:38 PM
![[b] - go to www.blogger.com](https://kalateh.blogspot.com/status.blogger/theb175.gif) |
| |
| about |
| |
| The purpose of this site to proceed Blogger users informed of what'south upwards with Blogger servers, development, upgrades, outages, etc. It will offer more detail about what we're working on, problems that exist, what'south beingness washed virtually them, etc. than the home page. And it'south hosted on a completely separate server, separate facitily, opposite side of the country as the main Blogger servers. Then it's always the place to go, even if Blogger is completely unreachable. |
| |
| links |
| |
| www.blogger.com Blogger Pro Blogger API Blog*Spot bloggerDev Group |
| |
Source: https://kalateh.blogspot.com/
0 Response to "Øâ¯ã˜â§ã™â€ Ù„ã™ë†ã˜â¯ Øâ³ã˜â±ã›å’ã˜â§ã™â€ž Once and Again 2002"
Post a Comment