735 karma · joined December 22, 2011
I once accidentally paid for AppleCare with apple pay (a mistake), so when at some point I switched phones I had to get new secondary card numbers tied to my physical cards. The old secondaries went away when I wiped my old phone, so AppleCare was no longer able to draw the monthly payment. The number in the invoice was likewise not the original physical card number, but some other number.
Whether the secondary numbers are easier or impossible to track is certainly a question, but I believe there's always a number.
(You need to setup your DNS to respond in a certain way for a canary domain)
CLIPS is one of those definitely underrated gems, many many thanks for what you are doing!
David Grann is a well known New Yorker contributor and, before the book, has also written an article named "Lost City of Z": https://www.newyorker.com/magazine/2005/09/19/the-lost-city-...
That's good and it's actually the Perl way, Perl was always about helping getting stuff done.
> CloudABI is no longer being maintained. It was an awesome experiment, but it never got enough traction to be sustainable. If you like the idea behind CloudABI, please consider looking into the WebAssembly System Interface (WASI). WASI's design has been inspired by CloudABI.
https://github.com/NuxiNL/cloudlibc
edit: https://github.com/bytecodealliance/wasmtime/blob/main/docs/... is a good reference and also mentions the Capsicum framework (https://www.cl.cam.ac.uk/research/security/capsicum/). Which is present in FreeBSD for several versions btw.
You can group tag messages on mutt with any pattern you'd like and then move them. Or, you can limit your view to what you want to move, select some and then move them.
1. Returning values different than what the MIB says.
2. Missing values that are not optional in the MIB.
3. Broken getnext code that returns an incorrect oid, which could even lead to loops. Net-snmp will detect it, but proper snmpwalk gets broken.
4. Broken getbulk repeater code that can cause crashes if the repeater is too large.
5. OIDs that will crash/stall/slow the agent.
6. Implementations that cannot handle simultaneous requests. Admittedly this is notoriously difficult to achieve: most MIB implementation code is not reentrant for various reasons.
7. SNMP SET is very difficult to implement, cannot be meaningfully used for almost anything beyond extremely simple stuff.
8. UDP encapsulation can cause MTU/fragmentation issues that are a nightmare to debug. Net-snmp actually implemented transports such as TCP and it was very nice, but it never caught on in general.
Bonus, there is also the not related to implementation problem of:
9. The query semantics of SNMP are non-existent, and the indirection in the SMI is cumbersome, which means that as a client/manager you'll have to do all sorts of data wrangling to find what you need.
> Point of view is worth 80 IQ points
The wisdom of it is that it suggests a profound change in the point of view of what intelligence is. Although I suspect this must have been researched well before the quote, it summarizes so beautifully the fact that intelligence isn't just some single-dimensional hard coded genetic trait, but something transferable and even contagious through language. Love that quote.