Thanks for the details ! Still curious to know how a new instance, with an old domain and fresh keys, would be handled by other instances.
Thanks for the details ! Still curious to know how a new instance, with an old domain and fresh keys, would be handled by other instances.
There is even a “Ignore cache” box in the devtools network tab
Yeah, this probably has to do with the cache. You can try opening dev tools (F12 in most browsers), go to the network tab, and browse to pathfinder.social. You should see all requests going out, including “fake requests” to content that you already have locally cached
That’s really really weird, I cannot resolve the domain to an IP, even after trying a bunch of different DNS servers. If you’re on linux, can you run nslookup pathfinder.social
and paste the output here ?
The fact that it has not been bought as soon as the domain expired makes me believe this instance went down before the trend started
These services usually use either or both of passive DNS replication (running public recursive DNS resolvers and logging lookup that returns a record) and certificate transparency logs (where certificate authorities publish the domain names for which they issue certificates). A lot of my subdomains are missing from these services
It does not seem to be the case. Was it the full domain for this instance ?
I prefer the CLI as well, but when I’m not a dev I supervise practical works in programming classes, where I don’t have much saying in the recommended/required tools
I don’t remember exactly, but the issue is about the existence of a button that makes beginners think a commit and a push are part of the same atomic operation. Not the order of the words on this button
The worst thing about eclipse I’ve had to deal with is its git integration. The conflict resolution tool is awful and half the terminology diverges from plain git.
The fact that it has a “Push & Commit” button also drives me mad far more than it should
As usual, I subscribed for the giggles and I keep getting dragged into unsolicited rabbit holes of useful knowledge. Thanks for being an awesome community
I can think of some “programming best practices” that can help with reducing merge conflicts, such as making small functions/methods, but I see it as a positive side effect.
I don’t think avoiding merge conflicts should be a goal we actively try to reach. Writing readable code organized in atomic commits will already help you get fewer conflicts and will make them easier to resolve.
I’ve seen too many junior and students being distracted from getting their task done because they spent so much time “coordinating” on order to avoid these “scary” merge conflicts
That was the point of my comment, unless they wrote this ironically.
Sorry you went through the trouble of writing all of this explanation, I hope this is useful to someone else
How do you avoid conflicts happening in the first place?
Might as well use Google drive… Or maybe actually learn to use git? The learning curve is steep but it’s worth investing in it
Well, it kind of makes sense to give a figure in such an unit. It allows you to quickly calculate how much you’re gonna spend on your electric bill (but only if you’re based in the US), since all weird conversions are already done
Well, Watts are just a different way to write Joules per second. The unit we should eliminate is {k,M}W.h which introduce a 3.6 factor in conversions to/from the regular unit system
I totally agree with w3schools being bad. However, when teaching web dev to beginner students, they usually find the MDN hard to understand and turn to w3schools.
The MDN requires either quite a lot of experience reading documentation, or being shown how to navigate it.
What I did is use a wildcard subdomain and certificate. This way, only
pierre-couy.fr
and*.pierre-couy.fr
ever show up in the transparency logs. Since I’m using pi-hole with carefully chosen upstream DNS servers, passive DNS replication services do not seem to pick up my subdomains (but even subdomains I share with some relatives who probably use their ISP’s default DNS do not show up)This obviously only works if all your subdomains go to the same IP. I’ve achieved something similar to cloudflare tunnels using a combination of nginx and wireguard on a cheap VPS (I want to write a tutorial about this when I find some time). One side benefit of this setup is that I usually don’t need to fiddle with my DNS zone to set up a new subdomains : all I need to do is add a new nginx config file with a
server
section.Some scanners will still try to brute-force subdomains. I simply block any IP that hits my VPS with a
Host
header containing a subdomain I did not configure