Aatube

dohpaz42, 2 months ago

I read the article, and a few points stuck out to me:

1. This has been a restriction since 2021; now it’s documented in the files and not just the online EULA (ie consistent)
2. This is a protection to disallow other companies like Intel and AMD from profiting off of Nvidia’s work
3. Nothing is stopping anybody from porting the software to other hardware, eg

Recompiling existing CUDA programs remains perfectly legal. To simplify this, both AMD and Intel have tools to port CUDA programs to their ROCm (1) and OpenAPI platforms, respectively.

I’m all for piracy and personal freedoms, but it doesn’t seem to be what this is about. It’s about combating other companies profiting off Nvidia’s work. Companies should be able to fight back against other companies (or countries).

I mean it’s not like Nvidia is unreasonably suing open-source projects into oblivion or anything, or subpoenaing websites for user data; at least, not yet.

underisk, 2 months ago

a) Organizations and Conferences

1. Insist on doing everything through “channels.” Never permit short-cuts to be taken in order to expedite decisions.
2. Make “speeches.” Talk as frequently as possible and at great length. Illustrate your “points” by long anecdotes and accounts of personal experiences. Never hesitate to make a few appropriate “patriotic” comments.
3. When possible, refer all matters to committees, for “further study and consideration.” Attempt to make the committees as large as possible—never less than five.
4. Bring up irrelevant issues as frequently as possible.
5. Haggle over precise wordings of communications, minutes, resolutions.
6. Refer back to matters decided upon at the last meeting and attempt to re-open the question of the advisability of that decision.
7. Advocate “caution.” Be “reasonable” and urge your fellow-conferees to be “reasonable” and avoid haste which might result in embarrassments or difficulties later on.
8. Be worried about the propriety of any decision—raise the question of whether such action as is contemplated lies within the jurisdiction of the group or whether it might conflict with the policy of some higher echelon.-

• OSS Guide to Simple Sabatoge

doctorcrimson, 3 months ago

I solved the spambot problem on my channel by blocking every single emoji as well as some common forms of url extension

https://lemmy.today/pictrs/image/5d543afb-9bfb-4d14-8147-ecdb386f0c55.png

southsamurai, 3 months ago

My wife rick rolled me as a Valentine’s present.

See, I’m an old fuck. Old enough that I was around when the song came out. I love the song, and did back then.

So, when rick rolls became a thing, I loved them. Did a lot of them, and giggled like crazy any time I’d run across one.

It essentially makes me impossible to Rick roll because my default assumption is that any link, hidden image, or otherwise suspicious thing online is going to be one, and I’ll gleefully go looking in the hopes that it is.

But she found a Valentine’s card that has the lyrics with a rickpic, and plays the song when you open it.

So I got rick rolled for the first time in ages, and we laughed ourselves into an achy stomach because of it.

Good thing I married her :)

themeatbridge, 3 months ago

I know this isn’t what you want to hear, but you did in fact fuck up and act recklessly

I start moving to the side of the exit to make myself visible and just convince the guy to not bother. Not here to be a hero or get someone arrested. Just trying to deter.

No. Don’t ever do that. You don’t know what a thief will try, and the cost of the product isn’t worth getting punched or worse. You’re lucky the guy wasn’t armed.

Do not attempt to deter thieves. Your job is not worth it.

The company does not have a choice but to fire you. They need to make it absolutely clear to every other employee to never, ever, under any circumstances, place yourself in harms way to deter a crime.

Your coroporate overlords do not give a shit about you. They don’t care if you have been loyal, so don’t be. They won’t reward you for going the extra mile, so stop exactly where they stop paying you.

You were injured on the job. Did you file for employer’s compensation? You should talk to a lawyer. Maybe you didn’t want to, because you felt like it was partly your fault, or you were worried about keeping your job. That’s over, it’s time to protect yourself. Call lawyers now. Make a list of local employment and injury lawyers and start calling when their offices open.

