I also want sunrise/sunset time, random number generator, and hourly beep+30m beep like a ships clock

Format is: (1-1024) WORD WORD WORD with a relatively short wordlist (8k words). Maps to ~1 square meter and plurals/singular words represent the same value. Completely open source to everyone.

My gripe with pluscodes is memorizability. Number and 3 words from a short list should be pretty easy to remember and write down. Either way, my replacement can easily map to plus codes/lat lon/google maps/openstreetmap. I'm super excited about it.

I'll probably post here when it's closer to done.

As a Firefox user, articles like this are just noise, not a possible attack on my personal privacy. When was the last technical scandal with Firefox? Adding an optional bookmarking service? How are people still defending chrome?

Also if you compare from a fingerprinting side of view then Brave is better than Firefox+uBlock (and all privacy lists involved). You can compare that easily between your Firefox and Brave here: https://coveryourtracks.eff.org/

For me personally I also don't want to miss Chromecast capabilities (it's a nice system and unfortunately there is no good alternative) in my mobile browser.

1) You go to https://i.imgur.com/vuUyLnz.gifv.

2) You decide to skip the beginning so you "Right Click > Show Controls" and use the controls to skip the beginning.

3) You decide to skip to the end so you move your mouse over to where the controls should be but they don't reappear.

4) They're gone and the only way to get them back is to "Right Click > Show Controls" again.

There are a lot of rough edges like that. I'd almost rather not use browsers than use Firefox in its current state.

Your other commentmentions i.imgur.com being the case? Maybe libredirext can help you never hit the i. Site?

Afraid not. In Chrome and Safari the controls reappear in step 3. In Firefox step 4 is required.

I wouldn't be surprised if it was an imgur thing but I have seen it in non-imgur embeds on reddit.

> Maybe libredirext can help you never hit the i. Site?

That could work. Thank you!

Chrome seems to ignore this attribute being set to false and continue to show controls anyway, which appears to be a spec violation from my reading of it. Of course it ends up being a desirable behavior in this case.

Just skimming through the first few pages and it looks like all of the videos are gifv:

NSFW

https://old.reddit.com/domain/imgur.com/

cough Proton cough

That being said, most of the extensions I use have survived the last two years of Firefox development.

I'd take Proton any day over a neutered ad blocker

It's like one setting in about:config

> Switching to Firefox means accepting ads built-in to the browser, something that (AFAIK) Google has never done

Google might not build ads into the browser, but if you use it as they intend and log into the account all of your activity gets tied to your account. I would rather have pocket then not be able to sign into a google account without google signing it in across the browser

> I mean, sure it's great that ad blockers still work, but let's not pretend that Firefox is some kind of bastion of pro-user sentiment.

Yeah mozilla has a shitty track record I'll admit and firefox is a lower quality product, but at the end of the day it's still the lesser of two evils

Oh really, which one?

> at the end of the day it's still the lesser of two evils

Never said it wasn't.

Unfortunately it does not, as other replies and plenty of HN Firefox posts demonstrate.

> I honestly don't understand why more people, especially on hn, haven't switched over still.

There are several important areas where Firefox is lacking. Automation on macOS is one of them (it’s the sole major browser without AppleScript support) but in every thread I see people complaining of something different.

I use neither Firefox nor Chrome. I don’t want to support Google, but it’s also not feasible to use Firefox as my daily driver or to support it in the tools I release.

Here's a minimal example (https://jsfiddle.net/wc5dn9x2/):

    <img id="asdf" name="getElementById" />
    <script>
        // The img object
        console.log(document.getElementById);

        // TypeError: document.getElementById is not a function :D
        console.log(document.getElementById('asdf'));
    </script>

It seems that the names overwrite properties on document with themselves only for these elements: embed form iframe img object

Edit: Here's how I found this: https://jsfiddle.net/wc5dn9x2/1/

It's weirdly not that discussed on the web, most probably because it require a pretty specific situation.

If I predict with 99.99% odds something will happen and it doesn't, my prediction could still have been correct as that fits in the remaining .01%. Whereas if I predict something will or won't happen after some time, you can confirm if it did or didn't happen after that time.

Even if someone says "there will be an ice cream shortage in France in the summer of 2025" they don't mean they are 100 % certain of it. They mean they find it somewhat likely -- but exactly how likely? That's what they have to tell us, because we don't know.

