rawTOP
-
Posts
6,070 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Blogs
Events
Gallery
Everything posted by rawTOP
-
Congress has passed, and the President will soon sign, a law that makes anything escort-related illegal. The US no longer differentiates between consensual sex work and sex trafficking. For more about the law, check out this link: https://www.xbiz.com/news/234491/sestas-passage-has-immediate-chilling-effect-on-adult-content-distribution Just as a reference, the entire Craigslist personals section is now completely gone. So, going forward, there is to be no mention of escorts or escorting. No mention of receiving or giving payment for sex. And so on. The only exceptions would be clearly fictional stories in the fiction section, or factual telling of a story involving an escort where you casually mention that s/he was an escort. There was a fairly big and active section on here about female escorts that barebacked. Most of the discussion was about escorts in/around London where escorting is legal. I've had to shut it down. I need your help… Please scour the site and find all non-fiction references to escorting and use the report function immediately under the post to report the post, and a moderator will hide the post or thread if the entire thread is dedicated to the subject of escorting. If the law is ever modified to something more sensible, we can restore those posts/threads. For the time being no infractions will be given for escort-related posts. Then we'll start giving infractions to repeat offenders, and once everyone is aware of the new rules, we'll give infractions like we do with other problem content.
-
Did you bother reading my message above? It's explained there. If you come back with a question that shows you read that message, then we can discuss further. But I'm not going to repeat myself to people who are too lazy to read the last few comments in the thread.
-
OK. I think most of the problems have been resolved. Chat should now work properly on mobile as well as desktop. A few caveats (things that will probably never get fixed)… If you're using ad blocker software that blocks browser fingerprinting, you will never be able to get into chat. This is not something I intend to fix. If you keep getting "your browser can not be identified" errors – there's a good chance that's what's happening. But if you can eventually get around those errors, then ad blocker software isn't the problem. Sometimes the session cookies here on the forum are stale and so your login can't be validated by the chat software. This is the "GET.ips_sess_id was blank" error. The only solution is to reload the page you're looking at on the forum, and try to click again. This is not something I think I can fix. And honestly, session hijacking is a thing and I wouldn't want to loosen security to fix it since it would open you up to potential session hijacking. In general reloading the page you're looking at on the forum (or going to another page), and then clicking on the link again is the best way to get chat to work if you have a problem. If you consistently have the same problem over and over and you feel it's a reproducable bug, please respond with the details of how I can see the same error you're seeing. I need to know things like how long since the page you're looking at was loaded, and the exact error message you see and whether there are steps you can take (like described above) that finally let you get in.
-
The makers of the old chat software shut down the service. Going back to it is not an option since it no longer exists. Background refresh only happens when the window is "active". It doesn't happen when you go to another tab (and possibly if you go to another application). Give it about 5 seconds after you return to the tab for it to refresh. I will eventually get to 1-on-1 chat. It will work just like group chat only it will be between two people.
-
Yes, it's a caching issue. I think I've resolved it and it shouldn't happen anymore. If it does, report it here (more details the better so I can figure out where the caching problem is in my code) and then try again and it will probably work. The other problem is with mobile devices. I know what needs to be fixed, it's just the developer of this site didn't make it easy for me. So I'll keep trying until I get it. The short explanation is that the nav bar exists twice in code – once for desktop and once for mobile. I was only changing the desktop version, not the mobile version. But changing the mobile version is more complicated – so when I figure it out mobile users will be able to use chat.
-
Just a note… I won't be getting back to work on the remaining issues until next week. In the meantime, try turning off any ad blockers that might be overly aggressive. Chat needs something to run called a browser fingerprint. It's how I confirm you're you when I pass your credentials from this site to the site is running on. I've seen an ad blocker block the fingerprint script since it's often used to track people across websites. There are good reasons for tracking across websites and bad reasons. I think I use it for good reasons, but your ad blocker assumes I'm using it for bad reasons. This problem with ad blockers is not something I'll be fixing (since it's a self-inflicted problem). But I will look into other possible problems next week.
-
So it seems chat is working pretty well now. The problems most of you posted were probably due to the browser remembering temporary redirects or there being some weirdness stored in a cookie or something that needed to be corrected. If anyone has continued problems with chat, let me know.
-
I believe that's a caching issue. If you'd tried a few minutes later it should have worked. I've put the cache period down to 1 second, that should take care of it. If you (or anyone else) continues to see that problem, let me know.
-
OK. I think I just figured out the problem(s). Somehow I had managed to delete a small line of code and didn't see the omission even though I looked at it 1000 times over the past 4 days. There was also a problem with certain browsers and validating their version numbers (something I do to try to stop hackers). And there was the problem with + signs in one of the pieces of data (something I had suspected early on). But the good news about working on it for so many days is that I found and fixed a few other problems in the process. I don't have time to test things properly. My two test cases are working, so all I can say conclusively is that it's working better than it was. It's the end of the day and we have a guest coming over in an hour, so I'm gonna quit there and do some cleaning. Please let me know if you continue to have problems and what the exact error messages are. Also, please copy the URL from the error page. I have some extra debug code in there that I don't have on the page. Again, sorry for the down time. Trust me, I've been really frustrated about not being able to get it back up quickly.
-
Well, I fixed the data problem. Haven't figured out the cause of that problem yet. And it did not fix the chat login problem. It's the end of the day. I'm frustrated and stopping. I'll pick it up again in the morning. Now I have to figure out if I wanna go out cycling (my new way to release energy) or if I want to have a drink. My boyfriend will probably suggest combining both and cycling to a bar
-
Well, I found a potential source of a problem. Unfortunately it's a data problem (some duplicate records) and data problems take longer to fix than code problems because I first have to write code to fix the data problem, and then prevent the problem from happening again, and then have to find the flaw in the code that created the duplicate records. And then I have to see if that's the source of the current problem. So clearly that means I need more time. Not certain it will be done before I quit today, but we'll see. Maybe… By the way… Sorry this is happening. It's sorta just bad luck that it showed it's head right before a weekend. If I had seen it quickly I would have rolled back to the old code. But I would have needed to resolve this problem eventually…
-
There's a problem with chat? Really? I had no clue! Maybe I should have read this thread… Yeah, that's sarcastic, but yes, I know there's a problem with chat. I worked on it all day yesterday. Only stopped when a woman down the block dragged me to a community meeting. I know the nature of the problem. Just trying to figure out exactly why and when it's happening.
-
It's the morning and I'm back at it. Those error messages are helpful. In particular, 3 of the 4 hashes didn't contain + signs. So that means the problem is something other than what I thought it was. Now to figure out what the problem really is… Can't say how long it will take. Could be 5 minutes, could be 5 hours, could be (parts of) 5 days…
-
That is exactly how it it supposed to work. You can't go to chat until the word Chat shows up.
-
It's 7pm. I'm frustrated I can't get the 2nd of my two test cases to work. So I'm stopping for the evening and will pick it back up in the morning. But some of you are able to get into chat. Anyone that is continuing to have errors, please post them here (unless they're just like someone else's error). In particular, my test case that fails throws an error something like this: IMPORTANT MESSAGE: Invalid Login Hash IElcA5aTNnogzWOGu3+gHI/R9yVTWsjYSOSGzI/qHRw= Let me know if you see anything like that (or anything else).
-
I think I'm closer. Now I'm seeing a problem with the authentication keys I'm passing after you're logged into the new system. If they contain a + things don't work. So let me work on that now. But those of you lucky enough to not get a + in your login hashes should be able to get in right now.
-
My comment just above yours answers your question.
-
I have something else I'm gonna try. So give me a half hour or so… [A few of you can get into chat (including me), but not everyone. I think I know why…]
-
If anyone is still seeing this error, please let me know. I've made some changes, but I may not have fixed what's causing the problem, so need to know details. UPDATE: The fact that I'm the only one in chat right now makes me think something is wrong. But there were some guys who got in a little while ago…
-
The short version of a long explanation is you now have to wait for the check of how many people are in chat before you can go into chat. I've changed it so there's just a . while those stats are loading. When they're loading it changes to "Chat". At that point it's safe to click.
-
Sorry for the delay. Everything worked when I tested it, but then I took the weekend off. Unfortunately as soon as there were zero people in the chatroom things failed because it tested to see if >0 were in there to do something critical. I've changed it to >=0 and now everything should work. ronetbus – I'm not sure the problem you reported is the same problem, so I'll look into that next.
-
IM and chat are on completely different systems. I can't really answer too many questions about code I didn't write. So don't know the answer to your question.
-
lol. That sorta describes a forum thread like this one. Or are you looking for something between or where you can browse more of what went before in the thread? Anyway, chat is back up and running. If you're wondering I was working on a common logon system for my sites today. And I'll continue work tomorrow. Things aren't fully functional yet. How this sites interacts with my new sites will always be a bit odd. But that is what it is. One thing that can go wrong this evening (I'll work on it tomorrow), is that you session on this site needs to stay active for chat to work. That means you may need to come over here and do a page refresh or something every 20 or 30 minutes or else chat may stop working for you. I'll work on that tomorrow. Basically everything you do on chat this evening is doing a new login to chat. And that requires the session cookie on here to be active. The way it used to work was there was a separate login into chat with a separate cookie. I changed how my cookies work, so that login doesn't exist right now. I'll figure out how to make that happen tomorrow.
-
Please read the previous messages in the thread before posting.
-
That's not my code, so won't be improving it. In a few years I'll replace it completely with my own code. In the meantime you just gotta deal with what you've got.
