Recommended Posts

Damn lots of news today, check out my two previous posts today for more goodies.

--------

Checkin of the week! A lot of people are gonna be exited about a checkin that just happend.

A patch in Bug 291033 - Enable support for profile temp directory on local filesystem has just been checked in. This means that Mozilla Firefox is now able to store it's cache on the local filesystem. This will have a big effect on installations where the profile is stored on a network drive. Fx in organizations where Mozilla Firefox is rolled out. This will limit the amount of network trafic and make Mozilla Firefox behave faster.

The original bug 74085 - Disk cache should use local directory is one of the most commented and voted for bugs with more than 115 comments and 42 votes. The bug was opened in march 2001.

---

The Client Customization Kit (CCK) has now been revived. The CCK project aims to make it easy for organisations to customise Mozilla products to meet their needs. This includes setting certain default options, locking some preferences so they can't be changed and configuring the user interface.

---

This is also about to land,

#291910 [Core]-Provide utility for incremental download [All]

This will help will cross session resumeable downloads and is a key part for patches instead of full releases to update Firefox.

Update System

One of the biggest difficulties that the Mozilla Foundation has encountered in the months following the Firefox 1.0 release has been managing the Software Update System for distributing updates to 1.0 users. We had never done anything of this scale before, and the system in place is representative of approximately a week worth of work on my part prior to 1.0 with little understanding of the problems that the Mozilla release team would end up facing.

In this light, improving the Software Update System has become a primary objective for Firefox 1.1. We have already met several times, and there are groups now working on the various pieces of the system. Darin Fisher and I will be working on the client side segments, with help and input from Benjamin Smedberg, Doug Turner, Daniel Veditz, Chase Phillips, Chris Beard et al. I have developed some initial UI mocks which you can find on the Mozilla Wiki in the Software Update section, along with some growing but rough design documentation for the client side piece. Darin has figured out how to get binary patching working, and is working on a system for incremental background update download. I will post updates about the client side pieces as they develop further.

Source: Ben Goodger's Blog

Changes for Extension Developers

Last week I landed some important changes to the Firefox Extension management system. These changes involved almost a complete restructuring of the Extension system and offer the following benefits (briefly):

For developers: You can now have Extensions that live outside the profile and application Extensions directories. This may make development easier, because you can have your Extension source code live somewhere else, use the flat chrome packaging (instead of .jars) and place a file in the profile "extensions" folder whose name is the {GUID} of your extension that contains a path to the location of the Extension.

For users: You can install extensions by dropping their XPI into the profile or application Extensions directory.

For developers: You can install extensions by expanding the XPI into a folder whose name is the {GUID} of the extension, and drop it into the profile or application Extensions directory.

For developers: Before 1.1 (not yet, but soon) you will be able to install extensions by setting a registry key.

For users and developers: You will be able to uninstall an Extension by simply deleting its folder from the profile or application Extensions directory, or removing the text link file.

For developers: XULRunner applications will be able to specify their own special kinds of Extension install locations in addition to the profile and application directories, e.g. a special kind of registry key mapping, etc.

For developers: More comprehensive logging of installation and updating.

For users: Move Up/Move Down should now work properly.

The new architecture for tracking how Extensions are installed is much improved over the one used by Firefox 1.0 and will allow us to do many new and interesting things, make our build and release processes more efficient, make application install easier, and allow for other types of items to be more easily tracked by the Extension system.

I want to dish out thanks to Benjamin Smedberg and Darin Fisher for the excellent and prompt feedback on a 5600-lines-added-or-changed patch and helping get this checked in as quickly as possible for the Deer Park Alpha.

Source: Ben Goodger's Blog

The roadmap is not intended for public use or info on when a release will be. It is for a rough target date on when the devs should try to get things done that was decided upon months beforehand. dont worry though, only a couple more blocking bugs and then there will be a 1.1a release, should be within two weeks...depending on if they are going to release it as is after all the blocking bugs are fixed or if they are going to fix some of the regression caused by the new features.

11 bugs left blocking, 3 or more are already landed just need to tie up some things. and i think two of the bugs are just to enable the reporter tool for the release. so actually only a few bugs left blocking

Edit: Just seen this

schedule for 1.8b2 / Deer Park alpha1

We are currently planning to ship Gecko 1.8 beta 2 and Deer Park alpha 1 early next week.

We hope to be essentially done with work for these releases by Friday.