That’s what your employer is afraid of. That’s why you were fired, and why they want to be absolutely clear that employees should never act recklessly like you did. Not because they care about you or their employees, as we already know they don’t. It’s because they are afraid of being sued. And they are afraid of that because being sued will cost them more money than training your replacement.

Be the thing they are afraid of. Win or lose, you’ll know you did what you could to protect yourself this time.

d3Xt3r, 3 months ago (edited 3 months ago)

matching other programs and platforms

Actually, Ctrl+C is the interrupt hotkey for pretty much every CLI app/terminal on every platform. Try it within the Command Prompt/PowerShell/Windows Terminal, or the macOS terminal - they’ll all behave the same.

The use of Ctrl+C as an interrupt/termination signal has a very long history even predating the old UNIX days and DEC - it goes back to the days of early telecommunications, where control characters were used for controlling the follow of data through telecommunication lines. These control characters, along with regular characters, were transmitted by being encoded in binary, and this encoding scheme was defined by ASCII (American Stanard Code for Information Interchange), published in 1963.

In ASCII, the control character ETX (meaning end-of-text; represented by the hex code 0x03) was used to indicate “this segment of input is over”, or “stop the current processing”.

Now what does all this have to do with with Ctrl+C you ask?

For that, you’ll need to go back to the days of early keyboards. Keyboards back then generated ASCII codes directly, and when a modifier key (Ctrl/Shift/Meta) on a keyboard was pressed in combination with another key, it modified the signal sent by the keyboard to produce a control character.

Specifically, pressing Ctrl with a letter key made the keyboard clear (set to zero) the upper three bits of the binary code of the letter, thus effectively mapping the letter keys to control characters (0x00 - 0x1F: the first 32 characters on the ASCII table).

• The ASCII code for ‘C’ is 0x43 (binary 01000011).
• Pressing Ctrl+C clears the upper three bits, resulting in 00000011, which is 0x03 in hex.

And would you look at that, 0x03 is the code which represents the control character ETX.

The use of ETX to interrupt a program in digital computers was first adopted by the TOPS-10 OS, which ran on DEC’s PDP-10 computer, back in the late 60s. It’s successor, TOPS-20 also included it, followed by the RSX-11 (on the PDP-11), and VMS (on the VAX-11).

RSX-11 was a very influential OS, created by a team that included David Cutler. It influenced the design of several OSes that followed, such as VMS and Windows NT. Cutler later moved to Microsoft and became the father of Windows NT. Early NT did not include a GUI, so it was natural to adopt existing terminal operation standards, including the use of ETX. In fact, NT’s internals were so similar to VMS that a lawsuit was in the works, but instead, MS agreed to pay off DEC millions of $$$.

Also, when UNIX first came out (1969), it ran on DEC hardware, and so they followed the tradition of using the ETX signal to stop programs. This convention flowed to BSD (1978) which was based on UNIX, and NeXTSTEP (1989), which was based on BSD. NeXTSTEP was developed by NeXT Computers, which was founded by Steve Jobs… and the rest is history.

Therefore, Ctrl+C is something that’s deeply rooted in history. You don’t just simply change something like that. Sure, you may be able to remap the keybindings, but it’s actually hardcoded into many programs so you’ll run into inconsistencies - that is, if you used the standard remapping tools built into GNOME/KDE etc.

If you want to truly remap Ctrl+C, you’ll want to do so at a lower level (evdev layer) so that it’s not intercepted by other programs, eg using tools like evremap or keyd. But even then, it’s not guaranteed to work everywhere, for instance, if you’re inside a VM or using a different OS, or in a remote session. So it’s best to remap the keys at the keyboard layer itself, which is possible on many popular mechanical keyboards using customisable firmware like QMK/VIA.

skullgiver, 3 months ago (edited 2 months ago)

deleted_by_author

hakunawazo, 3 months ago

…AND behavior = ‘nice’?

For reference:
img.ifunny.co/…/84367d463ab592ae1781d52ac110aca72…