> BGP is the protocol that gives the Internet its shape, and you can’t directly speak it yourself.
It's actually surprisingly easy to get an ASN for yourself and speak BGP. If you find building something like this tool interesting, you should give it a try. I wrote an introduction of sorts earlier (https://qt.ax/asn) if that interests you.
You don't actually need an ASN to get PI though? You can use PI just fine with BYOIP. Actually... I don't think you are even required to announce them on the Internet.
You need the coöperation of the ISP(s), but what you can do is get PI space, run BGP on your router, and use a private ASN (64512-65534) to advertise to your ISP, and then your ISP advertises to the world with their ASN.
One common scenario is two links to the same ISP, so everyone knows which link is active (you can do active-active (load balancing/sharing), or change weights or local preference for active-passive):
The whole BGP process with a private ASN that the ISP strips out and replace with their own ASN on the Internet is how "BYOIP" (bring your own IP) usually works.
Note that ARIN NRPM 4.10 now requires the requested range to be used exclusively for IPv6 transition and not anything else.
As for full table, several providers I recommended in the original post are able to do a full table for less than $10/month. You can also join an IX and ask nicely for transit from other members. Some may even offer you free transit the moment you join.
4.10 still allows dual stacking core services like DNS but it is intended for NAT64 type deployment for other things (which I'm a fan of anyways! I'd encourage anyone to look into it while waiting for a different assignment, it's really quite good)... that said they are never going to be able to tell if your usage is from NAT64 or raw clients, not that I would condone lying in your application.
Thanks, I'll poke around a few and see which looks best! A bit more than Vultr but well worth it for a full table.
I am curious which leap day system you use for the French Republican calendar. Most popular versions of the calendar I see floating around just use the Gregorian leap year system, which I don't like because it yields the wrong results in the year the calendar was in use. Yet, I don't see mental math as a viable option when using the original date-of-equinox method used during the revolution.
It's not an easy thing; frankly, if I have to back convert to prior times when the Calendar was still in use, you have to just swallow the pill
However, if using the calendar in day to day life, the Revised System is much easier.
To quote Wikipedia:
leap years being every year divisible by 4, except years divisible by 100 and not by 400. Years divisible by 4000 would also be ordinary years. This calendar also has the benefit that every year in the third century of the Republican Era (1992–2091) begins on 22 September.
It's actually using setTimeout. Every time the callback fires, it calculates exactly how many milliseconds it would take before the next second arrives, and schedules another timeout exactly that many milliseconds later. This is done separately for both decimal and 24-hour time to ensure the most accurate time is shown.
I believe this avoids the weird issues with setInterval but does not use as much CPU as requestAnimationFrame.
I made a decimal time clock here https://github.com/wegry/decimal-time where I used `requestAnimationFrame`. Admittedly, it probably uses more CPU than it should.
> In this Fiddle, you can clearly see that the timeout will fall behind, while the interval is almost all the time at almost 1 call/second (which the script is trying to do). If you change the speed variable at the top to something small like 20 (meaning it will try to run 50 times per second), the interval will never quite reach an average of 50 iterations per second.
Thanks for reporting! I didn't notice since I always navigated directly to the page while testing, but it is rather annoying when linked. I just pushed a fix.
The original French Republican Calendar determined the start of the year with the date of the autumnal equinox at the Paris Observatory. This made the calendar somewhat unpredictable, as it required a lot of astronomy to figure out the start of the year (and thus whether the previous year was a leap year). These days, it's common to see versions floating around with the same leap year rules as the Gregorian calendar instead of the original rules, leading to weird cases like having the wrong leap years compared to what happened historically.
I got nerd-sniped into making a calendar following the original rules and tried to see how far I can push it with modern astronomy, and this is the result.
Yes, desktops with two PCIe GPUs is actually the more common use case. As for dummy plug, it's most likely need to convince windows to turn on the GPU when you are not plugging a monitor.
The default was chosen as 4 words due to usability concerns with longer passwords or more obscure words, but it is adjustable. The strength meter is yellow at 4 words to indicate the less-than-optimal entropy, but I felt it was better than turning a new user off by making it too hard to remember. But that's a decision I plan on revisiting.
If you are security conscious, you can save a more secure default for yourself (in local storage, nothing is ever transmitted to a server).
I would recommend the default be 6 words, and let people choose down to 4, but not lower. At last that way, users know what a "secure default" looks like. Granted, it breaks the four-word "correct horse battery staple" XKCD format, but Randall was in some error with that comic anyway.
It's actually surprisingly easy to get an ASN for yourself and speak BGP. If you find building something like this tool interesting, you should give it a try. I wrote an introduction of sorts earlier (https://qt.ax/asn) if that interests you.