In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
The Security Operations Center of CERN is responsible for ingesting, storing and aggregating an immense amount of data each day (around 2.5TB). The main message processing pipeline used to be based on Spark streaming jobs deployed across a cluster of machines, but was still struggling with the daily load. Nowadays, everything is performed by a single Go binary deployed on 4 machines, with enough resources to spare. This talk focuses on why we switched languages, why it works better, as well as some key implementation takeaways.
During the last week of January 2019, 10 developers from 7 different countries gathered at CERN to celebrate the 30th anniversary of the Web by recreating the first browser, the World Wide Web. I will walk you through the process and the challenges of re-creating a 30 year old browser using modern tools.
How can a new database system which manages billions of rows with relatively short lifetime (weeks to months) be designed ?
The system should resemble a Whiteboard:
- data, grouped by given properties form data collections, are added when requested
- data collections are consumed by the requestor
- when not needed any more, data collections are removed by a "Whiteboard sponge" process.
I will show you what options I explored and which one is potentially the best in terms of efficiency.
Static websites are back on the rise. But I don't like writing in Markdown. So in these five minutes I'll show why it's better to write in Org-Mode, and how to convert that to a website with Hugo. All inside Emacs of course.
RISC-V is a fully open source processor architecture. It’s rapidly being adopted by major tech companies as an alternative to ARM licenses. With the advent of the IceStorm toolchain for the Lattice iCE40 FPGA, it’s now possible to construct your own RISC-V processor core and compile code to run on it using exclusively open source tools. This talk will include an overview of the RISC-V architecture, the toolchains for device synthesis and code compilation and will end with a very short demo of a working processor built during the talk!