Q. Do you provide trials or review memberships?
A. We provide a premium service, we don’t provide trials or review memberships, but we stand by our 3 day money-back guarantee.

Q. How many IPs do you have?
A. We have more than 9M+ active IPs every month from all over the world.

Q. Do you have US IPs?
A. Yes we do, more than 2M+/month, and yes we have IPs from Vietnam, UK, Indonesia or any other country you can think of.

Q. Do you have datacenter proxies?
A. No we don’t, we have only real residential proxies.

Q. Do you have city targeting?
A. For the moment we offer only country targeting.

Q. What is the IP rotation time?
A. The minimum rotation time is 5 minutes, you can choose rotation times up to 60 minutes.

Q. How many authorised IPs do you allow?
A. Up to 100 ports we allow 10 authorised IPs/proxy port package, over 100 ports we allow 100 authorised IPs.

Q. Does the discount apply to all my proxy port packages?
A. Yes, if you open up new proxy port package you will benefit from the same discount rate, just ask for a new coupon code.

Q. Do you charge VAT?
A. We are a legitimate business, so have an obligation to charge VAT in the countries where prices are subject to VAT.​

Rotating TLS Certs used with Public key Pinning

I have an app which connects to an API. The API TLS certificate is about to expire and we are using Public key Pinning.

How do I rotate the certs without disabling access to our users?

When rotating certs; can I change the private key without changing the public key? I assume no as they are a key pair. Can someone confirm?

What would be the point of rotating the cert only to update the expiry date? Surely someone investing sufficient time to compromise the private key can continue to do if only the expiry date variable is changed?

I understand if it coming close to expiry I should update the cert to prevent unavailability of the service but then is it recommended to have a long expiry date on the next rotation?

When keys are rotated (say I leave the public and private key the same); is there anything mathematically or from an encryption perspective that changes if only the expiry date has changed?

Prevent sprite from rotating with camera

I am creating a small 2d game and looking for a way, to prevent certain sprites from rotating with the camera.

I could not find any settings that would allow me to do so, so my next best guess would be, to do that in a vertex shader. Since my knowledge on shaders and math is quite limited, I could not figure out a way to accomplish that, either by rotating it back after all default transformations are done or setting the skip_vertex_transform flag and transform the vertex without rotating it.

Another option would be, to manually set the angles for each object individually, but I feel like that would not be the cleanest option, since there can be quite a few sprites on the screen that would need frequent “counter rotating”.

Rotating squares animation

enter image description here

I want to generate an rotating squares animation like this, my code only workd for 3×3 squares, how can I expand to more squares ( (2n-1) × (2n-1) )?

