Jump to content

mygoditsfullofstars

Resident
  • Posts

    71
  • Joined

  • Last visited

Reputation

102 Excellent

Retained

  • Member Title
    Pork Chop

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So you know what the overall cost would be for every person who wanted to have it on their parcel/region plus all the traffic in and out of the region that connected and listened to the stream? Unless you are LL's accountant and can see the books, you cant sit there and say they are rolling in money and can afford it, none of us are privy to LL's financial position.... Why should LL pay for it? Lets assume for arguments sake LL decided to do this, do you really think that expense wouldn't trickle down the pipe to somewhere else in the form of higher fees for land, currency transactions etc?
  2. Assuming is it a specific network carrier that's at fault, traceroutes (if enough of them are supplied), might help in identifying which one it might be (ie: comparing a bunch of traceroutes provided by people having problems against users in similar geographic locations who are not having problems). Whether anything can be done about a problematic intermediate network carrier is another matter entirely, depends on where along the path they are, if its something within Amazon or one of their upstreams its likely Amazon can get it resolved. If its a carrier beyond that boundary then all I can say is "good luck" since it would require sending an email to the NOC of that carrier (who most of the time don't respond to emails (based on my past experiences when in such a situation)). Its also possible this problem will just go away on its own if its a network carrier who is aware of the problem and is currently working to resolve it. Anyway I might be completely barking up the wrong tree with it being a specific intermediate network carrier being the issue, but is a plausible theory.
  3. UDP packet loss also wouldn't explain login issues (where some people are having to try 20 or more times before they can log in) since all of that most certainly is TCP (during the initial authentication stage).
  4. Traceroute, while handy in some scenarios shouldn't be considered a definitive guide as to the health of a network path. By default, traceroute uses ICMP. Many layer 3 devices (routers, firewalls) drop ICMP traffic (or can even de-prioritize it under certain network conditions). UDP is session-less, and UDP data not being returned could mean it is being lost literally anywhere along the network path, it doesn't necessarily indicate that the simulator or server itself is hosed and is not sending any traffic back.
  5. It has also been hit and miss for some people rather than constant - could it just be pure luck that the other machine worked when tested (ie: is it consistently able to log in and out and tp around with no issues?)
  6. It might be interesting to know whether or not if any of the affected people are using VPN's (some AV software like Norton, and I am sure there are others also includes a VPN service that runs in the background, often without the end users knowledge its even rerouting their network traffic).
  7. I am unaffected too. Using Linux here. Unsure if there is any pattern to operating system/os version. Looking at the data in this thread so far, it doesn't appear to be Country or ISP specific. It could be a problem with an intermediate network carrier somewhere along the network path into Amazon that's having issues and those who are unlucky are being routed via that carrier.. Anyway pure speculation on my part - it will be interesting to see what it actually is.
  8. If you are having the same symptoms as others in this thread, it is not Firestorm related (please read through the thread, you will find it is effecting other viewers too)
  9. Hello, that wont be the reason The dullahan binary shipped with official firestorm builds is safe, sometimes, certain antivirus software flags it as suspicious incorrectly (these are known as false positives). Cloudflare blocking can happen for a variety of reasons, but I wont go into them here, it will turn into a trainwreck of a thread if I attempt it (just like the last thread did).
  10. Its hard to stay inspired when all I face is aggression, baseless accusations etc. I am actually someone that's in a position to be helpful with a wide range of issues. I've offered an avenue for people to reach out for contact if they are facing Cloudflare issues but I just get shat on for even offering.
  11. Wow hostility much? I am not even remotely interested in your computer and was not offering to make any changes to it or suggesting that you do. I was offering to look at the Cloudflare logs on my end to see what might have caused the block, but carry on being hostile Have a nice day.
  12. If switching web browsers fixed it, then you can probably rule out your IP address as the issue. More than likely your other browser has some grudge with Javascript or certain types of Javascript. If you have the Ray ID of the block page I can confirm what it was, but do this in DM please if you want me to have a look, I don't want another round of what went on in the other thread here.
  13. Like I said, most web browsers warn users about enabling strict security settings, there are some pitfalls to doing it, and its not just our domains that users who enable strict security controls will run into issues with. To expect every network/site operator to just bow and cater to every need is ridiculous and unrealistic. There are some who even go as far as to completely disable Javascript on their machines and expect everyone to bow to their needs and not have anything that requires the use of javascript. It never ends, cant please everyone... In most cases, those who are "locked out" as you put it can work around it easily in most cases, but see if I elaborate on that, you will just use that to start another argument..
×
×
  • Create New...