For an individual prediction, you can never tell whether it's true or not, because individual predictions always come with some level of uncertainty.

What you can do, if you know at what confidence level it was made, is

- Score individual predictions. One made at 99.9 % certainty that doesn't come true gets a heavy negative score, while if it would have been made at 60 % it gets penalised much less.

- Verify the accuracy of a collection of predictions. If I predict five things at confidence levels of 0.8 0.7 0.9 0.5 0.5 then I should get roughly 3--4 of them right. If I don't, my predictions aren't very accurate.

> a stack made for a single game is not a game engine.

For a concrete example: the newest Lego game, Star Wars the Complete Saga, had a complete engine rewrite ("NTT") and the new game is the only one that runs it. I wonder what term the author would use to describe NTT, which isn't designed to run a single game or have a community.

Game engines are more of an ecosystem. Yes, the community is a thing because the devs seem to be a small indie group that uses Godot so they can ask for assistance, but Frostbite does not have such a thing (well, maybe internally at EA), and yet noone would say it's not an engine. As long as, through an upgrade, your engine keeps the same way of working and you're familiar with it, it is an engine as a whole. UE and Unity are two different engines because the workflows are different. But UE4.0 to UE5.0 is still the same engine, you won't take that much longer to get back in the groove.

Not really. In the case of Unreal/Unity/Godot (and perhaps things like Quake and Source before it), sure. But there is definitely more to engines than this, which is the argument being made.

We probably need a better term to differentiate traditional engines from the big ones that come with an integrated editor. But until we do, there are many sizes of engines.

> As long as, through an upgrade, your engine keeps the same way of working and you're familiar with it, it is an engine as a whole

Again, this is the controversial part. Engines are traditionally not about editors and workflows and whatnot. Sure the term has changed recently and a lot of people now have this impression, but until there's new terms, engines come in different sizes.

Lots of big claims about engines traditionally not being about editors, but nothing to back that up. Engines have always referred to the whole package, and to something somewhat reusable. Saying "recently" and mentioning the Quake Engine before makes me question your definition of recent. Thirty years old in an industry that's barely 50 if you count the first popular games like Oregon Trail? Where do you fit Monkey Island, using the SCUMM Engine in 1990 ? You don't see anyone talking about the Celeste Engine, or the A Link to the Past Engine, because they're bespoke, single purpose implementations.

So, no, engines have pretty much always been about reusable tools, that may or may not bake certain gameplay elements in, but are overall just a tool.

Big claims? What the hell does that mean?

What about Bevy, the engine mentioned in the article this thread refers to? Also, most Rust engines. Also most engines you find in Github.

Or do you want a list? Here's some from the top of my head that I'm familiar with: Love2D, Irrlicht, Torque3D, Solar2D, MUGEN, Nebula, jMonkeyEngine, Panda3D (this one powered several Disney games), Cocos2D (it powered several popular games before Cocos Creator existed), Ogre3D (before having an editor). There's also plenty of Rust ones: Bevy itself, Amethyst, I could do more research, but I suggest checking Wikipedia.

This is also not counting studio-specific scriptable engines. I worked on a few and we didn't need scene editors, because we just used 3D editors and tags. That's definitely an engine, despite not having the tools you claim to be necessary.

You can make the case for those engines not be called engines anymore, or maybe engines with editors should perhaps be called something like "megaengines" or whatever, but there's definitely more than one type of engine.

Sorry but you can't retroactively change the name of things just because they don't fit your limited knowledge. The "engines must have editors" thinking is something that only happened in the last 10 years, a few years after Unity3D gained popularity, and while some newbies might assume that from this meme, it doesn't really represent the historical use of term or the usage of the term by the industry as a whole.

And yes, I've tried smooth fonts and FixedSys/Less Perfect DOS-VGA on both and prefer blocky ones every time. High res screens love to use smoothing and subpixel rendering and I very much prefer none of it.

Edit: point being if you switch to high res displays, you won't always like it more

Quite the opposite! These are hacks for low-res displays to make type look better. Sufficiently high resolution displays disable these because they are high resolution enough that your eye perceives a smooth line/edge already without having to resort to hacks to avoid stairsteps.