Not sure if this is a difficult ask, but any way to get a json/xml/yaml/api dump of this page? Why: annotation of data collected by mac address accounting. Mostly looking to tie name to IP. I've occasionally used tool assistance to parse the previous HTML page. Not sure if anyone else does [or would if easier] do this. Open to other suggestions. -Michael
-----Original Message----- From: MICE Discuss <MICE-DISCUSS@LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Wednesday, June 28, 2023 4:10 AM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE Participants List
The MICE participants list is now built from IXP Manager: https://micemn.net/participants.html
If there is something wrong about your entry, please let me or Jeremy know. See below about port discrepancies, first.
I want to specifically thank Dustin Frandle of South Front Networks. He started this effort with JavaScript code to convert a standard IX-F JSON export into a participants table. While I ended up going a different direction (for reasons discussed below), he got the ball rolling.
Jeremy and I wanted to retain the contact addresses, which IXP Manager only outputs in the IX-F export if you are logged in. (And, despite my request, they remain firm in that position and refuse to allow customization.)
Additionally, I wanted to retain the ports, since our current process has Cologix using the website as the LOA/CFA. (We may want to move to a more standard approach on that, but I didn't want to put that change into the critical path of getting the participants list automated.)
Unfortunately, despite a previous request and my re-request for it, the IXP Manager maintainer has taken a firm position that the IX-F JSON export should not be customizable. So I cannot easily tweak the template to output emails when unauthenticated or add additional information for ports.
IXP Manager does support the idea of a custom member export, and INEX (the exchange primarily behind IXP Manager development) does use that for a custom JSON output. However, that requires building the desired output from scratch. I figured if I was going to do that, I might as well just output HTML directly. That way, I only have one thing in one language (PHP) to worry about, rather than two things (PHP + JavaScript).
Granted, there are some cons too. I'm not 100% happy about any of this. But, ultimately I had to make some decision to get it done, and that's where I landed.
I did the best I could with the responsive design. There are a couple of pre-existing bugs on edge cases (e.g. when your size falls at 991.xx so it's not <= 991 but also not >= 992, which is maybe only possible on HiDPI displays) that affect the whole site. This page in particular is not ideal on mobile, but I did what I could. If you've got better ideas, please let me know.
----
There are a couple port discrepancies that I've asked Jeremy to review:
702 Communications * Bluepeak Broadband Visions * G-Core Labs * HBC * LTD Broadband Omnitel * Paul Bunyan South Front Truestream * US Internet
* I'm pretty sure these were wrong/outdated on the old list and correct in IXP Manager / on the new list.
-- Richard