If it’s private property it could be anything. Maybe it’s a golf course or something plant related. Maybe it’s somewhere plant or tree related. Maybe it’s just camouflage to keep the visual noise down.
your link shows a \ before each underscore in the visible text for me in both comments, like this https://en.wikipedia.org/wiki/File:Blue_stop_sign_-_hawaii_-_oct_2015.jpg and hovering or clicking the link replaces that \ with %5C, so the entire thing tries linking to https://en.wikipedia.org/wiki/File:Blue%5C_stop%5C_sign%5C_-%5C_hawaii%5C_-%5C_oct%5C_2015.jpg. clicking ‘source’ on those comments shows just the \ before each underscore
no idea what’s causing it, super weird to have the same bug messing with links that reddit does
The underscore is used to underline text in Markdown. If you want to display a real underscore like this: _, you have to escape it with a backslash. Some clients apparently interpret this rule even in plain links, and some don’t. If we use real Markdown links this should not happen.
As you put it, the web version renders & includes the backslashes, causing your link to break on lemmy.world, running the website itself in Firefox on Windows 10.
Perhaps this would not happen if you insist on https://en.wikipedia.org/wiki/File:Blue_stop_sign_-_hawaii_-_oct_2015.jpg. Sure, it takes a little bit, but since the rendering of the underscores is put after including them in a hyperlink, I suspect going the extra mile makes it more reliable.
Either way, on web (Firefox in Windows 10), the fixed link works as desired, while the original is borked. And the hyperlink behind text one… Well, you’ll see.
I lived in Hawai’i for three years and remember blue stop signs, but not green. Green road signs in Hawai’i would fail to stand out for 3/4 of the year and defeat their purpose.
It could possibly be a stop sign from Ko Olina on O’ahu, but I never spent enough time there to actually absorb the color of their road signs.
Also, for those wondering about the inevitable followup question, a stop sign has to be placed by a local or state government to be enforceable, and is required to follow the exact standard specifications. Tickets have been thrown out due to stop signs being a slightly wrong shade of red, so blue or green are definitely out.
I am so down for a sequel of this game and while it looks good the only thing making me hesitate are the performance issues. I’m tempted to just play the first one more and even pick up a DLC I want for that instead of putting the cash to this.
So far I’ve played 4 hours and I just think there’s a hate train on it. I have a 3000 series card and took the recommended steps from paradox and the game plays fine, I’m enjoying it. From what I understand VRAM is the choke point, so if you don’t have a ton then maybe hold off
I think it’d be very playable. Just follow all the steps on the forum post. (To the downvoters, what does my experience not fit your narrative? That I’m having a fun time in a game that I’m enjoying?)
I loaded up the 100k city and it was playable after following the various guides out there for me. It reminded me a bit of how Dwarf Fortress used to slow down and stutter when you had a lot of dwarfs running around.
That said, they should have kept it in the oven until sometime in 2024. Besides performance improvements there are a few rough edges especially Chirper and in the simulation itself that need more work. One example is civs complaining about healthcare excessively until you unlock the upgrade for the full hospital and build one. Also some of the new tools like the road one and the pipe system need more polish as they can be unintuitive and frustrating to use at times.
It’s ultimately not a bad game it just shouldn’t be released yet. They should have gone the early access route because that’s how it feels at the moment.
It’s more trying to indicate the tongue placement - an N sounds different depending on whether you place it at the front of the tongue or back of the tongue. Back of the tongue is much more nasal, which is frequently associated with French accents, and could sound almost like an “ng” sound to someone less familiar with nasal pronunciations.
To this day, I still don’t understand what takes windows updates so dam long. Not sure about Mac, but Linux takes, what, 5 minutes at most if you’ve gone a while.
Very true for mainstream distros, but there’s more: Linux updates in the background. No matter how long it takes(if you for example use Gentoo), there is zero downtime. And with kexec your system can be its own bootloader and can do insane stuff like starting new kernel without re-running POST, which is on servers is very important(because they have shitty BIOS that takes ages to boot).
Sometimes I won’t use Tumbleweed for a few months then boot it up and it will update every package on the system (literally full reinstall of the os and all installed software) faster than Windows can search for updates. What the heck?
This is a byproduct of one of the largest and more ignored differences between windows and linux. The fact that Linux let’s you modify files while they are open whereas windows doesn’t.
This means that you can update a linux system by just replacing the files with the new ones while it runs. On the other side, Windows can’t modify its own files while it runs, so instead it has a second entire OS to update itself, and requires a reboot to unload all the files and boot from the updater without locking windows files.
No, silverblue does all the work before you restart the computer, and the actual work doesn’t involve replacing the OS itself but basically downloading some files and just checking a different git branch when booting.
In some sense this would even seem an advantage of Windows. (I know it’s the fundamental reason for many hangs and freezes, but the idea that a file is a lockable resource doesn’t seem that bad.)
I think files being locked is really intuitive, which greatly helps new users. Allowing files to be modified or deleted while they are open makes it really easy to shoot yourself in the foot. For example in the video of Linus switching to Linux he was uncompressing a file and tried to open it while it was still uncompressing, which failed since the file wasn’t complete. He didn’t understand why the file wasnt uncompressing correctly. That can’t happen on Windows, since the file being uncompressed would be locked.
I think there should be a ‘lockable mode’, and for distributions oriented to new users the home directory should be mounted like that.
There IS ‘lockable mode’ since System V era. It is extensively used by package managers and similar stuff.
Deleting file does not actually deletes it from disk until last program closes it. And there are ways to open file such that changes to file will not be seen in program.
Yeah with “lockable mode” I mean locking by default instead of requiring every program to specifically call for locking.
It would probably break lots of software, but only using such mode for the users home (or maybe even specific Downloads/documents/desktop/etc folders within the home directory) could reduce the impact.
[Edit] wait I think there is whole fs locking mode on mounting, with the “mand” option, going to test it.
Can’t remember a windows update taking longer than 5 minutes. And even if it did take that long, you can just press “update and shutdown” when you stop using the pc. Windows has a lot of problems but this isn’t one of them.
A lot of it happens in the backgound. It is at least a 15-30 minute process from start to finish. Very annoying if you have an older computer as it is sucks up a lot of resources updating during the background updates.
I normally don’t ever shutdown or restart my desktop. I like leaving program and stuff running so I can continue what I am doing when I get back. With an update I have to close out all of my shit and then shutdown and open everything back up.
I also swear when you have updates pending on a restart the computer doesn’t run very well.
Another issue is that windows will eventually force a reboot on you with pending updates. You can postpone it for a while, but eventually you’ll be in the middle of something and it will just do it anyways.
Another issue is that windows a predatory person will eventually force a reboot on rape you with pending updates upknocking. You can sometimes postpone it for a while, but eventually you’ll be in the middle of something and it they will just do it anyways.
Hopefully, we’ll agree that rape is much worse, but the underlying principle is the same: some entity abuses something you own - your body/property. Since you’re the owner, you exclusively should be in control.
Unfortunately, it can sometimes be necessary to leave an abusive partner/OS. This can be challenging if you “need” one but they’re all evil and dominating. M$ is not abusing its users as violently as some people are abusing their partners. However, their subtle abuse of their users takes place on a much bigger scale. Not only in this (pretty unimportant) regard, but also by e.g. unwanted telemetry/tracking. Luckily, non-abusive partners of the Linux family are becoming easier to find and date, and many are already flirting with one or more of them.
If your computer is always running it may never take longer than five minutes. But try to leave your computer shut down for a month or more. Then updates accumulate and it can take really long to make them.
They have no packages but do a full patch of the system data. Since this is the most complex approach and almost everything can go wrong down to the core they spend most of the time with checking and cleaning state.
Mac updates are less frequent but take longer. They also restart the machine. One difference though is that my mac never took it upon itself to start an update without asking my opinion.
One company I worked at had a weird customization for both Windows and Dell UEFI updates, and this shit was super intrusive, basically you could skip it only once, and then it’d count down to the update even if you’re on an important Teams meeting
memes
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.