885 karma · joined May 31, 2017
davchana.at.hn
Long time ago I came across very similar concept in use in India. Not much, but visible usage. I also came to know by looking at a sticker on car windshield.
Not true always. Often I see them sorted alphabetically by Destination, then time (in west coast US). Or occasionally (in middle east) by Airline Name & then Time. All Qatar Airlines together. Sometimes even whole LCD Labeled (digitally, on screen) as A-E, F-M etc. and a bit frustrating way, because often I know my flight destination, but not precise time (& sometimes time shifts around), sorted by pure time.
Its like you put a lock (NS) on your box (Domain). After few months you don't care about that box anymore and leave that key in the wild. Anybody can pick that key and use the box. The box holder (domain registrar) can't make you verify that you are the original owner 'by' asking you to open the box, because by default, anybody who has key, can open the box. The correct way & responsible way is to destroy the box (delete the domain) or at least destroy the key (unpoint the third party NS records).
Hosting company can not "give" the domain to anybody. If domain is still pointing to Hosting with NS records, anybody could make an account at Hosting, and add that domain. Now that scammer controls whats visible at Domain, but he is not yet the owner of domain.
Owner is who control and can change NS records. Scammer can change all other records, but not NS. NS is at original domain registrar. Original owner can very easily change the NS and cut the scammer out of everything (& should).
Gitlab used to be like this. You add a domain to Gitlab. You add an A record to your domain registrar or NS Manager. Now your domain shows your Gitlab Page. After few months, you don't want the pages anymore. You delete the project from Gitlab. You ignore to delete the A Record. Scammer adds that domain to his Gitlab, and shows his content at your domain.
Now Gitlab asks you to add a verification TXT record when adding any domain. Scammer's veri record is different. He can't prove that he owns the domain.
I want my domains at dynadot or namecheap or hexonet, but want CloudFlare to manage all DNS. CF doesn't support al ccTLDs.
What users would do is, add DNS records to their DNS Manager to point their custom domain to Gitlab Pages, later will delete the Gitlab pages when not wanted any more. Scammer will simply point that same domain to his fake repository, thus hijacking customer domain.
Gitlab then made customer add a Txt Record for verification of domain. Scammer's txt record value is different from customer txt record, scammer can't modify DNS records.
This post was my inspiration:
30 days so that I can have enough time to delete it. Trash & Spam is excluded, and every successful downloaded email is labeled to prevent it getting downloaded again in next run.
Originally 4 years ago when I started this script, it was timing out because of about 15 years of emails. I ran it for 6 minutes only, every hour. Now once it caught up, it needs only few seconds, and there are only like 5 to 20 emails caught in its daily net.
This is not a corner case (SSN required, not card). I would say its more like 90%. Since 2021 nobody needs proof of SSN, they just need the SSN number itself.
To quote CA DMV website:
> Applying for a REAL ID requires proof of identity, proof of California residency, and a trip to DMV. You will be asked to provide your Social Security number on your REAL ID application (exceptions may apply).
https://www.dmv.ca.gov/portal/driver-licenses-identification....
Not every REAL ID holder is a citizen & thus eligible to vote. Real ID needs only proof of legal status (citizen, permanent resident, tourist, work permit, study vis etc) and address.
I remember texting a lot while phone is under the table, or simply in pocket.
Some other models (not F91W) does track year.
To be fair, it doesn't ask for year anywhere in settings. It simply doesn't know what year it is.