Slashdot Mirror


Firefox's Web Push Notification System Announced

eldavojohn writes "Describing Notifications as 'somewhere between email and IM,' Mozilla has announced this push technology as a way to receive notifications from websites without having to keep them open in your browser — as well as receiving them on your mobile device. A JavaScript API reveals early interface ideas by the team. This core concept is not new — both Google and Apple have their own push notification systems for Android and iOS respectively. However, 'It's important to note that this push notification system is distinct from the existing desktop notification mechanisms that are already defined in pending standards. The desktop notifications that websites like GMail and Seesmic Web display to Chrome users, for example, will only work when the website is left open in a tab. Mozilla's push notification system moves beyond that limitation.' Mozilla is attempting to take push notifications to the entire web for any website to use."

132 comments

  1. WebSlices by Anonymous Coward · · Score: 5, Interesting

    Microsoft did this with WebSlices in Internet Explorer 8.

    http://msdn.microsoft.com/en-us/library/windows/desktop/cc956158%28v=vs.85%29.aspx

    As you can tell from how prominent they are, this idea really took off among web users.

    1. Re:WebSlices by Anaerin · · Score: 5, Informative

      IE may have introduced it in IE8, but Netscape (Remember them?) introduced it in 1995 in NS1.1, and it's supported in every browser except IE: http://en.wikipedia.org/wiki/Push_technology#HTTP_server_push

    2. Re:WebSlices by Anonymous Coward · · Score: 2, Informative

      You seem to have an off by one error in your IE versions.

    3. Re:WebSlices by Anonymous Coward · · Score: 0

      Do you have any more stories about history you can share with us? Perhaps one involving the Kaiser and an onion being attached to your belt, which may or may not have been the style at the time.

    4. Re:WebSlices by Anonymous Coward · · Score: 0

      A better equivalent would probably be the Java-based "NetCaster" thing which shipped with Netscape 4.0. (and was removed after a few months because it took about 5 minutes to start up)

    5. Re:WebSlices by donaggie03 · · Score: 1

      "Give me five bees for a quarter" you'd say.

      --
      Three days from now?? Thats tomorrow!! ~Peter Griffin
    6. Re:WebSlices by LocalH · · Score: 1

      IE did not support tabs until IE7.

      --
      FC Closer
    7. Re:WebSlices by Anonymous Coward · · Score: 0

      False.

    8. Re:WebSlices by Anonymous Coward · · Score: 0

      You're right. That's what I get for trusting my memory and the first result from Google. Made me think that IE 6 was released with tabs.

      http://news.cnet.com/Microsoft-offers-tabbed-browsing--in-IE-6/2100-1032_3-5738037.html

      It didn't have tabs, but MS brought tabs into it by creating a toolbar that few people probably used. IE 7 was the one that they revved up and kicked out the door flush with fancy features like tabs, to compete with upstart browsers like Firefox and Opera.

    9. Re:WebSlices by Anonymous Coward · · Score: 0

      I chased that rascal for dickety six miles.

    10. Re:WebSlices by LocalH · · Score: 1

      [citation needed]

      A stock installation of IE6 (any revision) does not support tabs. You have to install a third-party addon in order to get tabs in IE6.

      --
      FC Closer
    11. Re:WebSlices by yelvington · · Score: 1

      No. This is not HTTP server push. Has nothing to do with HTTP server push. Has nothing to do with Web Slices, either. This is more like dynamically assigned micro-mailboxes for message passing. Read the docs.

    12. Re:WebSlices by obsess5 · · Score: 1

      I used to use server-push in a custom Tcl-based web server back in the 1990s. Early versions of Opera supported server-push, but then it was dropped in later versions. Too bad because it was a nice technique at the time.

    13. Re:WebSlices by Anonymous Coward · · Score: 0

      You have to install a third-party addon in order to get tabs in IE6.

      No, you have to install a Microsoft add-on. The MSN toolbar added tabs to IE6.

  2. Interesting Concept by Anonymous Coward · · Score: 5, Insightful

    It's like we're fighting with ourselves though. "I really love these web apps, but I really wish they weren't web apps"

    1. Re:Interesting Concept by james_van · · Score: 0

      if i had seen you comment before i posted, i would have modded you up - you pretty much nailed it there

    2. Re:Interesting Concept by Anonymous Coward · · Score: 0

      You mean live silverlight?

    3. Re:Interesting Concept by Anonymous Coward · · Score: 1

      the reason people love web apps is because they don't fuck up your computer. visit 100 web apps use them all free, close your browser. Next time you open it, good as new.

      Good luck installing 100 real applications on Windows or Mac and getting anything like usability out of it.

    4. Re:Interesting Concept by aix+tom · · Score: 1

      On the other hand, the more web apps you get at the more different browsers diversify into different features, the more you get the "This web app only works on $browser from $version to $version, and that on only from $browser from $version to $version."

      We already have some of those problems with about 10 web Apps in out INTRAnet, where we have perfect control over both the server AND the web browser the users use.

      The more web Apps start to interact with each other, and the more they interact with the local data, the more that problem will happen. If any desktop app would 100% stick to the standard it would be no problem to install thousands of them. It's just the "tweaks" that cause problems. The same thing is already happening with web apps.

    5. Re:Interesting Concept by Anonymous Coward · · Score: 0

      Tried Pokki?

    6. Re:Interesting Concept by gbjbaanb · · Score: 1

      you've already got this problem with desktop apps, though not as bad as it is with current browsers (and definitely not as bad as with past browsers)

      At the moment, install a .NET app on a 100 desktops and you'll see 1 or 2 fail with errors, possibly due to a different number of updates installed, sometimes due to GAC or registry issues with other modules being/not being installed.

      My current issue is with a .NET app that doesn't run on my box (at all) because I'm on Win 7 sp1 and that has an ADO interface change, and the fixed version doesn't work on my colleagues box because he's installed the patch from MS.

      I once had Microsoft small business suite fail to install because WMI database was corrupt, yet that install was on a freshly installed copy of Vista. (the point being even when you install on a 'clean' system it can still fail).

      at least webapps are a little less dependant on a load of crap, you tell the user to tell you which browser and its version they're running and that's all they need to tell you. If it still doesn't work, you can tell them to install another browser and try it on that.
      I don't think we'll have issues with web apps conflicting with other web apps, because they'll be sandboxes for security purposes, but that should also help with conflicting.

    7. Re:Interesting Concept by Anonymous Coward · · Score: 0

      My current issue is with a .NET app that doesn't run on my box (at all) because I'm on Win 7 sp1 and that has an ADO interface change, and the fixed version doesn't work on my colleagues box because he's installed the patch from MS

      Yes, they fucked it up but (for the developer of the application) it should not be hard to implement the "fix". Then the application will work on all platforms. I've done it myself.

      http://support.microsoft.com/kb/2517589

    8. Re:Interesting Concept by wzzzzrd · · Score: 1

      the reason people love web apps is because they don't fuck up your computer.

      Get an operating system then.

      --
      On second thought, let's not go to Camelot. It is a silly place.
  3. Im not opposed by james_van · · Score: 5, Interesting

    but i feel like we're back in the late 90's/early 2000's with all the different web technologies from different companies, almost to the point of having to add the old "best viewed in derp derp browser" messages to websites. i know this sort of thing is necessary to move things along, but i kinda hate this limbo phase where we have all kinds of new/interesting/exciting/annoying technologies, and no standards yet to bring them together. that's my rant, ill be quiet now.

    1. Re:Im not opposed by arose · · Score: 4, Interesting

      You're looking too far ahead. The bleeding edge basically has to be this way to hammer out the problems before proposing the standard. On the other hand quite a few new/interesting/exciting/annoying technologies have been drafted together and implemented across the board. Or are things moving so fast that stuff like canvas, that is barely starting to see production adoption, doesn't qualify anymore?

      TL;DR It only seems like The Browser Wars because it's easy to pick out the incompatibilities.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    2. Re:Im not opposed by migla · · Score: 1

      but i feel like we're back in the late 90's/early 2000's with all the different web technologies from different companies, almost to the point of having to add the old "best viewed in derp derp browser" messages to websites. i know this sort of thing is necessary to move things along, but i kinda hate this limbo phase where we have all kinds of new/interesting/exciting/annoying technologies, and no standards yet to bring them together. that's my rant, ill be quiet now.

      You have got a point.

      But, if we look at this from the perspective of freedom-power-to-the-underdog and assume Mozilla is all for that, then there was much rejoicing. I am under the impression that Mozilla is in it for the benefit of all us little common people. Therefore, this, whatever it is, and even if MS allready did it, is presumably a good thing. Somebody correct me if I'm wrong (is Mozilla not the knight with shiny armpits I assume?).

      --
      Some of my favourite people are from th US; Vonnegut, Chomsky, Bill Hicks.
    3. Re:Im not opposed by nine-times · · Score: 1

      Well in fairness, sometimes this sort of thing just needs to happen. It's frustrating when there's a clear technological winner that isn't being implemented because of some political reason, but often enough there are legitimate reasons why the different browsers aren't happy with a given standard. Over time, improvements get made, problems get settled, new standards come out. Eventually, hopefully, there's a good standard that people can agree with. It takes time, but it's just what needs to happen.

      What's really a problem is when good standards get roadblocked because they threaten someone's revenue stream because it breaks vendor lock-in.

    4. Re:Im not opposed by Anonymous Coward · · Score: 0

      Every weird feature in Internet Explorer 5.x was a "proposed standard". About 25% of was adopted into real cross-browser standards, while the rest still lives on as proprietary extensions.

      Point being, once added, this stuff never gets removed, standard or not.

    5. Re:Im not opposed by Anonymous Coward · · Score: 0

      Would you rather go back to the IE 6 only days where you were stuck with a crappy crusty 6 year old browser? Where there was no innovation for 10 years because webmasters had to support the last 10% of users?

      Finally things are unfrozen again and we have innovation

    6. Re:Im not opposed by arose · · Score: 1

      Very much doubt most of it was supposed to be standardized, but if you have some proof I look forwards to being wrong on that (even better if that 25% wasn't just made up!). Proprietary extensions however aren't a problem as long is it's understood that that's what they are and web developers are aware enough not to rely on them. Currently some things are supported across all new browsers (e.g. canvas, fonts) and a bunch more can made to work in one way on half of them and in another on the other half (e.g. video and audio). It's work, it might break in the future, but it's worlds ahead of single browser solutions we used to see.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    7. Re:Im not opposed by Anonymous Coward · · Score: 0

      At least this time around, you can follow web standards and safely put "Best viewed in any browser except versions of IE before 9". Then just let the IE9 users assume the website looks funny, and not their browser being stupid. Just like old times... :P

    8. Re:Im not opposed by hairyfeet · · Score: 2

      If its anything like HTML V5 the "standard" will be fucking useless. Instead of having a brain and setting a free codec as a bare minimum, such as Vorbis or WebM, to where anybody could degrade to that and be assured that the content would play, instead they just left it a generic "video" tag and ended up with Apple being able to slam through H.264 which while it is very obviously the most technologically superior codec, its holding group might a well have as a motto "Pay your $699 license fee, you cocksmoking teabaggers!" so you can give up anybody other than the big three (Apple,Google,MSFT) using it.

      Basically it looks like we are headed right back to the bad old days of "you must use X browser" only it'll be the software patent trolls and lack of any real standards instead of the OS companies shoving it this time. Either way its gonna suck and frankly I wouldn't be surprised if everyone not falling all over the iShiny simply stayed with flash. At least Adobe doesn't sue your ass if you include flash support in your OS or device whereas MPEG-LA made it clear if Moz or anybody wants to support H.264 they better pay their license fee. How long until MPG 2 and 3 are out of patents? Maybe we should just say fuck it and bypass the whole mess.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    9. Re:Im not opposed by nine-times · · Score: 0

      with Apple being able to slam through H.264 which while it is very obviously the most technologically superior codec, its holding group might a well have as a motto "Pay your $699 license fee, you cocksmoking teabaggers!" so you can give up anybody other than the big three (Apple,Google,MSFT) using it.

      Well but here's the problem: First, h264 is (at least arguably) the technologically superior codec. Second, you're paying a licensing fee on h264 for patents, and AFAIK there's still no guarantee that Vorbis or WebM don't infringe on any patents.

      Nobody is claiming patent infringement because they aren't in wide use, and the money isn't really there. If one of them becomes the standard across all kinds of devices, someone might come along and start suing. Now maybe that's just FUD, but it's good enough FUD that it's going to keep people from jumping ship. Switching to a technologically inferior solution requires a huge investment and an uncertain benefit. People aren't going to do it.

      Basically it looks like we are headed right back to the bad old days of "you must use X browser"

      Not sure what you mean. So far, things are as "free" as they've ever been. H264 is *the* standard, like it or not. You can pitch a hissy fit, but the situation isn't much different from distributing music as MP3, which has also been patent-encumbered. GIF images, too.

      At least Adobe doesn't sue your ass if you include flash support in your OS or device whereas MPEG-LA made it clear if Moz or anybody wants to support H.264 they better pay their license fee.

      Adobe isn't going to sue you, but they will try to railroad you into using their products whether you like it or not. Incidentally, Adobe Flash is only increasing adoption of H264, since that's pretty much become the standard encoding for Flash video. The only difference is, instead of Microsoft or Google or Apple paying your licensing fee, Adobe does.

    10. Re:Im not opposed by hairyfeet · · Score: 1

      Well in the case of WebM you have an 8000 pound gorilla buying patents like they are going out of style so I'm sure if they went after Google there would be a serious case of the MAD strategy at play, as Google could unleash their patents and lawyers and make things SERIOUSLY bad for MPEG-LA.

      As for what I mean? There are already two browsers FF and Opera, that can't legally play your videos, so any users of those browsers won't be able to use your site. But since those users CAN use flash, why the fuck should I switch? you're either gonna end up with H.264 for the iShiny and flash for everybody else, or they'll stick with flash and leave the iShiny to GTFO. Oh and most of the videos i've seen in flash are VP6 which on anything under 1080p looks just fine with nice small files.

      Finally how is Adobe forcing shit? not only can you include their player absolutely free which you can NOT do withH.264, they didn't even say shit about Gnash whose who goal is to make a 100% free flash! try that shit with MPGE-LA and see how quickly you get a C&D. Look I'm a Windows guy and even I can see that H.264 is a way to cut off FOSS and lock the web down to the big three. MSFT has NEVER had any trouble from Apple because they know that they aren't really in the same markets. The hipsters that buy Apple wouldn't have anything that Suzy the checkout girl uses so MSFT isn't a consideration and Suzy doesn't have iMoney and would dilute the branding so Apple don't give a fuck about the peasants. And for Google to have full support for H.264 they are gonna have to lock it down as MPEG-LA ain't gonna put up with having their codec free for anybody to have, so watch in the next year to year and a half for Android to get eFuses or code signing. if Google didn't want the TiVo option left open they wouldn't have made damned sure not a single line of GPL V3 code comes anywhere near the Droid.

      You watch either the web sticks with flash or you can kiss any FOSS users watching shit goodbye. Kinda hard to be free as in beer when they gotta pay license fees ya know. Not to mention I can't see RMS and the other hardcore FOSSies allowing kernel DRM into Linux which is what they'll need to have encrypted video like Netflix has which you can be damned sure both MSFT and Apple will be pushing.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    11. Re:Im not opposed by nine-times · · Score: 1

      As for what I mean? There are already two browsers FF and Opera, that can't legally play your videos, so any users of those browsers won't be able to use your site.

      Generally speaking, this is no worse or more fragmented than before. On the contrary, you have basically eliminated WMV, Real Media, and you're on your way to being without Flash.

      But since those users CAN use flash, why the fuck should I switch? you're either gonna end up with H.264 for the iShiny and flash for everybody else, or they'll stick with flash and leave the iShiny to GTFO.

      I think you miss the point. That "Flash video" is still H264. The switch has happened. It's just than when you use Flash, you are locking yourself out of a very popular mobile platform while also committing yourself to a proprietary inefficient video player.

      Finally how is Adobe forcing shit? not only can you include their player absolutely free which you can NOT do withH.264

      Again, you're missing something very important. The Flash player is just another example of a H264 player being included "for free", similarly to the way Quicktime and Chrome are "free". By sticking with Flash, you aren't somehow refusing to move along to H264, you're just committing to a specific player instead of allowing people to use whichever player they like.

      So the question is, what are you really after? At first, I thought you were simply anti-patent and didn't understand how complicated the situation is. In this latest post, however, you seem to merely be anti-Apple and are eager to lock everyone into a specific proprietary H264 video player (i.e. Adobe Flash) in order to hurt Apple. Seems petty to me.

  4. I welcome our new pushers by dlinear · · Score: 0

    Let's hope they push relevant information and not drugs and booze.

    1. Re:I welcome our new pushers by Anonymous Coward · · Score: 0

      What is this? Government approved rock'n'roll? You have been made, narc.

  5. What a great idea: Syndication! by Anonymous Coward · · Score: 5, Funny

    Now if there were only a way to make this syndication Really Simple.

    1. Re:What a great idea: Syndication! by icebraining · · Score: 2, Informative

      That's pull, no push. Pushing is much more efficient.

    2. Re:What a great idea: Syndication! by nschubach · · Score: 1

      Yep, it would be like /. telling you when there's a new story instead of hitting their servers every 2 minutes trying to find out if there are any.

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    3. Re:What a great idea: Syndication! by sexconker · · Score: 4, Interesting

      That's pull, no push. Pushing is much more efficient.

      A "pull" notification requires the client to poke a server and check for content. This is typically done on a set interval.

      A "push" notification requires an open connection to push content through. The client acts as a server.

      Pushing is only more efficient if you're the server or you have a device with such a shitty battery.
      Desktop and laptop users don't give a flying fuck about the battery use required to poke at a server. The only ones who care are people on phones / tablets / nettops / other fad devices. And they all have "apps".

      The bottom line is that the client should NOT have to maintain a connection the server can inject into.
      It's backwards and retarded behavior for a web browser to maintain open connections to remote servers after a page is closed.
      You might as well just elav the tab open.

      There's a reason why no one uses IE's web slices.

    4. Re:What a great idea: Syndication! by JustSomeProgrammer · · Score: 4, Informative

      A pull notification system is more efficient only if there are updates more frequently than polls. If the updates are very infrequent it gets to be more efficient for pushing. And pushing shouldn't require you to keep a connection open to each site, it should just require you to keep one port open where all push notifications would go. The server would open a connection to that port in order to send the push. Unless pushes are frequent then you might maintain an open connection blah blah blah. At least every push system that I've ever worked with works in this way. Usually results in less traffic since there's never a poll that goes "hey ya got anything yet?"

    5. Re:What a great idea: Syndication! by Anonymous Coward · · Score: 0

      So, kinda like subscribing to the slashdot twitter feed? What a novel concept!

    6. Re:What a great idea: Syndication! by Anonymous Coward · · Score: 1

      Who would control the master push server for the web?

    7. Re:What a great idea: Syndication! by sexconker · · Score: 1, Insightful

      A pull notification system is more efficient only if there are updates more frequently than polls. If the updates are very infrequent it gets to be more efficient for pushing. And pushing shouldn't require you to keep a connection open to each site, it should just require you to keep one port open where all push notifications would go. The server would open a connection to that port in order to send the push. Unless pushes are frequent then you might maintain an open connection blah blah blah. At least every push system that I've ever worked with works in this way. Usually results in less traffic since there's never a poll that goes "hey ya got anything yet?"

      First, you'd have to define efficiency.

      As a non-mobile user, I don't give a flying fuck about how much power or system resources my polls cost me, and I don't give a fuck about the server end (because I'm selfish, because it should be able to handle it, etc.). Efficiency is nothing more than the delay between something existing and me getting it. Polling once a minute is more than fine for everything except emergency notifications, and those all (should) have a dedicated, separate communication channel.

      I'd much rather poke a server on demand, or have an explicit polling interval set, than have a pipe into my ass that lets the server poke me even after I've closed the page. Whether or not the connection is left open or not is irelevant - the security, privacy, and don't fucking bother me implications are the same as long as they can reestablish the connection.

      I already have to allow cookies and javascript from shady fucking servers and browse around 10 different sites for airfare before the site I actually want to use shows me their real rate. I don't want to have to allow a "Rate Advisor" to push notifications to me minutes/hours/days after leaving their site just so I can get the true price ("Wait! Come back and book now to save $$$ on your trip to Shitland!!).

    8. Re:What a great idea: Syndication! by icebraining · · Score: 1

      This system doesn't push directly to the client; your argument is irrelevant.

    9. Re:What a great idea: Syndication! by Anonymous Coward · · Score: 1

      And there already is pushing:
      http://en.wikipedia.org/wiki/PubSubHubbub

    10. Re:What a great idea: Syndication! by nschubach · · Score: 2, Informative

      Kind of... if you had twitter notify you every time you got a tweet instead of checking your twitter feed.

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    11. Re:What a great idea: Syndication! by Anonymous Coward · · Score: 0

      YMBGFAP.

    12. Re:What a great idea: Syndication! by ohnocitizen · · Score: 1

      That is an excellent point. I hope it will be easy to turn this off when it comes out in Firefox 13.

    13. Re:What a great idea: Syndication! by hairyfeet · · Score: 1

      So no different than what we had over a dozen years ago with pointcast then?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    14. Re:What a great idea: Syndication! by adolf · · Score: 1

      [much verbiage]

      Your outlook is not unreasonable.

      But here's what I want (for my own valid reasons): Instant updates. Push can do this, while pull cannot (well, without hammering things to the extent that even a selfish bastard like myself would begin to realize that I'm placing undue strain on things while really standing out in someone else's logfile).

      As a consumer, I don't give a flying fuck about security. I've got enough holes by simply connecting my machines with a wide-open egress firewall -- one little inbound connection means nothing to me.

      YMMV.

      (I thought this sort of tech was going to become the new hotness in the middle 90's sometime, but I guess not.)

    15. Re:What a great idea: Syndication! by icebraining · · Score: 1

      It's not an excellent point: the pushes are server-to-server, not to client.

    16. Re:What a great idea: Syndication! by 21mhz · · Score: 1

      And pushing shouldn't require you to keep a connection open to each site, it should just require you to keep one port open where all push notifications would go. The server would open a connection to that port in order to send the push.

      Of course, this works wonderfully in modern day internet, where pretty much every ordinary web client is behind a NAT and/or a firewall of some sort. There are all sorts of ugly solutions to keep that external port open on whatever box controls it (and you are fortunate if there's just one between you and the server), but nothing works as reliably as a TCP connection that is kept alive with periodic pings.

      That said, one connection to take care about all notifications is much better than many web apps doing periodic polls, or even opening a WebSocket each for itself.

      --
      My exception safety is -fno-exceptions.
    17. Re:What a great idea: Syndication! by sexconker · · Score: 1

      This system doesn't push directly to the client; your argument is irrelevant.

      It absolutely pushes to the client, and the client must maintain an open port (thus functioning as a server for this function) for this to happen.

    18. Re:What a great idea: Syndication! by icebraining · · Score: 1

      Can you please point out that part in the proposal? As far as I can see, the proposal only specifies the website to Notification Service part, not the part where those notifications are delivered to the user.

    19. Re:What a great idea: Syndication! by sexconker · · Score: 1

      Can you please point out that part in the proposal? As far as I can see, the proposal only specifies the website to Notification Service part, not the part where those notifications are delivered to the user.

      Are you joking?
      Website -> middle man server -> client devices.

      The middle man exists so they can track statistics, let end users easily manage permissions and devices, and so they can store notification history and push to all devices regardless of when they're reachable.

      Each client device must have an open communcation channel to receive the push notification from the middle man server.

      Or are you suggesting that the proposal is for a service where a website can issue notifications to a server that ends up NOT delivering them to the intended end user?

      The fucking proposal is centered around websites sending messages to the middle man because Mozilla needs their input.
      The proposal doesn't talk about how the middle man delivers the notifications to the end user because the fucking websites don't give a shit how Mozilla hands off the message as long as it gets handed off.
      Do you follow the dump truck to make sure your trash is being collected properly? If your city sends you a questionnaire about possible changes to the trash pickup schedule, do you bitch at them for not discussing the shift changes for Trashman Joe and Trashman Fred? Do you expect to have input on which of them gets to take the old Wednesday route?

    20. Re:What a great idea: Syndication! by icebraining · · Score: 1

      Or are you suggesting that the proposal is for a service where a website can issue notifications to a server that ends up NOT delivering them to the intended end user?

      Of course it delivers them. Doesn't mean it has to deliver them using push over an open connection. In fact, from what I could tell, they considered pushing them to Twitter and email, for example, which aren't necessarily push.

      So, can you tell me where they specify that the delivery to the client has to be done using push over an open connection?

  6. more spam please! by HarrySquatter · · Score: 4, Insightful

    Yay! A new spam vector!

    1. Re:more spam please! by Anonymous Coward · · Score: 3, Informative

      Requires your permission first. Get spammed? Revoke permission.

    2. Re:more spam please! by HarrySquatter · · Score: 3, Insightful

      Riiight. Because no one will ever find a way to abuse it. No, that never happens.

    3. Re:more spam please! by gorzek · · Score: 3, Informative

      Riiiight. Because it couldn't at all be possible to have a settings page like this:

      From which sites do you wish to permit push notifications?
      slashdot.org
      news.google.com
      cnn.com

      No, your browser would have to accept (and display!) every single notification ever sent to you. Makes perfect sense.

      And for each little notification bubble, why couldn't there be a little button? "Don't allow any more notifications from this service." Done.

      It's like saying you just have to deal with spam emails. No, you don't. That's what spam filters, whitelists, etc. are for. This sort of service sounds like it would be whitelist-based to begin with, so anyone who abuses the service can easily be blocked.

    4. Re:more spam please! by HarrySquatter · · Score: 2

      Because you think people can't be easily tricked into giving permission for this and then it used for spam?

    5. Re:more spam please! by sexconker · · Score: 5, Insightful

      Riiiight. Because it couldn't at all be possible to have a settings page like this:

      From which sites do you wish to permit push notifications?
      slashdot.org
      news.google.com
      cnn.com

      No, your browser would have to accept (and display!) every single notification ever sent to you. Makes perfect sense.

      And for each little notification bubble, why couldn't there be a little button? "Don't allow any more notifications from this service." Done.

      It's like saying you just have to deal with spam emails. No, you don't. That's what spam filters, whitelists, etc. are for. This sort of service sounds like it would be whitelist-based to begin with, so anyone who abuses the service can easily be blocked.

      Sorry, this post cannot be displayed.
      Please make sure you enable cookies, javascript, popups, and ads from yet.another.spamming.and.tracking.domain.from.google.com .

    6. Re:more spam please! by houghi · · Score: 2

      Yes, because that is what I like. Click on accept and/or decline for each website I ever visit and then not know if it actually comes from that site or from a subdomain or from some iframe or ...

      You want to know the updates of a site? Use RSS. Opt-in, not opt-out please.

      --
      Don't fight for your country, if your country does not fight for you.
    7. Re:more spam please! by Zan+Lynx · · Score: 1

      Sorry, this post cannot be displayed.
      Please make sure you enable cookies, javascript, popups, and ads from yet.another.spamming.and.tracking.domain.from.google.com .

      I use Firebug quite a lot to get around this because I run NoScript. Hello noscript tag or large obnoxious div blocking me from your mostly usable web site. Your visibility is now set to false.

    8. Re:more spam please! by firewrought · · Score: 1

      It's like saying you just have to deal with spam emails. No, you don't. That's what spam filters, whitelists, etc. are for.

      Umm... email spam is only kinda half-solved, and that's after throwing millions of dollars at it.

      --
      -1, Too Many Layers Of Abstraction
    9. Re:more spam please! by Anonymous Coward · · Score: 0

      I was wondering why I didn't see anyone else concerned about the obvious? security problems this enables.

    10. Re:more spam please! by 21mhz · · Score: 2

      Because you think somebody can be tricked into getting spam through this, and is dumb enough to not be able to cut the spammer off, means that the technology is useless for any legitimate purpose?

      --
      My exception safety is -fno-exceptions.
  7. Data caps? by mr_lizard13 · · Score: 4, Funny

    I fear if they use this to push notifications for each new Firefox release then I'll exceed my data cap.

    --
    "We live in a global world" - Harvey Pitt, former Securities and Exchange Commission Chairman
  8. Re:RSS by HarrySquatter · · Score: 0

    It's old. This is new and hip. It's more Web 2.0 (hell it might be Web 3.0) than RSS.

  9. All the best to Mozilla by Xolve · · Score: 3, Interesting

    Apart from making browser and email client, Mozilla is contributing a lot to bring more functionality to web. The good thing is that they do it in a very open way. But they lack popular web services to push the features. e.g. Google brought these APIs to Chrome and Gmail implemented them. While how many websites actually honor do not track option is still not known. Mozilla should also try to find collaborations with major web services providers to make the features happen.

    1. Re:All the best to Mozilla by hobarrera · · Score: 1

      Since Google has many "archenemies" (microsoft, facebook, etc), mozilla con just "suggest" to them that they use this technology. I belive there's a greater chance of them adopting it than gmail.
      Or maybe not.

  10. Nostalgia Goggles: PointCast by Anonymous Coward · · Score: 2, Interesting

    How is this different from PointCast?

    I never really saw the advantage of push technology over lightweight "pull" technology like RSS feeds. And who really wants desktop notifications when they're not using a program meant to read that kind of info? It's not like memory's so starved we have to close all our apps when they're not in use. We do that only when we don't want them bothering us.

  11. 256 bit entropy? by betterunixthanunix · · Score: 1

    Are they saying they support at least 32 bytes of information per message? 256 bits of randomness for those random messages? Perhaps I am just missing out on some cool-hip-web2.0-developer terminology here?

    --
    Palm trees and 8
  12. Re:RSS by icebraining · · Score: 2

    It's polling, which is extremely inefficient.

  13. Nevermind misread that by betterunixthanunix · · Score: 1

    The identifiers have 256 bits of entropy.

    --
    Palm trees and 8
  14. SIP SUBSCRIBE??? by janeuner · · Score: 2

    But I guess somebody's paycheck depends on reinventing the wheel?

    http://tools.ietf.org/html/rfc3265

  15. Re:So... by Anaerin · · Score: 1
  16. suing by bigbangnet · · Score: 1

    So who's gonna patent this technology first so they can sue the fuck out of everyone this time ? ps: does it show I got no more faith for this suing business thing anymore ?

    1. Re:suing by Anonymous Coward · · Score: 0

      What it shows is that you have a dramatic lack of understanding of how things work in the real world... which honestly is no surprise.

  17. Re:RSS by msheekhah · · Score: 2

    I'm a futurist. Where's my Web 7.0?

    --
    Mark Anthony Collins
  18. Dynamic IP? by Anonymous Coward · · Score: 1

    How will this work with dynamic IPs?
    What privacy implications are there if a message intended for me got sent to someone else who now has my IP?

    There'd need to be some sort of system for people to regularly refresh their IP. Opera Unite sort of done this by having their own service which connected to their servers.
    So, basically have the system designed in a way that it automatically refreshes IP to the server for whatever website you are subbed to when the IP is detected as different. (sort of like how the clients work for DynDNS or various other sites)
    Essentially it would be instant, always-on E-mail, and your IP would be the session. (well, obviously an account too initially!)

    I still don't think it would be used by most people though.
    Look at Chrome Notifications. Gmail is the only site I know that uses it. (seriously surprised Facebook doesn't use it, in fact)
    WebSlices as mentioned above isn't entirely related. It lets you subscribe to a slice of a webpage. It is basically a web scraper. BUT, some of the ideas there are certainly heading in the right direction.
    Hope Microsoft actually offer some feedback on this one and try to come to some sort of standard. This COULD be incredibly useful. But only if it gets standardized and done right. If it ends up being more obtuse than clicking a link, adding a user account, password (or done automatically if logged in), then some more advanced options if people wish to edit them (such as period to update IP, whether instant, every X hours, days, whatever), it is just going to be left unused by a large amount of people again.

    1. Re:Dynamic IP? by Obfuscant · · Score: 1

      How will this work with dynamic IPs? What privacy implications are there if a message intended for me got sent to someone else who now has my IP?

      What's even more important is how does this deal with people who are behind NAT or a firewall? I mean, my "browser" can become a "server" by opening a port on my desktop all it wants, nobody from outside is going to be able to connect to it.

      Now, I can open that path through my router if I want to, but what about people who work behind firewalls that can't change anything?

    2. Re:Dynamic IP? by Anonymous Coward · · Score: 0

      The article says that you don't have to have the web page open, you'll still have to have firefox open. You'll probably have to login to a mozilla account to use this option (like chrome as sync, etc). At this time, firefox can continue to match your account to your IP allowing their notifications system to send it to your browser.

  19. So, who's to blame... by xded · · Score: 1

    The companies that are trying to innovate, the companies that don't want to see *other* companies innovate, or the standardization system that moves at the speed of my grandpa, rocking in his chair while keeping an eye on all these children running around?

  20. Riiiiiiight by Anonymous Coward · · Score: 0, Funny

    a way to receive notifications from websites without having to keep them open in your browser

    Why not... oh, I don't know... fix the god damned browser's shitty memory handling so I can leave the fucking web page open for more than an hour!

    1. Re:Riiiiiiight by LaRainette · · Score: 1

      FF 10 : 25 tabs opened for 24 hours. Including tons with flash. 800MB memmory used.
      Chrome : Same 25 Tabs opened for 24 hours : Usage 770MB.
      ZOMG Firefox USES SO MUCH MEMORY !!!
      PS : 2008 called they want their bitching comment back.

  21. The 90s indeed.... by John+Bokma · · Score: 1

    I still have a copy of Delivering Push somewhere in the Netherlands ...

  22. Obligatory XKCD reference by jcreus · · Score: 1
    1. Re:Obligatory XKCD reference by Anonymous Coward · · Score: 0

      We need a standard way to reference obligatory XKCD strips.

    2. Re:Obligatory XKCD reference by hobarrera · · Score: 1

      Which are the other standards for web push tecnologies?

  23. Will it even work? by Todd+Knarr · · Score: 4, Insightful

    Will it work:

    • When the browser isn't running?
    • When the machine's behind a NATing router that isn't configured for port forwarding or a DMZ?
    • When the machine's behind a firewall that blocks all incoming connections that aren't associated with an outbound connection?

    If it can't, then we're going to be able to use it how again?

    1. Re:Will it even work? by firewrought · · Score: 1

      • When the browser isn't running?
      • When the machine's behind a NATing router that isn't configured for port forwarding or a DMZ?
      • When the machine's behind a firewall that blocks all incoming connections that aren't associated with an outbound connection?

      It's a problem on the host side too... the origin IP will be hidden by the firewall and/or load balancer. There are some workarounds, but will your infrastructure department support them? And can you get the workaround to play nice with your developer tools / website SDK's / vendor products / etc. that have come to depend on this push feature?

      --
      -1, Too Many Layers Of Abstraction
    2. Re:Will it even work? by emj · · Score: 1

      Yes it will, basically

      1. the website ask for permision
      2. the webbrowser asks the user
      3. the user says Sure post you notifications to my notification URL http://example.com/my-notes
      4. user checks http://example.com/my-notes for notifications
      5. the website pushes notifications to the notification URL
      6. user checks http://example.com/my-notes for notifications
      7. user checks http://example.com/my-notes for notifications
      8. user checks http://example.com/my-notes for notifications
      9. user checks http://example.com/my-notes for notifications

    3. Re:Will it even work? by Obfuscant · · Score: 1

      3. the user says Sure post you notifications to my notification URL http://example.com/my-notes

      So just where is this user's 24/7 webservice going to be running, that can accept this "push" content? You haven't solved the problem, you've just hidden it behind a URL.

      6. user checks http://example.com/my-notes for notifications

      So it really is pull, just written with the letters 'p', 'u', 's' and 'h'?

      If I want to check a URL for content, why not just check the URL directly?

    4. Re:Will it even work? by firewrought · · Score: 1

      Replying to myself now that I've read the protocol. Their design isn't an issue for the host, because it is the client that determines the callback URL.

      To make the spec viable*, it seems like you would need a third party service (possibly run by Mozilla or Verizon, Sprint, etc.) that your browser would talk with to get internet-visible callback URL's for. The service would aggregate your notifications, and you'd either poll for them periodically or maintain an always-on TCP/IP connection. It requires much more browser support than they're actually talking about, and it seems to be a pretty dumb arrangement for receiving notifications from a handful of sites, but perhaps the designers of this spec see a world where you have hundreds or thousands of websites sending you notifications.

      *E.g., to deal with NAT and firewalls, to enable encryption of notifications (HTTPS callback URL's), to centrally manage spam/malware filtering, and to receive notifications uninterrupted as you join/disconnect from different networks and as you open/close your browser.

      --
      -1, Too Many Layers Of Abstraction
    5. Re:Will it even work? by Todd+Knarr · · Score: 1

      If they're doing that, why don't I just query the website directly using, oh, I don't know, their RSS feed?

  24. XMPP PubSup by Anonymous Coward · · Score: 1

    Is there a reason why they don't use an already available and open standard like XMPP (wich BTW could also replace RSS)?
    http://xmpp.org/about-xmpp/technology-overview/pubsub/

    1. Re:XMPP PubSup by Anonymous Coward · · Score: 0

      The subject was obviously "PubSub"...

    2. Re:XMPP PubSup by yelvington · · Score: 1

      Discussed in the documentation, but this is Slashdot, so nobody will read that.

    3. Re:XMPP PubSup by Anonymous Coward · · Score: 0

      Well, I was looking for a little explanation...
      All I read in their wiki is something like: "We didn't use already established standards for various reasons". I don't know much about those things so it wasn't really useful.
      I just don't see how it's better (could be my ignorance) and "The provider has a set of user tokens for their customers. They then send messages to token@mozillamessaging.com (domain tbd) [...]" doesn't seem so good to me (does it all always go trough Mozilla?).

    4. Re:XMPP PubSup by Anonymous Coward · · Score: 0

      Yeah, they say there are some reasons why they don't use already existing standards, but they don't explain or even cite them in their wiki (and I can be bothered to search any further)...
      In my ignorance (I don't know much about this stuff) I don't see what's wrong with XMPP while I see a couple of things I don't like about their solution (unsupported, everything seems to go through their servers, yet another standard).

  25. push is a failure by Surt · · Score: 1

    People have been trying to get this right since at least 1998. The problem is, there is no right. As soon as you have a push channel, websites begin abusing it, and that channel gets shut down. It just can't be done.

    --
    "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  26. Re:Thius Delay is Intorable! by LocalH · · Score: 2

    So just don't use it. It's not like this is a requirement.

    It amazes me the number of so-called "technologically-savvy" people who are closet Luddites.

    --
    FC Closer
  27. Internet vs. Web by ArtemaOne · · Score: 1

    What, are we finally going to use something besides port 80? Haven't they all been blocked by our ISPs already?

    1. Re:Internet vs. Web by idontgno · · Score: 2

      No, actually, that's the point. That's the technology trend of the 21st Century.

      Every transport, protocol, or presentation which used to be carried over TCP or UDP will now be re-encapsulated and shipped down TCP/80 or TCP/443 with a hip new name.

      Why? Because doing everything in a browser is COOL.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
  28. Been done? by Anonymous Coward · · Score: 0

    A bit of generalizing in the post there. I have a couple of desktop notification apps that don't require websites or my browser to be open.

  29. What It Will Be Used For by sexconker · · Score: 1

    What it will be used for:

    Search Kayak.com for tickets to Hawaii in a month.
    Click on a link for the flight you want.
    Get a popup about allowing their "rate advisor".
    Allow it.
    Go back to the Kayak results.
    Click another result from a competitor airline and allow their "rate advisor".
    Get a notification from the first airline that you can save $$ on that flight if you book now.
    Go back to the first airline's website.
    Get a notification from the second airline that you can save $$ on that flight if you book now.
    Compare the two actual prices and decide which flight you want.
    Remove permissions for trip advisors.
    Reblock notification permissions, ads, javascript, and third party / promiscuous cookies related to their sites.

  30. Saves on app tabs by normaldotcom · · Score: 1

    This is actually a useful idea--I keep at least 6 "app tabs" open in firefox at all times just to see when I get notifications from Gmail, Facebook, Twitter, Google Calendar, Google Voice, etc. A push notification system could give nice in-browser notifications without keeping entire pages loaded into memory.

  31. {url: url} by hey · · Score: 1

    I enjoy code like:

            {url: url}

  32. Re:Thius Delay is Intorable! by cas2000 · · Score: 1

    yeah, it's almost as amazing as the number of fire-savvy people who are against people sticking their hands into a furnace.

    or the privacy-savvy people who try to warn others about the dangers of facebook and other web spyware.

  33. Re:RSS by LaRainette · · Score: 1

    Pull Vs Push services.

  34. Netscape Netcaster by Anonymous Coward · · Score: 0

    So it's Netscape Netcaster all over again. The future is always so original. It's gonna be about as big a hit as it was then.

  35. Re:Thius Delay is Intorable! by Barbara,+not+Barbie · · Score: 1

    It amazes me the number of so-called "technologically-savvy" people who are closet Luddites.

    What, they've come out with a new closet? So all of a sudden we're supposed to junk perfectly-working closets that keep all our clothes organized the way we're used to? No thanks.

    Seriously though, who cares? You can spend so much time "being connected" that you lose any real connections - look at all the people who use facebook to replace real-life contacts. The more they do this, the more they miss real-life interactions, so they end up in a vicious feedback loop where they spend even more time online trying to make up for it..

    --
    Let's call it what it is, Anti-Social Media.
  36. WebChunks extension by Anonymous Coward · · Score: 0

    The BlueGriffon author wrote a Firefox extension that implemented IE's WebSlices called WebChunks for Firefox 3.5, and as you can tell from how popular it was, he never updated it.

  37. This would have been news ... by Anonymous Coward · · Score: 0

    ... in '98. RSS and Atom have come out since for similar puproses, but it hasn't been done right. But more importantly, theres a reason that this hasn't found too much of a niche: its a solution looking for a problem. There isn't anything that it does that can't be done with other things, without needing a specific browser.

    Mozilla really is leveraging its market share unfairly lately, forcing aggressive upgrade models and features no one wants, while breaking core functionalities. This is just another step down that road, and it's unsurprising that the market share is going to Chrome more these days.

  38. RSS by windcask · · Score: 1

    Isn't this functionality, to a large extent, provided with a decent RSS reader?

  39. Hey Firefox. by Anonymous Coward · · Score: 0

    Hey Firefox.

    Push off.

  40. Only if it sends to Growl by Jonah+Hex · · Score: 1

    I really don't need anything popping up but my Growl http://en.wikipedia.org/wiki/Growl_(software) So push me your notifications, but do it in a standard way. HEX

    1. Re:Only if it sends to Growl by caspy7 · · Score: 1

      If the protocol becomes accepted/standardized, Growl will probably want to incorporate it.

    2. Re:Only if it sends to Growl by hobarrera · · Score: 1

      Or libnotify on *nix. Most *nixapps use this to show standardized notifications, and mozilla just caught up the last year or so.

  41. Re:RSS by Anonymous Coward · · Score: 0

    Where by "extremely inefficient" you mean "still requires utterly insignificant bandwidth compared to the video streaming and file sharing that make up the vast majority of internet traffic, but hey, we should totally concentrate on getting 0.0000001% down to 0.00000005% rather than working on anything that will have a noticable effect!"

  42. RE: Notifications by Anonymous Coward · · Score: 0

    They should stick to the browser; and use the browser as a desktop;
    otherwise they are going our way.

    See http://thinktank.tsert.com/patent-raod.html
            http://thinktank.tsert.com/patent-rcas.html
            http://thinktank.tsert.com/patent-rras.html
            http://thinktank.tsert.com/patent-feed.html

    Tsert.Com
    67.20.94.20