doneHey,
sadly i dont see any msg from you. Could you send me a pm here with your account email and i take care of it.
I have sent you
doneHey,
sadly i dont see any msg from you. Could you send me a pm here with your account email and i take care of it.
Payment received. Always fast via BTC![]()
It's weird, I made a withdrawal on 2/5 and I haven't received it yet
Hallo,
@Streamtape
Waiting payment via WM
Hello! I have low ad mode but I got like 5 ads in the beggining and they keep coming! I read that low ads mode only has 1 popup and 1 notification so what is happeningHey,
WM is done by our exchanger i will write him to speed the process up. But as always you will get your money![]()
Yes, the ads are very aggressive lately. In low ad mode, in addition to the pops I see a notification ad sometimes and two more banners to be closed.Hello! I have low ad mode but I got like 5 ads in the beggining and they keep coming! I read that low ads mode only has 1 popup and 1 notification so what is happening
@Streamtape , Can you make the downloads a little faster? The files are downloading very slowly.
Hi, question:
Cloudflare seems to prevent the embeds from loading.
In firefox I get
![]()
The user panel cannot be refreshed either without CF checking all the time. Otherwise error 400.
Can this be optimized please? Thanks.
Hey, just tested it with firefox embedd and user panel, both worked.
Please check if you dont have addons running like noscript.
Hey, just tested it with firefox embedd and user panel, both worked.
Please check if you dont have addons running like noscript.
That's probably because the Cloudflare challenge cookies were already set when you tested it, or you were testing it from a whitelisted IP or something. If you try it in a clean private browsing session from a domain that isn't streamtape you'll see that same error because the CF challenge page returns a 503 HTTP status. This is standard Firefox behavior and is unrelated to plugins. Usually you'd exclude embed pages from the challenge for this reason.
Thanks for the explanation we made some adjustments and it should be fixed now.