trualias
ancient-3d-for-turboc | trualias | |
---|---|---|
4 | 3 | |
11 | 36 | |
- | - | |
0.0 | 5.4 | |
over 7 years ago | 8 months ago | |
C | Python | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ancient-3d-for-turboc
-
Ask HN: Publish old projects even though the source code embarrasses you by now?
Nice! This prompted me to post my own code from the same era: https://github.com/pjc50/ancient-3d-for-turboc
I guess I should add screenshots.
-
Step Away from Stack Overflow
Twenty-five years ago, slightly before I was an undergraduate, I got hold of the PC Games Programmers Encyclopedia http://bespin.org/~qz/pc-gpe/ and built myself a software renderer. You can see it on github: https://github.com/pjc50/ancient-3d-for-turboc
Software matrix multiplication is a perfectly reasonable way of doing 3D graphics, when you don't have a GPU. They were just starting to become a consumer product at that time: https://fabiensanglard.net/3dfx_sst1/
-
Found a program I wrote in 1981 and decided to bring it back to life
The set of things you had to worry about is just .. different. My ancient programmer credentials from 1996: https://github.com/pjc50/ancient-3d-for-turboc
Back in the day, you had:
- single processor
-
Dissecting the Apple M1 GPU, part I
Is this where I post the code I wrote twenty-five years ago to do 16-bit fixed-point 3D rendering? https://github.com/pjc50/ancient-3d-for-turboc
The target architecture was a 33MHz 486 PC running in "real" (ie sixteen-bit) mode. While hardware floating point was sometimes available (DX systems) it was quite slow.
trualias
-
The IAB loves tracking users. But it hates users tracking them
They've settled on a set of features and non-features, similar to how we do it with threat indicators. If it's error prone for threat indicators it's error prone for user tracking and vice versa.
There are reasons not to care. For instance in the threat indicator space false negatives (a threat which is not caught) doesn't cause nearly the pucker as a false positive (something which is not a threat which is flagged as one). Their calculus and minimum may be driven by somewhat different objectives, because their audience is advertisers not security practitioners.
You can still 1:1 addresses to purposes and if you see crosstalk you can draw conclusions. Their normalization is lossy; that's the point.
The cynic in me notes that given the absolute lack of originality in password choice, similar lack of entropy could be seen in 1:1 mappings and perhaps they can infer that if you're hansolo@ and they're example.com, that the email address you'd use is han.solo+example@. The cynic also says: that's on you.
But damn, I'm looking better all the time: https://github.com/m3047/trualias
-
Ask HN: Publish old projects even though the source code embarrasses you by now?
If it has "artistic" or other redeeming value, go for it. Write a README or blog (or three) covering what's unique or important, or how it fits into some historical narrative. Just be clear with yourself on what you expect to get out of it, and how much work you're willing to put into feeding your pet.
I published something once which was three lines of code. It was useful; anyone could do it, but nobody did (a modem dialing script, of all things). The (often multipage) requests for releases to publish were an unexpected annoyance; I always tried to respond politely that I didn't feel it manifested the requisite originality to be a protected work, and that if they printed the email out and sent it to me with a self-addressed stamped envelope I'd sign it and send it back.
I publish https://github.com/m3047/trualias (checksummed on-the-fly email aliases) even though I consider the code far from perfect: it works, it defines a grammar (which I'm happy with), and it has (pretty comprehensive) tests for that grammar. The most important aspect in my opinion is the grammar and a working proof of concept. (To my bemusement it also has the most stars of any of my projects on GitHub, go figure.)
-
Using a catch-all domain is a mistake
The phone thing has veered into outright fraud. Twitter just paid a $150,000,000 fine to the (US) FTC for letting advertisers match on telephone numbers provided for 2FA.
I am really tired of people selling my burner phone to the credit people; and no, I don't own that phone number. Prove I do.
Take my local credit union. Please. Jackasses let someone have access to my checking account. I don't bank online with them either, or I didn't, but last summer was trying to talk to them about a refi and I had to register online and they wanted a phone for 2FA. So of course instead of calling the land line, which is clearly and incontrovertibly mine, they called the burner. Several times.
Eventually I answered it with "fuck you you frauds" and they were "oooh sir, call me back on my direct line" so I tried... from my land line in the same area code, you get the idea... and their system won't route the call to their fraud department. So I ignored them for a couple of weeks.
Seriously they were so incompetent that when the actual fraudsters were probing, the first transaction was a /deposit/. When they were finally trying to clean their mess up, they /credited/ me the same amount. I'm the one who figured it out and told them well you gave me 2x their original deposit, when you really should have debited the amount in the first place.
People like that are not going to safeguard your information.
Ob relevance: I have my own reasons for not wildcarding domains and use this instead: https://github.com/m3047/trualias
What are some alternatives?
mesa - Mesa 3D graphics library (read-only mirror of https://gitlab.freedesktop.org/mesa/mesa/)
K-BOOM - An Atomic Bomberman clone that runs on 80286, featuring video (1997).
transmit - Final Project for Distributed Web Systems (Fall 2016)
libphonenumber - Google's common Java, C++ and JavaScript library for parsing, formatting, and validating international phone numbers.
z80porter - Port writer/tester for Z80-based systems running CP/M
AnonAddy - Anonymous email forwarding
irooster - Turn your Mac into a $2,000 alarm clock
keepassxc - KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
lunchplanner - (VERY old code I keep for self reference, this is supposed to be a joke anyway)
uid2docs - Documentation Repository for Unified ID 2.0
fx-private-relay - Keep your email safe from hackers and trackers. Make an email alias with 1 click, and keep your address to yourself.