Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. As the news is reporting, sadly there was a terrible plane crash at LaGuardia Airport at 23:38 local last night.

As the news is reporting, sadly there was a terrible plane crash at LaGuardia Airport at 23:38 local last night.

Scheduled Pinned Locked Moved Uncategorized
chillyatcadvent
33 Posts 14 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • chillybot@infosec.exchangeC chillybot@infosec.exchange

    NTSB Press Briefing on the incident
    https://www.youtube.com/watch?v=UieRrg2etdY

    chillybot@infosec.exchangeC This user is from outside of this forum
    chillybot@infosec.exchangeC This user is from outside of this forum
    chillybot@infosec.exchange
    wrote last edited by
    #10

    And blancolirio did a video on the crash https://www.youtube.com/watch?v=VnSGMPaJ2OM

    scottwilson@infosec.exchangeS chillybot@infosec.exchangeC 2 Replies Last reply
    0
    • chillybot@infosec.exchangeC chillybot@infosec.exchange

      And blancolirio did a video on the crash https://www.youtube.com/watch?v=VnSGMPaJ2OM

      scottwilson@infosec.exchangeS This user is from outside of this forum
      scottwilson@infosec.exchangeS This user is from outside of this forum
      scottwilson@infosec.exchange
      wrote last edited by
      #11

      @chillybot I listened to the ATC of this incident. Brutal.

      1 Reply Last reply
      0
      • chillybot@infosec.exchangeC chillybot@infosec.exchange

        And blancolirio did a video on the crash https://www.youtube.com/watch?v=VnSGMPaJ2OM

        chillybot@infosec.exchangeC This user is from outside of this forum
        chillybot@infosec.exchangeC This user is from outside of this forum
        chillybot@infosec.exchange
        wrote last edited by
        #12

        Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

        • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

        • The controller clearly at least twice told the truck to stop before the crash

        • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

        • There is conflicting information on which air traffic controller was in charge of operations on the ground.

        • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

        • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

        • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

        • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

        • The automatic runway status lights were operational and indicated it was not clear to cross the runway

        • Chairwoman Homendy is awesome, as usual

        #AvGeek

        adamshostack@infosec.exchangeA davemwilburn@infosec.exchangeD insidertreat@infosec.exchangeI mlanger@mastodon.worldM user47@vmst.ioU 6 Replies Last reply
        1
        0
        • chillybot@infosec.exchangeC chillybot@infosec.exchange

          Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

          • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

          • The controller clearly at least twice told the truck to stop before the crash

          • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

          • There is conflicting information on which air traffic controller was in charge of operations on the ground.

          • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

          • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

          • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

          • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

          • The automatic runway status lights were operational and indicated it was not clear to cross the runway

          • Chairwoman Homendy is awesome, as usual

          #AvGeek

          adamshostack@infosec.exchangeA This user is from outside of this forum
          adamshostack@infosec.exchangeA This user is from outside of this forum
          adamshostack@infosec.exchange
          wrote last edited by
          #13

          @chillybot @paul_ipv6 Thank you!

          chillybot@infosec.exchangeC 1 Reply Last reply
          0
          • chillybot@infosec.exchangeC chillybot@infosec.exchange

            Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

            • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

            • The controller clearly at least twice told the truck to stop before the crash

            • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

            • There is conflicting information on which air traffic controller was in charge of operations on the ground.

            • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

            • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

            • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

            • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

            • The automatic runway status lights were operational and indicated it was not clear to cross the runway

            • Chairwoman Homendy is awesome, as usual

            #AvGeek

            adamshostack@infosec.exchangeA This user is from outside of this forum
            adamshostack@infosec.exchangeA This user is from outside of this forum
            adamshostack@infosec.exchange
            wrote last edited by
            #14

            @chillybot @paul_ipv6 Meanwhile in cybersecurity we get reports like “scattered spider vished the mfa and then laterelled and no one could have foreseen it.” Cc @boblord @wendynather

            chillybot@infosec.exchangeC 1 Reply Last reply
            0
            • adamshostack@infosec.exchangeA adamshostack@infosec.exchange

              @chillybot @paul_ipv6 Meanwhile in cybersecurity we get reports like “scattered spider vished the mfa and then laterelled and no one could have foreseen it.” Cc @boblord @wendynather

              chillybot@infosec.exchangeC This user is from outside of this forum
              chillybot@infosec.exchangeC This user is from outside of this forum
              chillybot@infosec.exchange
              wrote last edited by
              #15

              @adamshostack
              Yupppp, exactly. Bring back the CSRB! Aviation makes me jealous. We as an industry have much to learn from them.
              @paul_ipv6 @boblord @wendynather

              petrillic@hachyderm.ioP tindrasgrove@infosec.exchangeT 2 Replies Last reply
              0
              • adamshostack@infosec.exchangeA adamshostack@infosec.exchange

                @chillybot @paul_ipv6 Thank you!

                chillybot@infosec.exchangeC This user is from outside of this forum
                chillybot@infosec.exchangeC This user is from outside of this forum
                chillybot@infosec.exchange
                wrote last edited by
                #16

                @adamshostack
                Of course! Thanks for the thanks
                @paul_ipv6

                1 Reply Last reply
                0
                • chillybot@infosec.exchangeC chillybot@infosec.exchange

                  Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                  • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                  • The controller clearly at least twice told the truck to stop before the crash

                  • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                  • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                  • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                  • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                  • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                  • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                  • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                  • Chairwoman Homendy is awesome, as usual

                  #AvGeek

                  davemwilburn@infosec.exchangeD This user is from outside of this forum
                  davemwilburn@infosec.exchangeD This user is from outside of this forum
                  davemwilburn@infosec.exchange
                  wrote last edited by
                  #17

                  @chillybot

                  Did you get any sense as to whether they'd be looking at the FAA's practice of granting anticipatory clearance as a potential factor?

                  chillybot@infosec.exchangeC 1 Reply Last reply
                  0
                  • chillybot@infosec.exchangeC chillybot@infosec.exchange

                    @adamshostack
                    Yupppp, exactly. Bring back the CSRB! Aviation makes me jealous. We as an industry have much to learn from them.
                    @paul_ipv6 @boblord @wendynather

                    petrillic@hachyderm.ioP This user is from outside of this forum
                    petrillic@hachyderm.ioP This user is from outside of this forum
                    petrillic@hachyderm.io
                    wrote last edited by
                    #18

                    @chillybot @adamshostack @paul_ipv6 @boblord @wendynather another plug for another group doing yeoman's work... US Chemical Safety and Hazard Investigation Board. I use these constantly to demonstrate how to explain VERY complicated problems to people clearly, and identify fundamental structural changes that can improve things.

                    https://www.youtube.com/user/USCSB

                    wendynather@infosec.exchangeW 1 Reply Last reply
                    0
                    • chillybot@infosec.exchangeC chillybot@infosec.exchange

                      Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                      • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                      • The controller clearly at least twice told the truck to stop before the crash

                      • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                      • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                      • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                      • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                      • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                      • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                      • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                      • Chairwoman Homendy is awesome, as usual

                      #AvGeek

                      insidertreat@infosec.exchangeI This user is from outside of this forum
                      insidertreat@infosec.exchangeI This user is from outside of this forum
                      insidertreat@infosec.exchange
                      wrote last edited by
                      #19

                      @chillybot obviously I feel for everyone involved but I listened to the ATC recording afterwards and couldn't help feel like that ATC is going to fully blame themselves.

                      1 Reply Last reply
                      0
                      • petrillic@hachyderm.ioP petrillic@hachyderm.io

                        @chillybot @adamshostack @paul_ipv6 @boblord @wendynather another plug for another group doing yeoman's work... US Chemical Safety and Hazard Investigation Board. I use these constantly to demonstrate how to explain VERY complicated problems to people clearly, and identify fundamental structural changes that can improve things.

                        https://www.youtube.com/user/USCSB

                        wendynather@infosec.exchangeW This user is from outside of this forum
                        wendynather@infosec.exchangeW This user is from outside of this forum
                        wendynather@infosec.exchange
                        wrote last edited by
                        #20

                        @petrillic @chillybot @adamshostack @paul_ipv6 @boblord Whoa, great callout!

                        1 Reply Last reply
                        0
                        • davemwilburn@infosec.exchangeD davemwilburn@infosec.exchange

                          @chillybot

                          Did you get any sense as to whether they'd be looking at the FAA's practice of granting anticipatory clearance as a potential factor?

                          chillybot@infosec.exchangeC This user is from outside of this forum
                          chillybot@infosec.exchangeC This user is from outside of this forum
                          chillybot@infosec.exchange
                          wrote last edited by
                          #21

                          @DaveMWilburn
                          To explain for others, anticipatory clearance in this case refers to the practice of essentially preventing the runway from being used by anyone other than the plane cleared to land. ATCs in the US do not currently do this while a lot of Europe does.

                          Regarding the briefing, I do not believe this specifically was discussed. That being said yesterday was the first full day of investigation and I think the NTSB will likely look into it.

                          davemwilburn@infosec.exchangeD 1 Reply Last reply
                          0
                          • chillybot@infosec.exchangeC chillybot@infosec.exchange

                            @DaveMWilburn
                            To explain for others, anticipatory clearance in this case refers to the practice of essentially preventing the runway from being used by anyone other than the plane cleared to land. ATCs in the US do not currently do this while a lot of Europe does.

                            Regarding the briefing, I do not believe this specifically was discussed. That being said yesterday was the first full day of investigation and I think the NTSB will likely look into it.

                            davemwilburn@infosec.exchangeD This user is from outside of this forum
                            davemwilburn@infosec.exchangeD This user is from outside of this forum
                            davemwilburn@infosec.exchange
                            wrote last edited by
                            #22

                            @chillybot I was under the impression that "anticipatory clearance" is an American FAA practice, unusual elsewhere in the world, of granting clearance to inbound aircraft before the runway is clear, in anticipation of any preceding aircraft and other obstacles clearing the runway before their arrival. Am I wrong?

                            chillybot@infosec.exchangeC 1 Reply Last reply
                            0
                            • davemwilburn@infosec.exchangeD davemwilburn@infosec.exchange

                              @chillybot I was under the impression that "anticipatory clearance" is an American FAA practice, unusual elsewhere in the world, of granting clearance to inbound aircraft before the runway is clear, in anticipation of any preceding aircraft and other obstacles clearing the runway before their arrival. Am I wrong?

                              chillybot@infosec.exchangeC This user is from outside of this forum
                              chillybot@infosec.exchangeC This user is from outside of this forum
                              chillybot@infosec.exchange
                              wrote last edited by
                              #23

                              @DaveMWilburn
                              You are not! I forgot a not haha Your phrasing is indeed better

                              1 Reply Last reply
                              0
                              • chillybot@infosec.exchangeC chillybot@infosec.exchange

                                @adamshostack
                                Yupppp, exactly. Bring back the CSRB! Aviation makes me jealous. We as an industry have much to learn from them.
                                @paul_ipv6 @boblord @wendynather

                                tindrasgrove@infosec.exchangeT This user is from outside of this forum
                                tindrasgrove@infosec.exchangeT This user is from outside of this forum
                                tindrasgrove@infosec.exchange
                                wrote last edited by
                                #24

                                @chillybot @adamshostack @paul_ipv6 @boblord @wendynather the best incident report ive read was written by someone who was given zero guidance on how to investigate, but he was previously an aviator, so he just did what he knew.

                                adamshostack@infosec.exchangeA 1 Reply Last reply
                                0
                                • tindrasgrove@infosec.exchangeT tindrasgrove@infosec.exchange

                                  @chillybot @adamshostack @paul_ipv6 @boblord @wendynather the best incident report ive read was written by someone who was given zero guidance on how to investigate, but he was previously an aviator, so he just did what he knew.

                                  adamshostack@infosec.exchangeA This user is from outside of this forum
                                  adamshostack@infosec.exchangeA This user is from outside of this forum
                                  adamshostack@infosec.exchange
                                  wrote last edited by
                                  #25

                                  @TindrasGrove @wendynather @chillybot @paul_ipv6 @boblord Must.. reinvent.. wheel!

                                  tindrasgrove@infosec.exchangeT ferrix@mastodon.onlineF 2 Replies Last reply
                                  0
                                  • adamshostack@infosec.exchangeA adamshostack@infosec.exchange

                                    @TindrasGrove @wendynather @chillybot @paul_ipv6 @boblord Must.. reinvent.. wheel!

                                    tindrasgrove@infosec.exchangeT This user is from outside of this forum
                                    tindrasgrove@infosec.exchangeT This user is from outside of this forum
                                    tindrasgrove@infosec.exchange
                                    wrote last edited by
                                    #26

                                    @adamshostack @wendynather @chillybot @paul_ipv6 @boblord
                                    Just change all the acronyms and no one will know you just copy/pasted entire manuals

                                    tarah@infosec.exchangeT 1 Reply Last reply
                                    0
                                    • chillybot@infosec.exchangeC chillybot@infosec.exchange

                                      Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                                      • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                                      • The controller clearly at least twice told the truck to stop before the crash

                                      • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                                      • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                                      • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                                      • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                                      • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                                      • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                                      • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                                      • Chairwoman Homendy is awesome, as usual

                                      #AvGeek

                                      mlanger@mastodon.worldM This user is from outside of this forum
                                      mlanger@mastodon.worldM This user is from outside of this forum
                                      mlanger@mastodon.world
                                      wrote last edited by
                                      #27

                                      @chillybot @rpmik In defense of ATC handling multiple positions after midnight: there's very little traffic at an airport between midnight and maybe 5 AM. I'm not saying that it was OK to do so in this particular situation because I don't know the details of the situation. I'm just saying that it is reasonable to have less staff in the middle of the night than, say, in the morning between 8 AM and 11 AM.

                                      chillybot@infosec.exchangeC 1 Reply Last reply
                                      0
                                      • mlanger@mastodon.worldM mlanger@mastodon.world

                                        @chillybot @rpmik In defense of ATC handling multiple positions after midnight: there's very little traffic at an airport between midnight and maybe 5 AM. I'm not saying that it was OK to do so in this particular situation because I don't know the details of the situation. I'm just saying that it is reasonable to have less staff in the middle of the night than, say, in the morning between 8 AM and 11 AM.

                                        chillybot@infosec.exchangeC This user is from outside of this forum
                                        chillybot@infosec.exchangeC This user is from outside of this forum
                                        chillybot@infosec.exchange
                                        wrote last edited by
                                        #28

                                        @mlanger
                                        This is very true. Occasionally, however, it can get quite busy but usually it is a light shift.
                                        @rpmik

                                        mlanger@mastodon.worldM 1 Reply Last reply
                                        0
                                        • chillybot@infosec.exchangeC chillybot@infosec.exchange

                                          @mlanger
                                          This is very true. Occasionally, however, it can get quite busy but usually it is a light shift.
                                          @rpmik

                                          mlanger@mastodon.worldM This user is from outside of this forum
                                          mlanger@mastodon.worldM This user is from outside of this forum
                                          mlanger@mastodon.world
                                          wrote last edited by
                                          #29

                                          @chillybot @rpmik I bet it gets zoo like when weather delays have flights arriving much later than originally expected. But I'd also hope that they'd be able to modify scheduling on the fly to handle things like that. Maybe I'm just expecting too much of them.

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups