clpwn
Is the manufacturer of the bomb responsible for when Israel drops it on a family home in Gaza? Yes. Is it the same responsibility as the general who gave the order? No. Is it the same as the pilot who followed the order? No.
Does that make it useless to hold people accountable? Of course not.
I don't know if your AI products are scummy or not, but the fact that you're asking this question makes me less worried about you than a lot of other folks out there furiously rushing to get their AI pre-crime hot dog detectors rushed out the door so they can get on the NASDAQ.
In the end, it's just two different types of cults. You're a fool to show loyalty to Amazon when it shows none back, and Google is in some ways creepier for pretending to care about you and suck in all facets of yourself into a corporation.
The straightforward solution is to work for neither, and show that we won't tolerate creepy corporate culture taking over the technology world that we love.
Much like a lot of other "eccentric" artists in other realms, that eccentricity is, at least in part, a bravery of knowing what one wants and making that a reality, usually with compromises that others might not be comfortable making (efficiency, time, social interaction from a larger group, etc).
As moviuro mentioned, no, not unless you want to get fancy with independent network namespaces (https://man7.org/linux/man-pages/man8/ip-netns.8.html).
If you want to be more confident of not having an address space conflict, I recommend using a randomly generated private IPv6 block using the RFC 4193 specification: https://en.wikipedia.org/wiki/Private_network#Private_IPv6_a...
> 2. Could you please provide installation instructions for generic linux, as I am looking to host on almalinux and opensuse leap, neither of which use dpkg.
Our Arch PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=inner...) may be the simplest existing guide for making your own package for your distro. If it's not a lot of work to add, I'm happy to maintain other package formats, or help you be a maintainer.
Thanks! Looking forward to hearing how it goes for you.
I feel that adding TCP support would push innernet beyond a WireGuard configuration manager and into something a bit more behemoth. I'm quite fond of the fact that innernet doesn't "touch the packets" in its current state.
That said, if a strong need arises over time it's not out of the question, and in the mean time anybody is welcome to add their own wrapper around innernet or fork it to support that.
I also end up using https://gitlab.com/ipcalc/ipcalc a lot, and am definitely planning on similarly making it easier in the terminal to manage and visualize the CIDRs in innernet networks. I'm hoping innernet can become a fun way to learn networking in a safe (and cheap) virtual environment.
macOS is a different story, since there are only userspace implementations at the moment. Innernet currently looks for the official "wireguard-go" implementation, but you can swap out userspace implementations as you like. I'll add an environment variable check to make that easier without needing to recompile.
There aren't any current plans to bake in TCP support, but you can rig it up yourself using something like udptunnel.
Related old HN comment with basic instructions: https://news.ycombinator.com/item?id=17847008
Also see: the "TCP Mode" section in https://www.wireguard.com/known-limitations/.
Happy to change the way that alias works if it ends up being a problem.
The other voice argues that I will be healthier and more capable of producing the things I actually want to produce if I can just stop being so damn stressed about "wasting" an evening playing video games every once in a while. Why buy into the myth that the meaning of life is maximizing productivity?
Some people have biases against specific forms of media (video games and TV take especially big punches) they feel are the Fentanyl of art in a world that otherwise would be glasses of wine. In the end it always feels like a debate about the right ratios of consuming vs. producing, which I feel like is worth reflecting about but will be different for every personality.
There are a ton of cheap "dubplate" vinyl cutting shops out there, and it seems like maybe the OP sent off to one of these shops to print their ROM. Otherwise, they could have just re-cut a new vinyl with the equalization fixes baked in...
tonari is the entire stack, similar in "feature scope" to WebRTC but with different goals and target environments.
> Are they doing video encoding (the audio encoding seems to be done by that webrtc-audio thing)?
Yep, this includes video encoding and transport. We don't use the WebRTC audio library for encoding or transport, just for echo cancellation and other helpful acoustic processing.
> Have they chosen a progressive encoding format that compresses frames and pumps them out to the wire as soon as they're done?
Yep, basically, if by that you mean we don't use B-frames or other codec features that would require buffering multiple video frames before receiving a compressed stream, so we're able to send out encoded frames as they arrive.
> Is TCP or UDP involved or a new Layer 3 protocol entirely?
We encapsulate our protocol in UDP since we operate on normal internet - a new protocol is out of the question without a huge lobbying force and 15 years of patience on your side.
> Have I just missed all of those parts or were they really missing amid all the Rust celebration?
We intentionally didn't get into the protocol details because we are saving that for a dedicated post (and code to back it up).
With crossbeam for example, you can hit roadblocks with std since their channels are MPSC, whereas crossbeam supports MPMC channels (and is faster than std in every meaningful measurement last I checked).
To clarify, we're targeting "transparent" sounding audio, not "FLACs or bust" audio. Right now we send stereo 48kHz 96kb/s Opus (CELT, not SILK) that we found hit the voice transparency sweet-spot compared to the lossless audio source. We had used higher bitrates in the past, and could easily go back to them, but quality plateaued at around 96k in our experimentation.
More than choosing sane transparent-sounding encoding parameters, the biggest difference in fidelity by far was choosing the correct microphones and speakers for accurate reproduction of voices.
You can't talk about how much money you make (or could have made) and disregard the pain you cause people in the process. Not all startups are equally unethical, and Palantir is famously one of the most closely tied to so much human suffering in the world.
It's super fun to play with cryptography, but giving a false confidence to users who may seriously rely on it is what can lead to major problems.