re: other improvements, it was also common for mods to change behavior between netquake and quake world.
Specifically I remember team fortress's pyro secondary grenade in QW being just pulses of AOE damage instead of shooting more fire particles that needed tracked, and the soldier nail grenade .. doing something different to not have as many flying objects.
The inaccuracy point is particularly problematic as either they cite you as the source despite possibly warping your content to be incorrect.. or they don't cite you and more directly steal the content. I'm not sure which is worse
'those scientists' were from Sweden responding to protests over the increasing costs of food due to famine. When looked at from the lens of maximizing calories per dollar, it makes a lot more sense.
I'm pretty far removed from game dev but curious.. is the in mem sqlite DB the only representation of game state or is it just 'mirroring' the 'real' values in ram? like if there's a Score on the HUD, are you doing a SQL select to read the value on every frame?
Or is this just a way to serialize and deserialization the game state to automatically save the game so it could be reloaded if it closed/crashed without explicitly running a 'save game' function?
This is interesting but something i feel like id disable on most of my ssh servers as they are only exposed through a shared jump host, and I don't want users that have too many keys in their agent to cause the jump host IP to be penalized.
And unlike some other sshd directives that have a 'Command' alternative to specify a command to run instead of reading a file, this one doesn't, so you can't just DIY distribution by having it curl a shared revocation list.
It would also be very rare. The penalties described here start at 30s, I don't know the max, but presumably whatever is issuing the bad behavior from that IP range will give up at some point when the sshd stops responding rather than continuing to brute force at 1 attempt per some amount of hours.
And that's still assuming you end up in a range that is actively attacking your sshd. It's definitely possible but really doesn't seem like a bad tradeoff
id assume those unchanging ipv4 addresses are not shared and natted with other customs and thus charging for them makes sense as you're consuming a limited resource they are paying for.
That's not the same for not changing an ipv6 address
>Just because you need an algorithm such as a specialized prompt to retrieve this memorized data, is also irrelevant.
I disagree. Granted I'm a layman and not a lawyer so I have no clue how the court feels. But I can certainly make very specialized algorithms to produce whatever output I want from whatever input I want, and that shouldn't let me declare any input as infringing on any rights.
For the reducto ad absurdum example: I demand everyone stops using spaces, using the algorithm 'remove a space and add my copyrighted text' it produces an identical copy of my copyrighted text.
For the less absurd example.. if I took any clean model without your copyrighted text, and brute forced prompts and settings until I produced your text, is your model violating the copyright or is my inputs?
if it was trained on a sufficient amount of fan art made in the studio Ghibli style and tagged as such, yes.
otherwise those would just be unknown words, same as asking an artist to do that without any examples.
though I am curious how performance would differ between training on only actual studio Ghibli art, only fan art, or a mix. Maybe the fan art could convey what we expect 'studio Ghibli style' to be even more, whereas actual art from them could have other similarities that that tag conveys.
IMO setting the expectation of 'wont survive a reboot' is more consistent. but even that fails with private tmp files that could be tied to ephemeral units
Even easier to just have a doc give some examples of third party tunneling solutions and not have the app try to do anything more than normal connections.
ssh tunneling alone can be done in so many ways with different environments necessitating which might work. are we talking ssh tun/tap IP tunnels? simple port forwarding? either of the above but with a proxyjump required to get there?
Probably good to have some basic checks too if it's expecting a text file of SQL queries- like a dismissible warning if it's over a certain size or doesn't appear to be plain text
Are you sure about that 'never'? that no device will ever try to use p2p fonnections?
Even then id still rather ensure every device is appropriately firewalled. 'not worrying about it's sounds like a hardened shell with a juicy center. What happens when a device does get compromised and tries to spread to your local network?
> But it’s clearly not what people want. Ask any person if a search for a hex encoded ID should be a fuzzy match for a different ID and the answer will be no.
>
in a search field explicitly for hex encoded IDs it shouldn't be
In a generic web search that has to guess if my term was a hex encoded id ('cafe' is but almost certainly isn't intended as one..).. it's less obvious.
in the case of a clear hex encoded id of sufficient length, i would like to know there are zero exact results, but as long as it's still fast I would love some fuzzy matches after in case there was a typo in my term or in the indexed document.