It seems your project is at a really early stage. Almost none of the links on the page work, which is too bad, because it could have provided more background information on your goals and wishes. The only thing that seems to work is login through Google, which is a bit much for a demo site.
What's going to be the edge above the already excellent https://bgp.tools ?
You could have a _somewhat_ static blog and incorporate something like Webmentions[0] for comments or replies. For example, Molly White's microblog[1] shows the following text below the post:
Have you responded to this post on your own site? Send a webmention[0]! Note: Webmentions are moderated for anti-spam purposes, so they will not appear immediately.
I find this method to be a sweet spot between generating content on your own pace, while allowing other people to "post" to your website, but not relying on a third-party service like Disqus.
I found this document[0] very insightful. It's quite a long read, but gradually introduces the concepts needed for double-entry bookkeeping.
I think the main advantage is that you can granularly keep track of the movement of money, stocks, commodities, etc., and their conversions. As a day-to-day example, it gives you the ability to follow, for example, invoices received (Liabilities or Accounts Payable), transactions on a bank account (Assets), and what you are going to spend (or at some point, have spent) (Expenses).
This separation allows you to, for example, enter an invoice you've received on January 1 in Accounts Payable, with a corresponding value in Expenses. At this moment, nothing happened yet, it's simply an administrative transfer of some amount from an asset account to an expenses account (the sum of these transfers must be zero, so one amount is negative whereas the other amount is positive. See [0] for more details).
As a result, this gives you insight in what still needs to be paid. Once a transaction for that invoice enters your bank account on, for example, January 10, it gets "paid" to Accounts Payable, thus giving you a link between an invoice, its payment, and finally the amount spent. (This concept also works the other way around, see this sibling comment[1], where it's also extended into working with multiple accounts.)
I do like how it has some brutalist web design elements. With regards to drop-shadow colours on the /symbols page, it doesn't provide additional structure, so I would choose either none or a grayscale tint. Or, if you prefer colours, choose as many distinct colours as there are categories, such that they provide that additional structure.
The symbols on that page could be a bit bigger, though, as they are the main subject. (I changed 1.125rem to something like 1.6rem for text-lg; that works, but it could get a bit crowded with the clickable arrow on lower resolution screens).
I'm not a huge fan of things that move; the offset of a block of symbols, as well as scaling of an individual symbol block when hovering seems a bit too much. I would do either, but not both.
Disclosure Timeline:
- 21.10.2025: Submission of initial version of this report.
Upcoming Timeline:
- 24.10.2025: Submission of a talk for 39th Chaos Communication Congress (39C3). No technical details shared.
- 21.12.2025: Disclosure of this report on https://seclists.org/fulldisclosure/
- 26-31.12.2025: If accepted by content team, 39C3 Congress talk regarding this report
I'm surprised to see that this isn't published on fulldisclosure yet, though there is a talk on GPG vulnerabilities scheduled for 39C3: https://fahrplan.events.ccc.de/congress/2025/fahrplan/event/... . 60 days from report to full disclosure is... tough.
Yes, dnsdiag is a solid toolbox — it’s great for digging into DNS issues at the packet level. This project is aimed more at benchmarking and monitoring resolvers over time, so they complement each other well: dnsdiag for diagnostics and troubleshooting, dns‑benchmark‑tool for comparative speed and health checks.
> Same with What's New modals, some people will benefit from learning these things (notably power users?), but they'll annoy others.
I think power users are most annoyed by those modals. It prevents them from doing the exact thing they were planning to do. Instead, they'll have to reinterpret what the application is telling them, consider it to be irrelevant (most of the times), and then pick up whatever they were planning to do. This creates friction.
I don't need the application to tell me a sidebar was introduced. I see that immediately because it differs from the layout I'm already used to. And then I'm annoyed they added the sidebar, because it takes up space without offering relevant new functionality.
Most, if not all, Asian take-out / restaurants in NL still use a TUI for registering your order. Several motorcyle retailers in NL use a TUI for parts management, invoicing, repair tracking. In both cases, people operating these systems develop muscle memory for their everyday usage. I'm not sure if it's still in use, but for at least a decade since 2005 or so, the local university's student canteen used an in-house developed TUI for selling snacks and drinks.
And if you stretch the definition of TUI a bit, the Bloomberg terminal is a fascinating example.
> if you stretch the definition of TUI a bit, the Bloomberg terminal is a fascinating example
The Bloomberg Terminal uses several different UI methodologies depending on use case -- many functions (applications) are absolutely TUIs whereas Launchpad is more mouse-driven.
> In both cases, people operating these systems develop muscle memory for their everyday usage.
I worked as a UX designer at Bloomberg and when we had to modify existing functions we were careful to maintain shortcuts and keyboard navigation. In a couple cases we even ended up re-implementing UI bugs that one or more users had grown accustomed to. I've never worked anywhere quite so committed to backward UI compatibility, but that came at the expense of a steep learning curve.
I had to reverse engineer the 1980s style ASW screen and replicate it, bugs and all. It had on-screen side effects where hitting TAB would cause numbers to recalculate according to a buggy LIBOR interpolation rule that persisted until ASW got replaced around 2010. Yet traders would take ASW as gospel.
I spent many evenings hand-marking dozens of Bloomberg screen prints to satisfy Accounting that my calculations were right and our Bloomberg operators were getting fooled.
I never worked on ASW or its replacements, but assuming they fixed the calculations in one of the newer swap curve functions I also wouldn't be surprised if some poor developer had to add a "compatibility mode" with the old calculation to avoid breaking someone's longitudinal analysis or satisfy some important user who prefers a stable calculation to a correct one.
It seems your project is at a really early stage. Almost none of the links on the page work, which is too bad, because it could have provided more background information on your goals and wishes. The only thing that seems to work is login through Google, which is a bit much for a demo site.
What's going to be the edge above the already excellent https://bgp.tools ?
reply