You are free to use it however you want - but if you start charging for your product I get a cut.
The problem here is who this "I" is. Often times, there are dozens or hundreds of contributors. Do they each get a cut? Do they all get a cut of a cut? How is that cut calculated?
I really like them as dumb little "reactions" in chats (as in: emojis other can attach to a message) but, for longer, more thoughtful text posts, they usually distract from the content IME.
I also don't like how they're usually, well I don't know how to describe it but: Overly emotional. Your crying emoji is a good example; you're not actually crying an ocean because you miss emojis, you're just a little sad about it (I assume).
This "always taking everyting to the extreme" really annoys me about our current society. There is no moderation anymore; it feels like you must either be extremely happy or extremely sad/angry/whatever. You can no longer be "a little sad about it", you must show that you're crying a river over it or whatever.
I think that may be one of the reasons why I prefer emoticons. They don't have that problem as much as you can't easily express extreme emotions with them. :'( is about as bad a "crying" usually gets for example and when someone writes xD, you know they're taking a piss.
Suspicious as in: You're lying; the project doesn't exist or you haven't contributed to the degree you'd claim to.
Wouldn't that come off as suspicious?
You're converting to analog and back, each time generating a bunch of noise (how much depends on the converters). The ideal solution is to cut out the analog signal here.
The only digital way of transferring audio streams I know of are TOSLINK (no idea whether that can work between computers) and custom protocols over standard ip like @usrtrv@lemmy.ml mentioned.
An Wortspielen gibt es hier Nix.
I use NixOS but I don't bother with automatic deployment or even automatic formatting. I don't feel it's necessary in a homelab setting as hardware failure rarely happens at such small scale and the manual steps left aren't that significant.
This kind of integration testing is best left up to the individual distros. Same as the integration (as in: packaging) itself.
Distros don't want your binary package, they want your source code, build instructions and a build system that won't make them cry. Some distros even explicitly disallow re-packaging external binary distributions.
As a distro maintainer, I appreciate your wish to do QA on all the distros but that's just too much work. You focus on making your software better, we focus on making it work with the rest of the software ecosystem.
Providing a package for one or two distros (i.e. your favourite one) is good practice to ensure your software can be reasonably packaged but it's not the primary way your users should receive your package in the traditional Linux distro model.
Additionally, you might want to package your software for one of the cross-distro package managers such as Flatpak, AppImage, Snap, Nix, Guix, distri or homebrew.
This can serve distro maintainers as a point of reference; showing how it is intended to work so they can compare their packaging effort. If there's some bug present in the distro package but not the cross-distro package, that's a good sign the issue lies in the distro packaging for example.
Again, don't put much time in this.
Focus on your app.
In der Nix Community gibt's gefühlt auch nur Deutsche. Letzte Woche war plötzlich eine, von der ich mir sicher war, sie wäre aus den U.S. oder so in unserem lokalen hackspace chat und hat angefangen Deutsch zu reden O.o
simple_cat which does a simple read/write loop
You just proved my own point. cat does the write(). Bash just configures where it writes to.
re the reflink thing, you were probably thinking of cp, not cat.
No, I was specifically thinking of cat. I just copied a 73G non-sparse incompressible file in 3 seconds using cat file > copy.
copy_file_range does reflinks on btrfs.
and also for Chrome:
Though it should be noted that this method isn't the only way to detect extensions.