Hacker Newsnew | past | comments | ask | show | jobs | submit | vanderZwan's commentslogin

That video is three years old, although the item in question might be older of course. I remember reading about the Washing Machine Project a decade ago or so.

So I guess Operation Neptune was the inspiration for UFO 50s Porgy?

https://ufo50.miraheze.org/wiki/Porgy


> the bizarre decision to make federation whitelist based.

Given the multiple articles I've seen on how federation can easily accidentally DDOS mastodon servers, which isn't even a form of federation that primarily uses something as heavy in data usage as video, I do not find that so strange tbh. And that's before factoring in malicious actors or even just careless ones like all the AI scrapers.


I can see that's probably the logic behind it, but when your biggest USP is federation it still seems like a bad idea to deliberately hobble it.

IMHO based on my use of the fediverse, fundamentally it's about porn and curtailing unwanted porn in your domain. I'm a user of mastodon.social in the "wee US hours" (before US mods are awake) and run across a lot of hit-and-run porn being pushed to Trending (and I report, etc.).

It's a thing, it happens a lot and Lemmy instances have the same problems to fight. Unwanted porn in my eyeballs is sadly a not uncommon experience until you've put in effort to set up blocks and filters on your personal accounts. Peertube being explicitly video based is a natural target for porn pushers.


Hey, some of us are younger and happened to get into programming via making games on their TI-83 graphing calculator in Z80!


Which I guess is the same reason why modern Intel CPU pipelines can rely on it for pipelining.


Hah, we commented on the exact same paragraph within a minute of each other! My memory agrees with your memory, although I think that should be 3E 00. Let me look that up:

https://jnz.dk/z80/ld_r_n.html

https://jnz.dk/z80/xor_r.html

Yep, if I'm reading this right that's 3E 00, since the second byte is the immediate value.

One difference between XOR and LD is that LD A, 0 does not affect flags, which sometimes mattered.


What is this "LD A, 0" syntax? Is it a z80 thing?

One of the random things burned into my memory for 6502 assembly is that LDA is $A9. I never separated the instruction from the register; it's not like they were general purpose. But that might be because I learned programming from the 2 books that came with my C64, a BASIC manual and a machine code reference manual, and that's how they did it.

I learned assembly programming by reading through the list of supported instructions. That, and typing in games from Compute's Gazette and manually disassembling the DATA instructions to understand how they worked. Oh, and the zero-page reference.

Good times.


What is this "LD A, 0" syntax? Is it a z80 thing?

On the 6502 you had three instructions LDA, LDX, LDY where the register name is essentially part of the instruction name. On the Z80 you had a lot of "load" instruction so you had LD and then many different operands: loading 8-bit registers, loading 16-bit, writing to memory, reading from memory, reading/writing from memory using a register as an index. So, made more sense on Z80 to have "LD" whereas LDA/LDX/LDY worked fine on 6502.


> One of the random things burned into my memory for 6502 assembly is that LDA is $A9. I never separated the instruction from the register; it's not like they were general purpose.

You had LDA and LDX and LDY as separate instructions while the Z80 assembler had a single LD instruction with different operands. It's the same thing really.


Right, though the LD? and ST? instructions were kind of exceptions. You could only do arithmetic and stack and bitwise ops (and, or, eor, shift, rotate) with A, never X nor Y. Increment and decrement were X/Y only. You couldn't even add two registers together without stashing one in memory.


> What is this "LD A, 0" syntax? Is it a z80 thing?

Well, I never wrote any 6502 so I can't compare, but yes, you could load immediate values into any register except the flag register on the Z80. Was that not a thing on the 6502?


The 6502 instruction set was really limited but there were three registers: A, X, Y and there were immediate load instructions for each: LDA #0, LDX #0, LDY #0.

You're right. Of course, it's 3E 00. Not sure how I remembered 3E 01. My only excuse is that it was 40 years ago!


Not sure why you got downvoted for pointing that out - it might be linked at the end of the article but people can still miss that.


*shrugs* the internet being the internet I suppose.

There was "See the video that accompanies this post." but NGL was just posting encase anyone didn’t have time to read or missed it.


> In my 6502 hacking days, the presence of an exclusive OR was a sure-fire indicator you’d either found the encryption part of the code, or some kind of sprite routine.

Meanwhile, people like me who got started with a Z80 instead immediately knew why, since XOR A is the smallest and fastest way to clear the accumulator and flag register. Funny how that also shows how specific this is to a particular CPU lineage or its offshoots.


He's explaining that C was not the reason for picking * over ^


> But, as you note, IRL this is not usually the case.

Except for the huge the amounts of already generated slop that is combined with SEO to pop up in search results


Oh, if you finetune GPT-4 on an author it assumes the style so well that people prefer it to human experts doing the same job

> "Readers Prefer Outputs of AI Trained on Copyrighted Books over Expert Human Writers"


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: