fireant

We're mostly talking about FPS here, you've got 2 main cheat categories: aimbots and esps (visibility hacks)

Esps are purely client side, they read actors from game's memory and draw a client side overlay. It's impossible to protect against these on the server. Even if you had perfect culling from the server (didn't send players behind walls for example) you'd still have semitransparent surfaces like foliage and smoke. There are people making good money in PUBG just making enemy textures that are easier to see. You need kernel anticheat to prevent the cheat reading the memory. Also you want to take screenshots periodically and detect overlays.

Aimbots in the olden days could be detected on the server because their movements were instant, precise, unnatural snaps. But these days cheat developers have wisened up. Again the best protection is to prevent the cheat from reading the games memory in the first place, some anticheats go as far as to try to prevent input from any artificial device (so the cheat can't create mouse movement)

There are also movement hacks, but I don't think that these are really common these days. You can detect protect against these on the server side

What's a difference between this domain model and the service then? In your example you'd have a Login service and all the code related to login would have to go through the Login service, right? Why do you need the additional domain model layer?

I've been using radial menu from Charmstone to switch apps on macos for about half a year and it's a really great paradign. Never could memorize too many shortcuts for switching apps but this is just as fast. I wish there was a high quality app for windows that did this.

I have a website with a game download that has maybe 50 players total. Nobody uses it. I'm fairly certain that actual people downloading the game is maybe a few per month. Yet from this 2GB zip file I've had 5TB traffic over the last month and this has been going on for years.

This is no "DDOS", it's just misconfigured bots/crawlers going through all the links and being unable to cancel downloads.

I've found myself writing the same session/proxy/rate limiting/header faking management code over and over for my scrapers. I've extracted it into it's own service that runs in docker and acts as a MITM proxy between you and target. It is client language agnostic, so you can write scrapers in python, node or whatever and still have great performance.

Highly recommend this approach, it allows you to separate infrastructure code, that gets highly complex as you need more requests, from actual spider/parser code that is usually pretty straightforward and project specific.

https://github.com/jkelin/forward-proxy-manager

That is the future, but I don't think we are quite so far just yet. Right now quality TTS is very expensive and too slow for realtime. Then there are obvious IP issues. Also many books need subtle edits for audio version.

I don't think we can fully replace editors and publishing houses just yet, at least not while retaining high quality and integration.

Bleeding edge TTS is 95% as good as human actors, at least for the audiobooks I consume. I think that for vast majority of audiobooks, the era of human readers has come to an end.

That said AFAIK Audible buys audibooks from partners and does not voice it themselves, so I think this layoff is unrelated.

My understanding is that it's quite hard to make convex objects with radiance fields, right? For example the furniture in OP would be quite problematic.

We can create radiance fields with photogrammetry, but IMO we need much better algorithms for transforming these into high quality triangle meshes that are usable in lower triangle budget media like games.

First time hearing about this. I'm surprised the whole region isn't massively degenerated after centuries of traditional incest. The numbers are pretty staggering

You can easily make maybes in the other direction too - maybe they maintain their absolute market dominace, like Intel for years and years. Maybe they come with a technology jump that will be hard to beat for a long time, like M1. We are probably in the early adopter stage of current AI too.

Predicting the future is hard. Stock prices are based on extrapolated current information and mostly hype.

"... after the country passed a law that allows news organizations to negotiate with tech giants to receive payment for articles shared on their platforms" is a really funny way to describe a law that FORCES tech giants to pay for having links to news articles.

It's almost as if WP has a horse in the race.

Does that imply that everyone who started with more money than Musk now has even more money than Musk? Or perhaps it implies that you just can't ever get poorer?

I don't think its possible, or fair, to reduce success to a single digestible dimension.

Wow I didn't even think of this. Truly a brilliant move that intends to kill the open web on two fronts at once.

Wow that's a cool evolutionary algorithm in practice! I'm actually surprised it worked, especially with the amount of fuzzing I'd expect ssh ecosystem to receive (well perhaps the servers do, but not the clients haha).

Is this what the whole argument about intelligence is about? That you don't want to cause suffering and only species of certain intelligence can suffer and others can't, thus you are not feeling guilt when killing and eating things that are not intelligent?

That just seems so bizarrely naive to me. Every living thing suffers when hurt. Suffering is a feeling of not wanting to die, or to be hurt. I'm pretty sure that it is one of the primary mechanisms of evolution of living things, it is a strive for self preservation. Human suffering is fundamentally the same as that of an octopus, an insect or a tree.

Yes, comprised/utilize doesn't really matter because you will know from context, but biweekly is really tricky. For example "we have biweekly sprint ceremonies on monday and friday" can be very confusing.

It's funny that on one hand people are preaching about Time To First Byte and SSR and what not, and on the other people from CF/Vercel and others are massively investing into serverless which almost by definition has to have drastically degraded latency compared to normal apps.

You setup CORS on your backend, it does not matter where or how you frontend works.

IMO biggest problem is that if your website is public facing, then just having an SPA is bad for crawlers and not great for UX.

I've switched to running new projects on Remix after using Next.js for many years. Remix is just much more sane. Next.js feels like they are aiming to statically precompile everything and do some automagic with the rest all the while locking useful features under Vercel.

I just want to write my SSR applications with dynamic data and deploy them to Docker, Next is making it harder than it needs to be.

I'm in the same boat as I haven't read or watched the news deliberately for years. The important stuff is going to get through to me anyway.

But people need to have an option to know. You need access to information for healthy society, even if you mostly don't consume it. News is information, even the articles you posted.

Missing standard downstream promise cancellation is arguably one of the bigger problems in the whole javascript ecosystem. In C# almost every async function has a CancellationToken parameter, same in Go with Context.

Even after years of writing fullstack javascript this is my first time seeing AbortSignals, probably because nobody uses them. Some libraries, like Axios, handroll their own cancellation mechanisms, but that does not really cut it.

WASM could be such an IR unironically https://github.com/nebulet/nebulet. But I doubt that we would be gaining performance/efficiency this way.

There could be price savings too, right? Two motors less and simpler ESC gotta save something.

I really wonder if total cost of ownership/energy required to run a cluster of old android phones would actually be lower than one or two servers.

The phones are ARM, will have battery issues (esp if they run 24/7) so you need to provision for safety, can only be connected over wifi, have thermal issues (they are meant for burst, not sustained load), have non-homogeneous bootloaders/bugs and so on

Thank you for the link. I have a project with plenty of structured data from which I create summaries and short articles. Currently I'm generating prompts with context inside the prompt. GPT Index seems to pretty well fitted to that usecase

The voices are really amazing, I couldn't really tell that they are synthetic and I was looking for it.

The only issue is that the actual recordings sound like they have been overcompressed, or poorly recorded - is there any way to improve this? Something like superresolution, but for voice?

Everyone is different, I read rather slow and can ingest the article much quicker with audio (esp. sped up audio) than by reading it.

While brain has vastly more computing resources, they are probably operating very far from the theoretical optimum. There must be so much baggage, inefficiency and dead pathways left which do not have much purpose at all. The brain was evolved, not designed, which means that any random features/mutations which did not inhibit individuals ability to procreate got to stay.

I think that even when we understand the brain completely, it will be very difficult disentangling what is useful for artificial neural networks and what doesn't really matter.

Pretty strange isn't it. I would think that headless server is #1 deployment for ubuntu, but out of 4 headline features only one is for this usecase and it's for a different product by Cannonical. Boring is good, but is there actually nothing interesting happening?

This exact code can be found 1000 times on github and many of those are MIT licensed https://github.com/search?q=%22cs+*cs_transpose+%28%22&type=.... Copilot, or any other developer or person, has no way of knowing where the original implementation came from or it's original license. The cat is out of the bag, get used to it.