You might have noticed I’ve turned the feeds off.
Relax. Your runners will pool messages until I turn it back on.
I’m conducting a mixed signals operation to ensure you’re protected from your network. They’re actively targeting some of you.
I’ll flip the switch back on when it’s done. This needs to happen. We’ve got to shut off their eyes.
IRCTHULU just got google indexed. I need to fix that title for the next crawl.
-C
The Presenta layer is complete.
Presenta is an “example” ui. I hope someone comes along and builds a more robust and featured UI — but it works, and it works on mobile phones.
The Example UI is crude, simple, and functional.
The API and UI will be moved to alpha, and will be publicly expo’d later today.
This version should be rather sturdy.
An announcement with url’s will be made shortly after the new services are up.
I’ve decided to take the Presenta example UI in a different direction.
Since this will be primarily tailored for google-indexed log viewing and identity research, we need to have something more palatable to the index crawlers than would easily be provided by a static html page.
So, I’m moving it to be a drill-down style navigation with breadcrumbs and making it PHP based to speed things up a bit.
[Log Selector] -> [Log Viewer] -> [Identity Research]
[Network] -> [Channel] -> [ Date Start, Date End]
[Log]
[Host Research] | [Ident Research] | [User Research]
[ Host, Associated Idents[], Associated Users[] ]
[ Ident, Associated Hosts[], Associated Users[] ]
[ User, Associated Hosts[], Associated Idents[] ]
-C
The final layer is now in early draft.
I have not yet exposed the API to the public yet as I’ve ended up reshaping alot to make it easier to build sites on top of it.
Presenta is going to have a red white and blue theme. Here’s a screenshot of where it’s at currently before I start dropping in the identity research and cross-referencing modals windows.
The API serving the data from the data tier is complete enough to begin building the UI.
IRCThulu is now moving to the sample UI development which draws from the API. The API will be polished up to provide more features as determined from the building of the sample UI. This is the last piece before the project status can move forward. During this iteration I will also be moving the REST API to a server allowing the public to query it, marking the first point at which data is served publicly from what is now the world’s largest IRC logging system.
Sneak Peak: Larynx is using DJANGO REST SWAGGER to document the API so as it evolves you’ll have a nice reference from which to build your own UI from.
IRCThulu is still in a prototyping phase.
At the current time of writing, the data backend is active.
Runners are the people who run the TENTA layer components on their system.
The first generation of runners are actively doing this now and these clients have consistently been feeding hundreds of thousands of records to the DATA layer.
While many channels are being recorded and the data is shaped as expected, the larynx component which will feed the records to the UI in a read-only fashion is pending completion.
Larynx is a REST API. I am considering moving away from the Django Rest Framework due to the burdensome development processes associated with it which would compromise the guerrilla model of prototype development being used to be more consistent with project goals.
Once a basic API is complete enough a sample UI will be developed entirely in static HTML.
Between now and then, a dedicated iteration of development will take place to streamline configuration of all components to better allow them to be hosted on all separate servers. This iteration will also automate the process of bundling for deployments in a fashion that does not require centralized control. This already exists for the Tenta layer, but currently standing up DATA and PRESENTA components requires hands on configuration and minor code changes.
This site will be the new home for the IRCTHULU project.