Thus, starting on Friday, drivers intend to become much more restrictive in granting trunk approval requests (and we'll also be a little more restrictive between now and then).

To nominate a bug for consideration as blocking these alpha/beta releases, please set the blocking1.8b2 flag to ?

Alright instead of bumping this thread every couple of days with new info I decided to start a blog and just post the news there. I'm asking you guys to post comments to this thread every so often to bump it to the top so that people can still see the graph and queries and other important info in the first post. Thanks

http://www.supernova00.biz/blog/ I'm still setting setting everything up and will set up the RSS/XML feeder in a few hours

EDIT: http://supernova00.biz/blog/atom.xml

Edited by supernova_00
  • 2 weeks later...

Found a broken website with firefox? Report it!

Check out my blog for more information (will post info here later just don't have enough time)

http://www.supernova00.biz/blog/

The build on my blog is a nightly!!! Please don't install unless you know what your doing

Broken Website? Report it!

You know how everyone seems to complain that some site does not work in firefox? Now you can do something about it, Report it! The tool, called "Reporter", is accessible from the Help menu and launches a simple wizard that lets you send Mozilla Foundation feedback about broken websites. It's not yet a part of the default installer, but you can enable it by doing a custom installation and checking the box in the list of available additions (with DOM Inspector and Talkback.) Once you report a site some mozilla hackers will take a look at it and see if it is broken because of non-standard coding or if it is indeed a Firefox bug.

This new tool is to report e.g.:

  • Sites Blocking Firefox Users
  • Draws the page funny
  • Causes your browser to get excessively slugish
  • Plugin Problems
  • Feature doesn't work

Download: 20050517 build NOTE: THIS IS A NIGHTLY BUILD

Edited by supernova_00

What's going on with Firefox 1.1?

I bet more than a few of you all are wondering what exactly is going on behind the scenes with the Firefox 1.1 development. Other than the new features that I post at the bottom of my "Road to Firefox 1.1" threads there have been over 1700 bug fixes since the 1.0 release and we still have a few months left with the 1.1 development cycle. Jesse Ruderman has an unofficial changelog on his site The Burning Edge. His changelog includes new features, layout fixes, memory leak fixes and whatever other important bugs have been fixed since 1.0.

next couple of days unless a security vulnerbility comes up...then all focus will turn towards fixing that. But my guess is tomorrow night for 1.1a, onyl 6 more blockers for Gecko 1.8b2 and only two are last minute changes while two other bugs are close to having patchs land. so its very very close.

As soon as these two bugs are fixed we will have 1.1a within a few hours:

Bug# 294630 - Crash when closing tab with picture [@ nsImageDocument::Destroy]

and

Bug# 281988 - Stop sharing DOM object wrappers between content and chrome

585940381[/snapback]

:D

Great news, I can't hardly wait. Although I have been using the nightly anyway, this will mean a more bug free version. Great work they are doing at Mozilla, that's for sure. Thanks supernova_00 for keeping us posted.

585937108[/snapback]

cant wait

woot woot :rofl:

What's going on with Firefox 1.1? (Part 2)

I have to new information to follow up on my last post about the Firefox 1.1 status. The Mozilla Foundation will release Firefox 1.1a beginning of next week...looks like Tuesday. Firefox 1.1a will be branded as 'Deer Park' not 'Firefox' and all the icons will be changed to a blue globe rather then the fox on the globe. This is being done to hopefully not confuse end users that this release is a final build when in fact it is a Developers Preview.

The reason for the Developers Preview is so that extension and theme developers learn what changes took place on the backend of the code, so that they have adequate time to fix any problems for the Firefox 1.1 release. Don't forget there are still new features to go into Firefox before the 1.1 release (which is still months away)...like the "drag and drop reordering of tabs".

The Mozilla Foundation has a page up now for what's new in Firefox 1.1a. See below for links.

Official 'What's New' page

Unofficial but more complete changelog

Deer Park Alpha 1 candidate builds available for testing

- We're pretty much there and have a round of builds that are very, very close to what we will ship as Deer Park Alpha 1 (what will eventually ship as Firefox 1.1)

- If you'd like to help us test these candidates, please grab one from the links below. Note that for our alpha releases, we know there are feature and polish issues that we haven't completely worked out but we want to get the core code out to our community so they can test out major Gecko and platform changes ASAP.

- The Gecko included in this candidate build is about one year of development improved since the Gecko that shipped in Firefox 1.0. We've also made major changes to the extension system. XUL application developers, extension and theme developers, and web developers are the primary audience for the upcoming Alpha.

- Oh, one other note, we've also added (thank, Robert) a new feature called "Reporter". This is a wizard for reporting broken websites. You can install this from the custom install and access it from the Help menu. Please report any broken websites you find in this candidate or the actual Alpha build using the new Reporter tool.

-These are candidate builds, not the final Deer Park Alpha 1. If these candidates test out well, we'll be shipping Deer Park Alpha 1 real soon. Also note that the naming and the artwork/branding changes are intentional, not bugs.

Linux || Mac || Windows

Edited by supernova_00
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Google Pixel 11 series: Here's what to expect by Hamid Ganji Google Pixel 10 series In recent years, Google has successfully turned its Pixel devices into worthy contenders in the smartphone market. The search giant is now preparing to launch the Pixel 11 series in just a few months, and many Pixel fans are likely wondering what Google has in store for them this year. The next lineup of Google smartphones includes four devices: the Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, and Pixel 11 Pro Fold. This year, we don’t expect Google to bring revolutionary upgrades to its handsets, and the Pixel 11 series is likely to receive modest hardware improvements alongside a slew of AI-powered features. Here are the rumored specifications of the Google Pixel 11 series ahead of its official debut: When will the new Pixel phones be unveiled? The last two generations of Google Pixel phones (Pixel 9 series and Pixel 10 series) were launched in August, unlike the previous three generations that debuted in October. With that in mind, we expect Google to unveil the Pixel 11 series sometime in August 2026. The exact launch date has yet to be confirmed. Google Pixel 11 CAD renders - Image via AndroidHeadlines How much will the Pixel 11 series cost? Predicting the final price of upcoming smartphones has become increasingly difficult. As you may know, RAM and memory prices are rising sharply, leading to significant increases in the cost of consumer electronics. Recently, Apple CEO Tim Cook said that price increases for some future Apple products are unavoidable, suggesting that the iPhone 18 series could become more expensive. Google has remained tight-lipped about any potential price increases for the Pixel 11 series. If the company manages to maintain last year’s pricing structure, here’s what the lineup could cost: Pixel 11: $799 Pixel 11 Pro: $999 Pixel 11 Pro XL: $1,199 Pixel 11 Pro Fold: $1,799 Given current market conditions, it may be difficult for Google to avoid raising prices unless it adopts cost-saving measures, such as equipping the base model with 8GB of RAM. Google Pixel 11 series anticipated specs: We expect the Google Pixel 11 series to debut with a new Tensor G6 processor as well as an upgraded camera system. The overall design, however, is expected to remain largely unchanged across the lineup. Specifications Pixel 11 Pixel 11 Pro Pixel 11 Pro XL Pixel 11 Pro Fold Display 6.3-inch LTPO AMOLED / 120Hz refresh rate / up to 3100 nits of brightness 6.3-inch Super Actua LTPO OLED, 120Hz refresh rate, up to 3600 nits of brightness 6.8-inch Super Actua LTPO OLED, 120Hz refresh rate, up to 3600 nits of brightness 8-inch inner screen and 6.4-inch outer display, 120Hz refresh rate, up to 3600 nits of brightness RAM & Processor Tensor G6 / 8-12GB of RAM Tensor G6 / 12-16GB of RAM Tensor G6 / 12-16GB of RAM Tensor G6 / 16GB of RAM Storage options 128GB or 256GB 256GB, 512GB, 1TB 256GB, 512GB, 1TB 256GB, 512GB, 1TB Camera 50MP main sensor, 13MP ultra-wide, 10.8MP 5x telephoto, 10.5MP front camera 50MP main camera, 48MP ultra-wide, 48MP telephoto with 5x optical zoom, 42MP selfie camera 50MP main camera, 48MP ultra-wide, 48MP telephoto with 5x optical zoom, 42MP selfie camera 50MP main camera, 10.5MP ultra-wide camera, 10.8MP telephoto camera, 10MP front camera, 10MP inner camera Battery 4,840 mAh 4,707 mAh 5,000 mAh 4,658 mAh Software Android 17 Android 17 Android 17 Android 17 The Pixel 11 series won’t be a major departure from its predecessor, with Google instead focusing on subtle improvements and AI additions such as Gemini Intelligence. However, a patent filed by Google suggests the company is working on a removable battery for its smartphones, and we could see this feature make its way to the Pixel 11 Pro Fold. Given that nearly all smartphones today lack removable batteries, such a feature would be a welcome addition to future Pixel devices. That said, it may not arrive with this year’s lineup after all, and the final decision is yet to be made by Google. The Pixel 11 series could also face an uphill battle in the market. In the Android segment, Samsung is performing well with the Galaxy S26 series, while the Galaxy Z Fold 8 lineup is also expected to launch next month. On the other hand, Apple is preparing to unveil the iPhone 18 Pro and iPhone 18 Pro Max in September alongside its first foldable iPhone.
    • At least AMD is still taking Windows 10 seriously (after the oops) before it consumer extended support ends. @WaltC - Memories, 2x Voodoo in SLI with a Riva TNT with an Aureal A3D soundcard.
    • So size is the ONLY selling point????? People have been plugging in PC's to TV's in living rooms for 20+ years. I would take a bigger box for more peformance. Also lot and lots of SFF/Mini ITX build guides out there.
    • My point is, if you buying this instead of a console for TV purposes, that you need to understand that you will not be able to play the most popular MP games with Steam OS. Now if you are not into those games, and into some of the perputual alpha/beta games on Steam then this is an option. I would argue a gaming PC would be the better route, more expensive but take the 1k -1.4k you are about to spend on this thing and build a better one. Because it is running Linux you can overide its 1080p settings. However The Verge complained about its 1080p cap and how you would have to get around it at the CLI, so someone buying this instead of a PS5 or Xbox might have a challege on their hands.
    • A review of Synology's BeeCamera software for the BeeStation Plus by Christopher White Synology is leaning into the BeeStation and the BeeStation Plus, and it's easy to understand why. While power users will want something more customizable, the BeeStation and its more powerful sibling, the BeeStation Plus, are great for those who want a device they can simply plug in, click a few buttons, and have it work as their own personal cloud. Until recently, the device was mostly used for the storage of files, photos, and videos, and with the Plus model, you could install and stream media through Plex. Synology recently released a new free application for the BeeStation Plus called BeeCamera, which is basically a stripped-down version of Surveillance Station. First, let's get the confusing naming out of the way. While you might initially think that BeeCamera is a physical device, perhaps a camera that Synology created specifically for the BeeStation Plus, that would be incorrect. BeeCamera is simply the name for the application that runs on the NAS and on your mobile device. I think the marketing team missed the mark here, but it does fit the other naming on the device, like BeePhotos and BeeFiles, I guess. Camera Support As of right now, only Synology-branded cameras are supported, which many will see as a callback to the drive locking the company implemented and then backtracked on. That said, while I 100% disagree on drive locking, I agree that camera locking for a device made to simply plug and play is the right decision. The whole point of the BeeStation line is simplicity. There are currently three camera model lines available, a wireless device for indoor use, and two PoE models for external use. CC400W (Wi-Fi): Plug it into power using the included power adapter, and connect it to your wireless network. This camera is rated only for indoor use and is the one I was provided to review the BeeCamera. $198.36, in line with the Unifi G6 Compact. BC510 (PoE): A bullet-style camera. Connect it to an Ethernet cable that is providing Power over Ethernet (PoE). This camera is rated for both indoor and outdoor use. $240. TC510 (PoE): A dome-style camera. Connect it to an Ethernet cable that is providing Power over Ethernet (PoE). This camera is rated for both indoor and outdoor use. $240. Although this isn't a review of the actual Synology camera, I did want to note that a positive for the Synology CC400W is that it uses a magnetic base. This means you can mount it on any magnetic surface, which is pretty handy. However, a downside to the camera is that it's powered by a built-in USB cable that's about six and a half feet (two meters) long. This means that the cable will probably be either too long or too short, but more importantly, if the cable is damaged at all, you'll likely need to buy an entirely new camera because there doesn't appear to be a way to replace it, unlike many competitors, like the Unifi G6 Instant. Hopefully, this is something Synology addresses in a future revision of the hardware. The BeeStation Plus supports up to four cameras. Setup The setup of BeeCamera is, like everything in the BeeStation family, very straightforward. Simply make sure you're on at least version 1.5 of the BeeStation OS, and BeeCamera is automatically installed on the device. BeeCamera Setup Screenshots Setting up the CC400W was just as easy. Plug it in, open up the BeeCamera app, and follow the on-screen steps to add the camera. During this process, you'll configure the camera name and how many days of retention you want to keep. The system will also automatically update the firmware for you. The whole thing took only a couple of minutes, excluding the time it took for the camera to update the firmware. Once the camera is connected to the BeeStation Plus, you can manage the various camera settings within the app, although there aren't many to choose from. You're able to configure whether the microphone will record audio (some privacy laws may preclude you from recording it), select what codec to use (H.264 or H.265), configure the color and exposure of the camera, and determine what data you want to overlay onto the video. Finally, you can set up AI detections so that BeeCamera will alert you if it sees certain things. These are all of the common detections you would expect in a camera system, such as people, pets, and vehicles. Under people and vehicles, you can also add extra monitoring for lingering and congestion detection, although pets are currently in "Lab" and therefore have no extra features yet. Recording in 4K using H.265 for 30 days will take roughly 300 GB of storage, which is very reasonable for most regular households, as the BeeStation Plus has 8TB of native storage. If you want to set up detection zones, you can. These are areas that BeeCamera will look at for the various detections, and are helpful if, for example, there's a tree in your frame and you don't want to be notified each time the wind makes the branches move around in the frame. Finally, you can also schedule when the camera should and should not be recording, which is a very useful feature. For example, you may want to record only at night when you're sleeping, but not during the day when you're up and about the house, so you can easily shut the camera off between 8 am and 10 pm. Each hour of each day can be configured to record continuously, only upon a detection event, or disabled completely. You can't fine-tune to record at a specific time, though, only hourly blocks on the hour. Daily Use The best part of BeeCamera is that it's easy and just works. If you only care about being notified when things happen, the mobile app sends those notifications and lets you click the button to bring up the video and see what's going on. For example, when I went out of town and had the camera pointed at the cat tower in our hallway, it was nice to be able to drop in and check that my furry friends were doing okay without me. Initiating the remote connection to the BeeStation Plus through the app is very responsive, but this will heavily depend on your ISP. In my case, using Xfinity, I'm able to go from starting the app to seeing live video in roughly three seconds, which is about the same amount of time it takes to connect to my Unifi UNVR system that costs much more. If you want to see footage from a specific day and time, you can do so using the calendar icon. You can also scroll through the timeline, looking for detections that are labeled in blue (vs. the normal gray when there's nothing of interest). There are buttons that let you go to the last/next detection on the timeline, which is helpful if you missed the notification on your mobile device. That's where the ease of use stops, though. While you can download clips that are flagged by detection, there's apparently no way to select generic time frames you're interested in, and the only place to download is to your phone. In addition, sharing a video shares the actual video, not just a link back to your BeeStation Plus. While that's good from a security and privacy perspective, it's a little awkward for sharing large videos. Limitations While the ease of implementation is great, there are some things that are lacking from BeeCamera. The most obvious is that there is no way to view the footage on the desktop. You can log in to the BeeStation Plus to see how much storage BeeCamera is using, but unlike BeePhotos and BeeFiles, there is no BeeCamera on the web console to manage or view footage. This means you'll be viewing all of your security footage on your mobile device, which is pretty limiting. In addition, there's no way to download the video to your PC without first using your phone as the intermediary. The one exception to this is that you can use BeeFiles to see the raw MP4 files. They're saved in 5-minute increments, and it's just raw data with no detection information or any other way to identify what any of them are. The lack of a way to interact with BeeCamera on the desktop also makes configuration of the cameras more difficult. For example, trying to set up detection zones using a tiny screen and your finger to draw boxes is more cumbersome than it needs to be. This reinforces the idea that BeeCamera is not made for power users. It's also missing some of the more advanced functionality of Surveillance Station. For example, I couldn't find a way to say, "Alert me if the thing in this zone is no longer there." Another major deficiency with BeeCamera, and a feature I suspect may come out in the future, is that while it can detect generic people, there is no specific facial recognition yet. This is an interesting omission, given the fact that other Synology tools can detect specific individuals, and competitors such as Unifi Protect also do it. This is probably a software limitation, so we will have to wait and see if this feature is added in the future. Conclusion If you need a security guard to monitor surveillance cameras to make sure your property is secure, then BeeCamera is not the solution for you. That said, you probably wouldn't be using a BeeStation Plus as the brains behind the system either. BeeCamera (and BeeStation in general) is clearly aimed at households that want to avoid sending personal data to Google and Amazon, and now want to add some cameras to keep an eye on their home and their pets while they're away. BeeCamera excels at doing this. The target market isn't interested in creating cases, tying multiple views together in a single pane of glass, or the like, and for the intended use case, the system works great. Where it starts to fall apart a bit is with more advanced features. Not being able to use a desktop app is a major compromise in my opinion, and having to do all of the configuration on a mobile device is annoying, but not impossible. If you don't want to have a full-fledged NAS device in your home, but still want control over your data (or maybe want an easy way to backup your data for World Backup Day), and want to add a couple of cameras to keep an eye on your house and your pets, this is a great, cheap, and easy way to go, and I suspect more functionality will come over time. If Synology releases a desktop app or at least a way to configure cameras and view footage on a desktop browser, this would be a near-perfect solution for a general home user. As an Amazon Associate, we earn from qualifying purchases.
  • Recent Achievements

    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      476
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      104
    4. 4
      Michael Scrip
      88
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!