Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • 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 (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Contract vs Fulltime

Contract vs Fulltime

Scheduled Pinned Locked Moved The Lounge
careervisual-studiotutorialquestion
32 Posts 23 Posters 1 Views 1 Watching
  • 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.
  • D Dan Neely

    Sounds like a cut down version of what @Ennis-Ray-Lynch-Jr [^] used to recommend whenever the question was asked. At one point he also had a calculator to help in factoring in how much more you should ask to cover the inevitable downtime between contracts; but a quick search failed to find it.

    Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt

    N Offline
    N Offline
    Nagy Vilmos
    wrote on last edited by
    #8

    It was Ennis and I apologise for forgetting and giving credit.

    veni bibi saltavi

    1 Reply Last reply
    0
    • L Lost User

      Nagy Vilmos wrote:

      2080 hours in a year
      1960 working hours in a year (10 federal holidays)
      1920 working hours if you take two weeks vacation

      So 10 days federal holiday equals = -120 hrs - Which suggests a 60 hr week And then 2 week vacation (10 days) = -40 hrs - Which suggests a 20 hr week. :confused:

      N Offline
      N Offline
      Nagy Vilmos
      wrote on last edited by
      #9

      cut and paste are hard!

      veni bibi saltavi

      1 Reply Last reply
      0
      • P pfsWrite

        I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

        R Offline
        R Offline
        rnbergren
        wrote on last edited by
        #10

        The rule of thumb we follow in the states is pretty much 2xPer hour = annual salary. Sooo, $90 per hour is about 180k per year. so that is a great deal more than 115k. That is pretty much it.

        To err is human to really mess up you need a computer

        1 Reply Last reply
        0
        • P pfsWrite

          I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

          G Offline
          G Offline
          gardnerp
          wrote on last edited by
          #11

          I've had to do the same calculations. Of course your results will vary, but maybe this will help: I take 5 weeks vacation. No sick/personal time allowed. Add in 7 holidays and that's 32 days per year. This means with contract I'll just get paid for (5 * 52) - 32 = 228 days. 228 days * 8 hours * $90 = $164160 annually. Now, I would have to pay about 9% in social security, medicare, and unemployment tax separate from what an employee pays (as a contractor). Next, I'd lose a 3% contribution towards a 401k plan. That brings it down to $144460. From here, remove any annual bonuses. Then remove medical/dental/vision benefits. For me that would take it down to about $135k. So contracting is better in this case using my numbers. It's possible you'll find that there's no clear winner. It comes down to personal preference much of the time.

          L 1 Reply Last reply
          0
          • P pfsWrite

            I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

            J Offline
            J Offline
            jgakenhe
            wrote on last edited by
            #12

            You aren’t going to find a chart on this subject, but I would not choose to be a contractor for just the money; that is short-sided thinking. I see a contractor as someone who has an advantage over typical employees and make more money with no benefits. Also, contractors don’t get stuck in the same place for their whole career; they can spread their wings and grow. If that is your passion, then go for it. To answer your financial question, my suggestion would be to either write a program or create a spreadsheet and take comparable salaries, benefits (medical, life, and 401k), raises, and inflation and determine how much you’d make. This is over your lifetime, not 6 months or 1 year. I have done this for my life and decided contract work would not be feasible after 35 years old. Unless you are a superstar contractor; you’d better expect to be working at Lowe's when you’re over 55 because I just don’t see many older contractors.

            D 1 Reply Last reply
            0
            • P pfsWrite

              I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

              D Offline
              D Offline
              David Crow
              wrote on last edited by
              #13

              I've always used 2048 hours per year. It's not exact, but is close enough.

              "One man's wage rise is another man's price increase." - Harold Wilson

              "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

              "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

              D A 2 Replies Last reply
              0
              • D David Crow

                I've always used 2048 hours per year. It's not exact, but is close enough.

                "One man's wage rise is another man's price increase." - Harold Wilson

                "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

                "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

                D Offline
                D Offline
                den2k88
                wrote on last edited by
                #14

                ...and a power of 2. Being the job we do what it is...

                Geek code v 3.12 GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++* Weapons extension: ma- k++ F+2 X

                1 Reply Last reply
                0
                • P pfsWrite

                  I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

                  R Offline
                  R Offline
                  Ron Anders
                  wrote on last edited by
                  #15

                  pfsWrite! Oh how I remember that one. Go for the contract. You cant buy priceless autonomy.

                  1 Reply Last reply
                  0
                  • G gardnerp

                    I've had to do the same calculations. Of course your results will vary, but maybe this will help: I take 5 weeks vacation. No sick/personal time allowed. Add in 7 holidays and that's 32 days per year. This means with contract I'll just get paid for (5 * 52) - 32 = 228 days. 228 days * 8 hours * $90 = $164160 annually. Now, I would have to pay about 9% in social security, medicare, and unemployment tax separate from what an employee pays (as a contractor). Next, I'd lose a 3% contribution towards a 401k plan. That brings it down to $144460. From here, remove any annual bonuses. Then remove medical/dental/vision benefits. For me that would take it down to about $135k. So contracting is better in this case using my numbers. It's possible you'll find that there's no clear winner. It comes down to personal preference much of the time.

                    L Offline
                    L Offline
                    Lost User
                    wrote on last edited by
                    #16

                    Not really. Contract means you have to renegotiate your job terms every 6 months. Next time you might not be so lucky. No severance etc. Contract means the company doesn't really want to keep anybody around

                    1 Reply Last reply
                    0
                    • J jgakenhe

                      You aren’t going to find a chart on this subject, but I would not choose to be a contractor for just the money; that is short-sided thinking. I see a contractor as someone who has an advantage over typical employees and make more money with no benefits. Also, contractors don’t get stuck in the same place for their whole career; they can spread their wings and grow. If that is your passion, then go for it. To answer your financial question, my suggestion would be to either write a program or create a spreadsheet and take comparable salaries, benefits (medical, life, and 401k), raises, and inflation and determine how much you’d make. This is over your lifetime, not 6 months or 1 year. I have done this for my life and decided contract work would not be feasible after 35 years old. Unless you are a superstar contractor; you’d better expect to be working at Lowe's when you’re over 55 because I just don’t see many older contractors.

                      D Offline
                      D Offline
                      den2k88
                      wrote on last edited by
                      #17

                      Maybe you are used to have companies that actually PAY contractors. In Italy the payment is usually after 60 or 90 or 180 days from the receipt and normally companies simply won't pay. Add the fact that autonomous job has an overall fiscal pressure of about 70% and... well I'd never choose contract work here. It is assured slavery and doom (not the one from ID software though).

                      Geek code v 3.12 GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++* Weapons extension: ma- k++ F+2 X

                      1 Reply Last reply
                      0
                      • L Lost User

                        Nagy Vilmos wrote:

                        2080 hours in a year
                        1960 working hours in a year (10 federal holidays)
                        1920 working hours if you take two weeks vacation

                        So 10 days federal holiday equals = -120 hrs - Which suggests a 60 hr week And then 2 week vacation (10 days) = -40 hrs - Which suggests a 20 hr week. :confused:

                        realJSOPR Offline
                        realJSOPR Offline
                        realJSOP
                        wrote on last edited by
                        #18

                        P0mpey3 wrote:

                        So 10 days federal holiday equals = -120 hrs - Which suggests a 60 hr week
                         
                        And then 2 week vacation (10 days) = -40 hrs - Which suggests a 20 hr week. :confused:

                        You math is seriously whacked. Holidays: 10 * 8 = 80, NOT 120. Vacation: 2 weeks of vacation is 10 days. Again 10 * 8 = 80. Most companies (in the US) allow 15 days of "PTO" (personal time off) to use as you wish (vacation and sick time). This means the "Vacation" category should actually be 15 * 8 (which is 120 hours). so when you take the 2080 value, and subtract 200 hours, you end up with a total of 1880 actual work hours, if the company you work for honors all federal holidays, and most companies only have 8 holidays (for instance, MLK day is generally not recognized as a holiday by civilian companies). Of course none of this matters - at all.

                        ".45 ACP - because shooting twice is just silly" - JSOP, 2010
                        -----
                        You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
                        -----
                        When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

                        L 1 Reply Last reply
                        0
                        • realJSOPR realJSOP

                          P0mpey3 wrote:

                          So 10 days federal holiday equals = -120 hrs - Which suggests a 60 hr week
                           
                          And then 2 week vacation (10 days) = -40 hrs - Which suggests a 20 hr week. :confused:

                          You math is seriously whacked. Holidays: 10 * 8 = 80, NOT 120. Vacation: 2 weeks of vacation is 10 days. Again 10 * 8 = 80. Most companies (in the US) allow 15 days of "PTO" (personal time off) to use as you wish (vacation and sick time). This means the "Vacation" category should actually be 15 * 8 (which is 120 hours). so when you take the 2080 value, and subtract 200 hours, you end up with a total of 1880 actual work hours, if the company you work for honors all federal holidays, and most companies only have 8 holidays (for instance, MLK day is generally not recognized as a holiday by civilian companies). Of course none of this matters - at all.

                          ".45 ACP - because shooting twice is just silly" - JSOP, 2010
                          -----
                          You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
                          -----
                          When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

                          L Offline
                          L Offline
                          Lost User
                          wrote on last edited by
                          #19

                          John Simmons / outlaw programmer wrote:

                          You math is seriously whacked.

                          Not my Maths, Nagys. I was getting my figures from his and pointing out that his subtractions were wrong.

                          1 Reply Last reply
                          0
                          • P pfsWrite

                            I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

                            M Offline
                            M Offline
                            Member 10707677
                            wrote on last edited by
                            #20

                            If you are contracting through an agency, the agency will take care of taxes. If not, find yourself a good accountant. The annual salary takes into consideration FUTA, local unemployment and a few other fringe taxes the employer pays for which, as an independent contractor, you are stuck paying. Is your contracting rate inclusive of sales tax? This is sometimes a pain in accounting as your invoices need to carry sales tax as a separate line item and you need to report this to the appropriate tax agency. Failure to do so can bring substantial penalties.

                            The difficult may take time, the impossible a little longer.

                            1 Reply Last reply
                            0
                            • P pfsWrite

                              I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

                              M Offline
                              M Offline
                              milo xml
                              wrote on last edited by
                              #21

                              By my calculations, a $90 an hour job would bring you home approximately $112,000 after taxes, health insurance, and other deductions (depending upon where you live) if was extended out for the year. The $115,000 would put about $69,000 in your pocket if you got your own health insurance, etc. I use 60% as a general rule for what I put in my pocket from gross after deductions for taxes and the like. Keep in mind that the employer matches what you put in FICA. From the looks of it, you might put as much in your pocket in 6 months as you would working for them for a year.

                              1 Reply Last reply
                              0
                              • D David Crow

                                I've always used 2048 hours per year. It's not exact, but is close enough.

                                "One man's wage rise is another man's price increase." - Harold Wilson

                                "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

                                "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

                                A Offline
                                A Offline
                                adudley
                                wrote on last edited by
                                #22

                                wow man, where do you get that form? here in the uk, we get minimum 20 + 8 days off. hear is how I got it to 1635 hours per year... (7.5 hour working days, we don't get paid for lunch hour :( ) Days in year 365 Bank Holidays, xmass etc. 8 Weekend days (52*2) 104 Full Paid Holidays 31 Full Paid Sick Days 4 Days actually working 218 Hours working 1635

                                D 1 Reply Last reply
                                0
                                • P pfsWrite

                                  I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

                                  K Offline
                                  K Offline
                                  Kirk 10389821
                                  wrote on last edited by
                                  #23

                                  As someone who lives this way, the rule of thumb is 3x. Take the rough salary ($90K/yr -> $45/hr (dividing by 2,000 is easiest)). Charge Triple that -> $135/hr (Roughly. Could be $125 - $150). The 3x is explained as: 1 for the Developer 1 for the Overhead (Your PC, Dev Tools, Paid Leave, Extra Taxes, Insurance, Lunches/Dinners) 1 for the Profit (This is the more "elastic" of the 3, but sets a strict limit on how low you go) So, now that you see where the number is derived. You could easily accept $90/hr. And realize you will have no "profit" in your business. At least at $100/hr, you know you have a 10% profit. I also suggest you setup a company, and use ONE Specific Credit Card for all expenses (and only legitimate expenses) for your business. Pay yourself as an employee from day one. Do NOT live off of the money that comes in (you may find yourself with a $50K tax bill due next year). I use an AmEx. The best $75/yr I spend. My account grabs the year end summary and does NOT waste his time going through all of my little receipts. (The one downside to AmEx is that about 3-5 times a year, I end up having to use a Visa to charge something at some backwoods place that doesnt take AmEx, so your mileage may vary) == Start with that. Then, shorter term work requires a Higher Profit Margin... Longer term work justifies being more flexible. Over a decade at this, and I wish I would have done it this way, DAY 1... HTH, Kirk Out! PS: Also buy a mileage tracker for your vehicle. Another thing I did not do well my first year or two. Over 50% of my mileage is business, so it pays for itself quickly.

                                  1 Reply Last reply
                                  0
                                  • P pfsWrite

                                    I am returning to contract programming after a long time. Forgive my ignorance in this matter. Trying to Google the answer really confused me further. Is there a good rule of thumb to determine at what point does dollars per hour translate to an annual salary? For example, a 6 month job in California pays $90/hour. The same company is offering a salary of $115K/year with NO benefits (no health insurance nor retirement plan) That part comes out of the pay per year. I am thinking a simple linear chart where if I work a certain time (3.2 months) contracting I will earn more. But I am surely missing something: FICA is twice the amount, instability of hours, no vacation time, do I need workmen's comp in CA? I seriously doubt if the company will fold over tomorrow, but it could happen too. Could one of the contractor folks point me in the right direction? I would really appreciate the input. Sincerely

                                    D Offline
                                    D Offline
                                    DumpsterJuice
                                    wrote on last edited by
                                    #24

                                    The one rule of thumb I know, is double your hourly rate = annual salary. so 180,000 compared to 115K, is a no brainer. Take the contract job, and get an accountant to make it work even better for you. For instance - you can probably write off your car, gas and a whole bunch of other things that will more than offset the extra you pay on FICA. The scenario you describe, is really not much of a debate.

                                    Where there's smoke, there's a Blue Screen of death.

                                    F 1 Reply Last reply
                                    0
                                    • D DumpsterJuice

                                      The one rule of thumb I know, is double your hourly rate = annual salary. so 180,000 compared to 115K, is a no brainer. Take the contract job, and get an accountant to make it work even better for you. For instance - you can probably write off your car, gas and a whole bunch of other things that will more than offset the extra you pay on FICA. The scenario you describe, is really not much of a debate.

                                      Where there's smoke, there's a Blue Screen of death.

                                      F Offline
                                      F Offline
                                      Frank W Wu
                                      wrote on last edited by
                                      #25

                                      For short-term contract, like 6 months, you have to count the gap cost between two contracts. You need to negotiate this cost; otherwise they put the money to their pocket.

                                      D 1 Reply Last reply
                                      0
                                      • L Lost User

                                        There is no rule of thumb answer to this question. You need to work that out for yourself. In my decades of contracting I have been asked variations of this question a number of times. I don't know about you specifically but it usually indicates the questioner is not cut out for contracting.

                                        Peter Wasser "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell

                                        G Offline
                                        G Offline
                                        Gary Huck
                                        wrote on last edited by
                                        #26

                                        Rude. I would bet you were lucky enough to find a special niche, decades ago. For a lot of us, it's hard to be a marketer, salesperson and expert software developer all at the same time. But we try.

                                        L 1 Reply Last reply
                                        0
                                        • A adudley

                                          wow man, where do you get that form? here in the uk, we get minimum 20 + 8 days off. hear is how I got it to 1635 hours per year... (7.5 hour working days, we don't get paid for lunch hour :( ) Days in year 365 Bank Holidays, xmass etc. 8 Weekend days (52*2) 104 Full Paid Holidays 31 Full Paid Sick Days 4 Days actually working 218 Hours working 1635

                                          D Offline
                                          D Offline
                                          David Crow
                                          wrote on last edited by
                                          #27

                                          40 hours per week * 52 weeks is 2080 hours per year. So I was 32 hours off; it's still close enough to be able to figure out a yearly salary based on a per-hour wage.

                                          "One man's wage rise is another man's price increase." - Harold Wilson

                                          "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

                                          "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

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


                                          • Login

                                          • Don't have an account? Register

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