Shortest URLs on the Internet
jameswillia.ms
jameswillia.ms
It's run by a character named Vince Cate who moved to Anguilla to protest taxes or something. He was from the US and gave up his US citizenship. He talked the Anguilla government into letting him set up its internet infrastructure for them.
it has a specific version. plz use it.
Very cyberpunk.
(And I checked; ai.security is parked. Very amusing.)
California forever and goodbye!!!
I genuinely want to know what you think is the percentage of FF users who type "ai" who intend to go to http://ai and not search for "ai" is. Even better if you can estimate that for all possible single words that are also TLDs. And then tell me why users who might actually want the domains can't just disable search from the address bar which is a feature FF has which is exactly tailored for this use case. And then also tell me what is wrong with having to explicitly specify "http://<whatever TLD>" which works even when the search-from-address feature is enabled.
The default behavior is also nonsensical if you want to access anything on the local network by name.
> The default behavior is also nonsensical if you want to access anything on the local network by name.
Ok, and what percent of users do you think that affects? And what percent of those aren't technically savvy enough to enable the separate search bar? And what percent of those who aren't under a company managed policy that enables the separate search bar automatically? Let's make some reasonable estimates about those numbers and then reevaluate how "nonsensical" this core feature of Firefox is.
And that right here is the same argument you can make for showing the hand full of remaining Firefox users a "this site requires a modern browser, download chrome here" message. After all the amount of users affected by that is a fucking rounding error.
And yes, I do have the two bars separated.
The address bar is for finding things locally that I know I have like bookmarks. The search bar is for finding things on the internet. It really bugs me that those two very different concepts get merged and conflated in modern browsers.
I say kill the concept of integrated search altogether. Search is a web page and should never be part of a web browser. Ever. It allows web browsers to sell that search bar default setting to the highest bidder. Or if your google, drive traffic to your advertising search engine using technologies that directly benefit its bottom line and nothing else.
Besides, searching sucks. Its all been SEO'd to death meaning finding information posted by real humans who are passionate about a subject are drowned in sea of mediocre (at best) blogspam. Of course this blogspam is funded by google adverts which only perpetuates this feedback loop of madness.
Does Mozilla do that?
Just to get this right. Makes him sound much more reasonable than protesting taxes.
Disclosure: I work for Google.
Some large orgs maintain internal shorteners, like http://go links at Google.
If you set your dns search path to example.com then http://go would resolve to go.example.com which could be your link shortner.
Do you happen to know how Google, or any other places, do this? I assume a custom DNS resolver being forced on clients through a network could do this, or maybe hosts files for each machine.
This often bites people when they wonder why they blow up their DNS servers with traffic from services that contact addresses like "foo.default". With a search path of "search default.svc.cluster.local svc.cluster.local cluster.local" in resolv.conf, the app is actually looking up foo.default, foo.default.default.svc.cluster.local, foo.default.cluster.local, and foo.default.svc.cluster.local, etc. every single time. Hard-code "foo.default.svc.cluster.local." in the app config, and you eliminate requests for the names that can't possibly exist, and save the load (and latency) of handling them.
It appears to have been archived in Japanese, but: https://web.archive.org/web/20120103092225/http://to/
People who discuss the internet publicly generally assume that a TLD implies renting out large numbers of domains to the public. IMO, that is only one potential use.
It seems that the service now redirects to a site called Freenom where you can still get .tk names, but they appear to be priced based on the length and whether or not the domain contains known words or phrases (though some free ones are apparently still available if you don't mind having a gibberish name)
IIRC, anything that isn’t the TLD is a subdomain. It’s just that we typically think of a subdomain as starting at the third-level. So, for this site, news is the subdomain of ycombinator.com, but also, ycombinator is a subdomain of com.
I consider that virtuous, and smart. Short domains must cost more than long domains. They're more valuable. Words must cost more than gibberish. But there were domains available, right? Didn't have to bang out twenty minutes finding something you liked that wasn't taken?
I was also curious about this. It turns out that it's because dig interprets some TLDs as DNS record types (MD, MG, MR, MX) or DNS classes (IN and CH) of the same name! Not sure why, but when given only a type or class (without a domain name), dig actually queries for a list of the root servers, which explains the strange results. Looks like using the -q option to specify the domain name works around this.
From that list, you could use http:// ㎝. / - that's U+339D if HN mangles it.
I wrote it up at https://shkspr.mobi/blog/2020/08/buying-a-single-character-d...
Shorten URLs using invisible spaces
% curl 'http://1.1/'
error code: 1003
% curl 'http://1.1/'
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>cloudflare</center>
</body>
</html> % curl --dump-header /dev/tty 'http://1.1/'
HTTP/1.1 403 Forbidden
Date: Sun, 11 Sep 2022 19:01:53 GMT
Content-Type: text/plain; charset=UTF-8
Content-Length: 16
Connection: close
X-Frame-Options: SAMEORIGIN
Referrer-Policy: same-origin
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Server: cloudflare
CF-RAY: 7492a7924b2bd895-CPH
error code: 1003
With 7.85.0:
% curl --dump-header /dev/tty 'http://1.1/'
HTTP/1.1 301 Moved Permanently
Server: cloudflare
Date: Sun, 11 Sep 2022 19:03:09 GMT
Content-Type: text/html
Content-Length: 167
Connection: keep-alive
Location: https://1.0.0.1/
CF-RAY: 7492a96a181df18a-PIT
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>cloudflare</center>
</body>
</html>[0] https://github.com/curl/curl/commit/56a037cc0ad1b2a770d0c08d...
For this reason, you could use a CNAME setup[0] and instead of using CNAMEs for proxied subdomains, you input 1.1.1.1 A records in your authoritative dns, and everything on Cloudflare's side will still see your hostname in the host header / SNI, and your website will load.
0: https://developers.cloudflare.com/dns/zone-setups/partial-se...
If you want to full details, see [0]
[0] https://daniel.haxx.se/blog/2021/04/19/curl-those-funny-ipv4...
I get the same behavior from other nonstandard ways of specifying 1.0.0.1, like "curl http://01.00.00.01/"
TL;DR: the second "1" in "1.1" is treated as a 24-bit integer.
Longer explanation: https://blog.dave.tf/post/ip-addr-parsing/
Of course, nobody actually does that anymore. But the parser behavior is still out there because there's the possibility that someone is still using it...
> IPv4 addresses may be represented in any notation expressing a 32-bit integer value.
I remember reading a man page that explained this really succinctly but I cannot remember which one it was. A tool like ping I believe.
https://www.freebsd.org/cgi/man.cgi?query=inet_aton&sektion=...
Wow, it actually works: http://127.65530
TIL
I suspect you are confused by n.n.n.0/24 being a network address in a /24 network which is obviously very common. However there are way more networks of other sizes that have .0 addresses in them.
It only requires changes within the LAN to accomplish this, since distant hosts are already not supposed to assume anything about how networks are or are not subnetted. (For instance, they don't know whether you're on a /24 or not.)
You can find some addresses ending a lot of zeroes that already work within
If you're operating a public site and you don't switch to IPv6-only, for example by doing dual-stack, you'll still need IPv4 addresses.
The challenge is that "just switch to IPv6" isn't something that you can do unilaterally if you need to talk to the rest of the Internet.
TIL that dotless record on newer gTLDs is forbidden, which explains my age-old question: "if google holds google., why are they only using it on domains.google? Surely having the url https://google would be desirable for the folks in marketing?". The answer is that they can't possibly because the ban was added precisely because of this.
https://www.google.com/search?q=site%3Agoogle https://www.google.com/search?q=site%3Agle https://www.google.com/search?q=site%3Agoog
You can combine the exclusion `-` syntax with this as well. If you want to find different sites on the TLD `.test` but only URLs on `home.test` are being shown, you can use this search:
site:test -site:home.test
> >>https://s.id/
ifconfig.co
ifconfig.pm
ifconfig.show
ipaddr.in
ipconfig.io
They return plain-text IP address to curl/wget, while serving up a more detailed web page to other web browsers.
Any semi-serious FTP users use dedicated clients.
They needed information from a third party. I gave the accountant the third party's email address, firstname@lastname.co.
The transaction was taking a while to get resolved. After repeated followups, the accountant finally told me that he was having a hard time getting a hold of the third party. Was I sure that their address was firstname@lastname.com?
Like... what the heck. We're all corresponding over email. You could have literally clicked the email address in the email that I sent you. But instead, somehow you've mangled it and are confused that it doesn't work?
That was instructive for me. .com TLDs only going forward!
"No, no. Not everyone has to use Gmail!"
Kinda surprised Linux routes 0.0.0.1 to my router, when used as a destination address. Might be fun to use it as a local redirector whitout having to do any DNS shenanigans.
Edit: yep, it works
Anyone knows a shorter protocol name that is widely supported/known?
dig ai @ googledns works
dig ai @ unbound works (DoT cloudflare behind)
dig ai @ dnsmasq NXDOMAIN (openwrt, forwards to unbound)
Thus something's up with openwrt (22.03.0 release) dnsmasq, or dnsmasq in general.
https://news.ycombinator.com/item?id=32804868
There's a dnsmasq setting you have to twiddle to make it work.
The default is probably due to some concern about leaking misspelled split-horizon local names.
I'm debating if I'll keep it set so that this works, or put it back the way it was.
I'm getting a NXDOMAIN for `dig ai.`, but when directly doing with an upstream server (i.e. 8.8.8.8 or 1.1.1.1) it perfectly works.
I assume this is the result of the `Never forward non-FQDN A and AAAA queries` setting being checked in pi-hole (which is AFAIK the default).
How about: y.uk
An empty hostname is invalid according to RFC 7230:
A sender MUST NOT generate an "http" URI with an empty host identifier. A recipient that processes such a URI reference MUST reject it as invalid.
This requirement also carries over to HTTPS.
irc:// is understood by Firefox at least.
https://news.ycombinator.com/item?id=32801317
17:07:12 vs 17:10:57
great minds, yada yada ;-)
Like aka.ms/mango or aka.ms/inglor?
EDIT: It will also depend on your DNS server apparently. I use Cloudflare’s.