pts = {{0, 0}, {1, 0}, {1, 1}, {0, 1}};  Manipulate[Graphics[{    EdgeForm[Gray], LightGreen,    RotationTransform[θ + Pi/2, #]@pts & /@ pts // Polygon,     LightRed, Polygon[pts],    TranslationTransform[RotationTransform[θ + Pi/2, #2]@# - #]@pts & @@@      Partition[pts, 2, 1, 1] // Polygon    }, PlotRange -> {{-2, 3}, {-2, 3}}], {θ, 0, Pi}] 

enter image description here

CloudProxies.com – 20000+ Rotating Public & Private Proxies – Instant Setup


Fast Quality HTTP & SOCKS5 Backconnect Proxies
With Instant Setup
Get Unlimited Access to 20,000+ Public and Private Proxies
– Super fast servers
– HTTP & SOCKS5 Proxies
– Unlimited Bandwidth
– USA EU ASIA WordWide Proxies
– Multiple subnets
– Instant Delivery
– These proxies will rotate to a new proxy every 3-10 minutes
– GEOlocation Filter
– China Proxy Filter
– 4 Access IPs.
50 Backconnect Ports – $ 50
100 Backconnect Ports – $ 100
200 Backconnect Ports – $ 180
Special Price for GSA members: 30% OFF Lifetime
Please post “I want 30% Coupon Code” in this thread and I will send code to your PM Inbox.
If you have any other questions, don’t hesitate to contact us!
Email – contact@cloudproxies.com
Support – http://cloudproxies.com/billing/helpdesk/
Refund Policy
We offer 48 hours money back guarantee on your first purchase, so you can test our service.
>> Visit >>CloudProxies.com<<

The screen will cause Z distortion after rotating

After screen rotation, the screen display will cause Z distortion when playing video or quickly switching photos.

We tried several monitors. ENVIRONMENT: Display = HDMI/DP Resolution = 1920x1080p / 1920×1920 OS = Ubuntu 18.04, Kernel 4.18.20 Platform: Intel Apollo Lake N4200

STEP: 1. System boot up 2. Rotation display to left/right/inverted 3. Play video

rotate to the right, Z distortion happen

$ xrandr -o right

rotate to the upside down, Z distortion happen

$ xrandr -o inverted

rotate to the left, Z distortion happen

$ xrandr -o left

rotate to the normal

$ xrandr -o normal

RESULT: screen will cause Z distortion. see the recording video below: https://drive.google.com/drive/folders/15oDuXqsMn8Q-39K8StbfkuBeL_CWF584?usp=sharing

Is rotating developers on a project a good or bad idea?

I’m working on a small team that will begin working on a large new project with another small team. The other team is currently working on a legacy system that they have been working on for years.

The manager has decided that the developers from my team will be rotating every few months to replace developers working on the legacy system. That way the other team will have a chance to work on the new project and have a better understanding of the new system.

I want to know the benefits and drawbacks (if any) of rotating the developers from the project every 2-3 months.

I know that this is a similar question to “Is rotating the lead developer a good or bad idea?”, but that question focuses on a lead developer. This question is about rotating the entire team on and off the project (tech. lead for the new project may or may not be rotated — I don’t know yet).

Strategies for Rotating MYSQL Encryption Keys

I have a web app that connects to a MYSQL database which has some encrypted data in it. The encrypted data is encrypted using the the mysql AES_ENCRYPT function and a key.

Now, this key has been static for a while, and we’re looking at methods to change the key (and ideally change the key periodically). My problem is that I have about 20 million records that are encrypted with this key. So I need to decrypt them, re-encrypt them in with a new key, and save them off again, with minimal downtime for the server.

I’m thinking, I could run 2 databases in parallel, and have a separate process copying over the data with a new key (and somehow making sure records are in sync) and once it’s done, switch to the alternate database. But, this would take a really long time, and would be a pain to run anytime we want to change the key in the future. I’m also wondering if there’s something clever I could do at the web app level.

I’ve looked for other column-level encryption methods to make key rotation easier in future key changes, and haven’t seen many options. I’ve looked at encrypting the entire database with mysql data-at-rest encryption (and I might implement that too), but I’d like reads from root and mysql users to be encrypted as well for an extra layer of security.

Anybody have any ideas, or any experience with this kind of thing? I’m sure other people have had this same problem but haven’t found anything online.

Sticking to a working proxy generated by a rotating proxy script

I’ve created a script in python to make proxied requests by picking working proxies from a list of proxies scraped from a free proxy site. The bot traverses few links to parse the urls of the different posts from a website. The script however uses a new working proxy every time it makes a new requests as there are multiple requests to make.

At this point I’ve rectified the logic within my script in such a way so that the script will first check whether the existing proxy is still working in making new requests. If it is still a working proxy then the script should stick to it otherwise It will pick a random one from the list to go on.

The logic to reuse the same working proxy in multiple requests (until it is invalid) is defined within this start_script() function.

The script eventually has got a weird look. I suppose there are rooms for improvement to make it more concise and less verbose.

This is what I’ve created so far (working one):

import random import requests from random import choice from bs4 import BeautifulSoup from urllib.parse import urljoin  test_url = 'https://stackoverflow.com/' #It is for testing proxied requests base_url = 'https://stackoverflow.com' main_urls = ['https://stackoverflow.com/questions/tagged/web-scraping?sort=newest&page={}&pagesize=50'.format(page) for page in range(2,5)] cbool = False usable_proxy = None  def get_proxies():        response = requests.get("https://www.sslproxies.org/")     soup = BeautifulSoup(response.text,"lxml")     proxies = [':'.join([item.select_one("td").text,item.select_one("td:nth-of-type(2)").text]) for item in soup.select("table.table tr") if "yes" in item.text]     return proxies  def get_random_proxy(proxy_vault):     while proxy_vault:         print("trying to get one----")         random.shuffle(proxy_vault)         proxy_url = proxy_vault.pop()         proxy_dict = {             'http': proxy_url,             'https': proxy_url         }         try:             res = requests.get(test_url, proxies=proxy_dict, timeout=10)             res.raise_for_status()             return proxy_url         except:             continue  def start_script(url):     global cbool     global usable_proxy     if not cbool:         proxy = get_proxies()         random_proxy = get_random_proxy(proxy)         if random_proxy:             usable_proxy = {'https': f'http://{random_proxy}'}             urls = make_requests(url,usable_proxy)             cbool = True             return urls         else:             return start_script(url)     else:         urls = make_requests(url,usable_proxy)         if urls:             return urls         else:             cbool = False    def make_requests(url,proxy):     try:         res = requests.get(url, proxies=proxy, timeout=10)     except Exception:         return start_script(url)     print("proxy used in requests:",proxy)     if res.status_code!=200:         return start_script(url)     soup = BeautifulSoup(res.text, "lxml")     return [urljoin(base_url,item.get("href")) for item in soup.select(".summary .question-hyperlink")]  if __name__ == '__main__':     for url in main_urls:         print(start_script(url)) 

Is this rotating cube interface user-friendly?

I’m working on a prototype for an innovative form interface, where different parts of the form are shown on different sides of a cube. The cube rotates, and the user can fill it out as the cube spins. Here is a working example:

enter image description here

To me, it seems like a pretty robust solution to our problem (i.e., before, our forms took up too much space on the page and were extremely boring), and it feels pretty usable to me, but this approach may have some user-experience problems I don’t know about.

Does this seem like a user-friendly model? If not, what can I do to improve it?