Vote for BP.Net for the 2013 Forum of the Year! Click here for more info.

» Site Navigation

» Home
 > FAQ

» Online Users: 621

0 members and 621 guests
No Members online
Most users ever online was 47,180, 07-16-2025 at 05:30 PM.

» Today's Birthdays

None

» Stats

Members: 75,916
Threads: 249,118
Posts: 2,572,199
Top Poster: JLC (31,651)
Welcome to our newest member, Wilson1885
  • 06-05-2014, 06:46 AM
    Bluebonnet Herp
    USFWS to Re-open Public Comment on Boas and Pythons
    I'm not a huge fan of USHerp but they're my only lead for now.


    Quote:

    The US Herpetoculture Alliance has just learned that US Fish & Wildlife Service (FWS) has given notice to the Office of Information and Regulatory Affairs (OIRA) that public comment on the Constrictor Rule will be re-opened. Although positive news, the Herp Alliance believes this action to be a clear signal that FWS is prepared to finalize the Constrictor Rule that was finalized in part on January 23, 2012 (77 FR 3330)– adding 4 species of constricting snakes to the Injurious Wildlife List of the Lacey Act. Any species listed on the Injurious List cannot be imported into the country nor transported across state lines without a special permit from FWS.

    In January 2012 FWS published a rule in the Federal Register that added the Burmese python, northern African python, southern African python and yellow anaconda to the Injurious Wildlife List of the Lacey Act. The Constrictor Rule accounted for 4 of the 9 snakes originally proposed for listing. The remaining 5 snakes, Boa constrictor, reticulated python, green anaconda, DeShauensee’s anaconda and Beni anaconda were not listed at that time, but remained “under consideration.”

    FWS has now given formal notice to OIRA that is is prepared to move forward to finalize the rule adding Boas, Retics and 3 anacondas to the Injurious List. Although FWS has announced to OIRA that they will re-open public comment on the Constrictor Rule, they have not indicated when it will re-open, or for how long. Details will be published in the Federal Register. Herp Alliance expects it to be very soon.
    Spread thou wordeth!


    http://usherp.org/2014/06/04/fws-to-re-open-public-comment-on-boas-and-pythons/
  • 06-05-2014, 07:37 AM
    Skiploder
    USHA is led by a liar and a scammer. If you pay him attention and link to him, you allow him to continue to exist.

    In the past, that liar and scammer's "news" breaks have been nothing but thinly veiled jabs at his perceived rivals. They are his stock in trade. (Well, Along with trying to run illegal background checks on this enemies and posting lies about them.)

    As in all USHA statements, the details are hidden among all the BS. In this case, the last paragraph states it all:

    "Although FWS has announced to OIRA that they will re-open public comment on the Constrictor Rule, they have not indicated when it will re-open, or for how long."

    In other words, the reason why USARK and other groups haven't said anything is there is nothing to be said. When public comment has a re-opening date, then USARK will post it. Until then all USHA is doing is posting rumors.

    All USHA does is post cute pictures on their Facebook page, buy likes from Mexico City and Indonesia and take swipes at USARK on their web page. Let this be the last that anyone on this site posts reference to Bozo the Wyatt and his farce of an organization.
  • 06-05-2014, 08:06 AM
    Bluebonnet Herp
    Honestly, I'd like to know where this buffoon gets this stuff. Obviously, hysteria is already being assumed on forums elsewhere.
    In the mean time, I'm still a rather unaware bystander floating around, trying to find what I can make of things with what I can get, so I suppose I'll just sit back and watch things play out for now to see. Always appreciate your insight though, Uncle Skippy!:)
  • 06-05-2014, 09:56 AM
    bcr229
    Re: USFWS to Re-open Public Comment on Boas and Pythons
    If public comments are ever re-opened then the notice should be available at http://www.fws.gov/policy/frsystem/default.cfm
Powered by vBadvanced CMPS v4.2.1