mkishi
Folks around here are generally uneasy about tracking in general too, but remove big brother monitoring from Safe Browsing and this story could still be the same: whole domain blacklisted by Google, only due to manual reporting instead.
"Oh, but a human reviewer would've known `*.statichost.eu` isn't managed by us"—not in a lot of cases, not really.
Now, this is only about it being a GitHub breach. Whether unlicensed (emenel/portfolio) or GPL (emenel/dust) code should be allowed in such datasets is a different matter.
[1] https://archive.softwareheritage.org/browse/origin/directory...
[2] https://archive.softwareheritage.org/browse/origin/directory...
[3] https://archive.softwareheritage.org/browse/origin/visits/?o...
It might not be to your liking, but it's been in Netflix's top 10 lists [2] quite a few times.
[1] https://www.independent.co.uk/arts-entertainment/tv/news/sha...
[1] Highlighted comment: https://www.youtube.com/watch?v=AHFSrxlouh8&lc=UgxI33WIYq61V...
You can still use `onMount`. It's not deprecated [2], although `$effect` could be used similarly going forward.
[1] https://svelte-5-preview.vercel.app/docs/functions#untrack [2] https://svelte-5-preview.vercel.app/docs/runes#$effect-what-...
It's still a pretty minor warning and it only requires two clicks to ignore.
> We got a takedown request by openai's legal team...
Did Github take a separate action somewhere?
I used Google Drive/OneDrive in the past but a few times vaults would get into a broken state where they couldn't connect to the provider anymore and I had to manually re-connect. It was always able to smoothly recover and sync, but I had no confidence I was synced at any given moment.
I jumped on Wifi Sync as soon as they launched it and haven't looked back—as long as I'm on the same network once in a while, everything is in sync.
Sometimes I get an itch to try the open-source/Keepass route again, especially since it seems to be much improved, but Enpass is convenient for now.
But it seems the parser is breaking when trying to do the inverse, anyway: "100 usd in eur" seems to do "e*ur" and gives "Values must be converted to units."
The fact it states it's powered by JSC before even mentioning Zig makes it pretty clear, imo.
The SNI here is that Tauri has hit stable, an information that does change how a lot of people would approach it.
I might need an even longer explanation, though, because I don't get it still. There are projects like Blender which were allowed to the front page like 5+ times in the past year, exclusively with posts about new releases. The discussions always hit the same notes. Why is that any different?
[1]: https://redux.js.org/understanding/history-and-design/prior-...
The details are not fresh, but it went something like: if a function called an async function like so `the_frame = async foo();`, you couldn't really reliably `resume the_frame;` unless you were responsible for all suspend points hit inside `foo`. If `foo` tried to call some other function `bar` you had no idea had a suspend point, you couldn't resume the frame anymore since you'd need to resume the inner frame instead.
So, yeah, they were colorless as in you could call any function you wanted and they don't advertise suspend points or async usage, but they are actually colorful inside and calling the wrong color breaks things.
I'm confident customers' reactions would be very different had Vimeo told them "hey, you're actually costing us money, please upgrade to this plan that'll cost you about 30% more." In fact, Vimeo could have done that at 2x, 3x, 4x... But nope, let's pretend they're paying customers and reveal we've actually been subsidizing the service the whole time, but we need 17.5x the money now. And the customer is the arrogant one?
And, yes, I'd personally consider word-of-mouth to be largely push-based. But I concede it could just as well be people asking (perhaps too many) questions.
Since I had a bunch of software open and the system had been online forever, I restarted and tested again — turns out it squeezed a couple of ms to ~16ms on shared-mode.
By the way, I believe the low latency stack is enabled system-wide, so Reaper should already be using it.
For what it's worth, on my game I've been piping a SunVox instance to a 128-samples shared-mode WASAPI stream and haven't encountered distorted audio, yet.
At the end of the day, I guess I would indeed default to recommending WASAPI unless one has hardware with great ASIO drivers.
It's just that I'm more focused on soft synths, and I can get a clean signal out of 64-samples buffers. Granted, that's not what I'd use with any realistic processing (for instance, I use Reaper at 128spl@48k).
While I haven't measured end-to-end yet, I do hope it stays below 20ms. I'm working on a synth-powered rhythm game, and the whole reason I chose to stick with plain WASAPI was to avoid requiring users to install extra drivers and because of Windows 10's low latency stack, with its advertised 0ms capture and 1.3ms output overhead on top of application and driver buffers.
Update: I ran RTL on the budget 2012 desktop and got worse results than I expected at 18ms@128spl for shared-mode WASAPI [1]. For some reason, I couldn't select smaller buffers. On the same hardware, exclusive-mode WASAPI managed 12.25ms@128spl, and ASIO4ALL managed 12.5ms@64spl and 15.1ms@128spl.
These days, I can get ~1ms latency with shared-mode WASAPI on a 2012 then-budget i5 desktop, with on-board audio...
But there doesn't seem to be concrete plans (dates or details) yet, so who knows.
They just announced today [2] that a second dev [3] officially joined the project.
[1] https://twitter.com/ruby0x1