Fork me on GitHub

Note for everyone... Since I'm not at Cisco anymore, I can't update the Asami repo (nor any of the associated projects). That's OK... I'm going to my own fork for each of them. (Some of these projects started in my account under other names anyway). Hopefully, someone at Cisco will be willing to put a notice in the README for their version of the Asami project, with a pointer to my fork. In the meantime, you'll find Asami, et al, at:

👍 5

I should have thought to do this before leaving. Oops! 🙂


A question for people who use Asami: Internally, Asami uses keyword nodes in the tg namespace (it's deliberately terse). This reflects the history of being sponsored by "ThreatGrid", which was the organization acquired by Cisco that I worked for. Over time, everything that was ThreatGrid was assimilated into Cisco, so it doesn't actually exist anymore, except as a GitHub org. Now that I'm developing Asami outside of any organization, I have been wondering if I should change this terse internal namespace to a. The reasons for this are: • To avoid confusion. People are more likely to understand why a terse namespace is a than tg since it matches the project's name. • Serializing saves a byte. This is actually useful in some places. However, there is one compelling reason to leave it alone, and that's because people may have data that they need to preserve. Hence, I thought I'd ask. What do people think?

👍 6
Jakub Holý (HolyJak)09:03:47

I like a, it makes more sense. Perhaps it would be easier if there was a migration function they could run to make old data compatible with the new way?


Yes, that WOULD help, and it makes sense… it would also take time, and that's so precious that I thought I’d solicit feedback. I don't know how important it is, and I thought I’d ask and see if anyone declared that they'd struggle with the migration