So I’ve been racking my brain over this problem for a while, and I think your problem is that you should be running a synchronous latch.

By doing this asynchronously, the CO pulse will be an extremely narrow glitch. As soon as you reach zero, the latch will set, which will load the data bits immediately, which will suddenly bounce CO back as fast as signaling allows. Remember that PE is asynchronous. As soon as it goes high, it will quickly become no longer true that we have a carry out, on the order of nanoseconds. This could be shorter than the minimum pulse width requirement of your latch gates which might not yet have had time to finish stabilizing. I could see that causing the latch to misbehave.

I don’t know if having such a skinny pulse could violate timing constraints on your gates.

deleted by creator

deleted by creator

Is your reset input into the latch connected to the clock pin? Was that intentional?

Lots of room for Trump and those poor kids.

I’m afraid this may not be enough. One who is so deep in their delusions isn’t so easily brought back to reality, if they ever can be.

Article says it’s the rough woodlouse.

I think it’s inevitable; I imagine that in the future there will be an application and vetting process if you want to federate with a major instance, as most users will not be interested in running their own instances, and your federation can be a source of work for the mods/admins.

I would like to underline and insist on using unique passwords. Many users like myself are joining small instances to get better performance and reduce the strain on the main servers, but anyone can spin up an instance and then poof, your password is gone if they can get you to sign up!

This was always the case for normal websites on the internet however. I strongly recommend everyone use a good password manager to prevent one breach from cascading into a breach of all your accounts. It’s good OPSEC.