We've been using zod 4 beta already with great improvements but due to our huge codebase not being able to handle the required moduleResolution settings, we cannot upgrade...
They could at least also publish it as a major version without the legacy layer
EDIT: I've just seen the reason described here: https://github.com/colinhacks/zod/issues/4371
TLDR: He doesn't want to trigger a "version bump avalanche" across the ecosystem. (Which I believe, wouldn't happen as they could still backport fixes and support the v3 for a time, as they do it right now)
Surely that must use conventional HTTP referrer data—for which we have well established standards, decades of experience managing interactions and edge cases, and norms for respecting user consent—and not some apparently wishful query parameter?
A user agent SHOULD NOT send a Referer header field if the referring resource was accessed with a secure protocol and the request target has an origin differing from that of the referring resource, unless the referring resource explicitly allows Referer to be sent. A user agent MUST NOT send a Referer header field in an unsecured HTTP request if the referring resource was accessed with a secure protocol.
In other words, it's not guaranteed that this Referer header is set. One can of course choose to remove the query parameter.
Yes, that’s the part about interactions and consent. The intent then is to circumvent that? A case of those pesky matters of security and respect for human dignity getting in the way of SEO?
Homerow looks very cool. Is it actively being supported? Looks like it still uses App Center despite that being sunset, plus the change log shows the last update in June 2024, and before that in April 2023
Some clubs in Berlin (Germany) already do this for quite some time and the people there are all fine with it.
The vibe is just different, because the people focus more on each other or themself instead of generating content for some online profiles.
The cultural and legal expectations around photographing people are very different in Germany than in most English-speaking countries, and especially the USA. In Germany, taking photos of people without permission is socially unacceptable, and sharing such photos is usually illegal.
In the USA, photographing people from somewhere the photographer has the right to be is protected as freedom of speech with few exceptions, and is less likely to be seen as rude. Of course a business can still impose its own rules of conduct inside.
Various clubs and parties in the NYC scene, too, going back well over a decade. I'm genuinely surprised to read there is some (perhaps exaggerated) controversy over this in the news. The places that have strict no photo / no video policies like this pretty explicitly _don't want_ a patron who became interested in attending primarily because they saw a video of the dance floor on Instagram, they cater to scenes and communities where word of mouth and reputation are more than enough to fill the room.
I don't recall getting stickers at any clubs NYC, although it's been a few years since I lived there. It was always on the honor system at places like Output and events like Black Market.
Maybe it varied depending on the night, but I remember Output being stricter about it the first few years they were open – staff would regularly confront people who took photos. But that seemed to fall off entirely over their final couple years.
Output was definitely doing stickers for a while, I still have several of them (on a stickerbombed bicycle frame). I can't remember whether that was in the early years or the late years though.
Yes, it's similar to RewindAI. I was inspired by them :) I mentioned this and listed them as inspirations on Product Hunt. However, I'm aiming to create a local ecosystem, and this is just the beginning. I have a lot of ideas in mind (but little time), so I'm progressing day by day.
Just thought that the `This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support` part will finally solve memory issues with jest, but Simen Bekkhus already posted that it's still an issue... (https://github.com/nodejs/node/issues/35375#issuecomment-174...)
Nope. How could you get any easier than plain DNS? That would require a torrent client and bittorrent protocol. The beauty of this hack is that it exists on top of the ubiquitous DNS system.
I think the obvious match here is how IPFS can use a dnslink TXT file to point to the content-addressable top of an IPFS-distributed static web https://docs.ipfs.tech/concepts/dnslink/ . This is how a lot of dweb/web3 websites maintain and advertise a non-http mirror. It works out of the box for sites served using https://distributed.press/ (non-commercial, open source) or https://fleek.co/ (hosted).
If you use Brave, or have the IPFS browser extension, you can access sites like https://ffdweb.org/ as an option, or preferentially.
It's not far from OpenAFS which uses SRV records to point to fileservers. It's not magnet/torrent but it's certainly DNS discovery for data on a different protocol.
no more paper stuff so rather some software where they have to type all the details into the computer