Mettā

Resumé

Unknown — Wed, 05 Nov 2025 00:00:00 +0000

Brief</h1>

Name: Berkus Karchebnyi</li>
Current position: Principal Software Engineer, Microsoft M365 Core</li>
Seeking position: (Principal) Rust Software Engineer, Rust Technology Lead</li>
Email: berkus+jobs@madfire.net</a></li> </ul>
Skills</h1>

Strong collaborative leadership (good at organizing people and keeping them involved).</li>
Strong technical documentation and communication ("write it down", ELI5).</li>
Excellent knowledge of Rust (own projects</a>), over 8 years programming experience, including no_std environments.</li>
Also a member of Rust Embedded WG</a>.</li>
Excellent knowledge of C++ (templates, exceptions, standard library, bughunting), over 20 years programming experience.</li>
Experienced in various infrastructure tools (source control systems - Git, Pijul, jj; scripting in Ruby, Python, shells; build pipelines - GitHub, CircleCI, Jenkins).</li>
Experienced software localiser to other languages (Russian/English).</li>
Some experience in SwiftUI.</li>
Some experience in Android development, mostly Java- and JNI-based.</li> </ul>
Previous jobs</h1>
Microsoft microsoft.com</a></h2>
Principal Software Engineer. June 2024 — Present time.
Developing a suite of SDKs to accelerate migration of core C# services to Rust. My focus areas include open-telemetry and C# interop areas. Working on the interoptopus</a> project in OSS to improve C#-Rust interop.
Twilio twilio.com</a></h2>
Principal Software Engineer, Engineering Team Lead. April 2016 — May 2024.
Initially maintained an Android Chat SDK, improving JNI layer and fixing bugs. Grew to lead the Conversations SDK team, which included Android, iOS and JavaScript developers producing corresponding platform SDKs.
Led C++ libraries upgrade for SDKs, and led migration from C++ to native implementations (Swift and Kotlin). One of the Kotlin native SDKs has been published to OSS - twilio-sync-sdk</a>.
Led the effort to document the largely undocumented body of SDK code and converted it into "specs first" approach, which then let the SDK team parallelise writing three platform implementations.
Exquance exquance.com</a></h2>
Co-founder, CTO, developer. June 2012 — April 2016.
Managed teams of outsource developers, set up CI/CD infrastructure, developed iOS (UIKit) and Windows (WPF, Visual Basic) applications.
Implemented a mandatory CI pipeline for all components of the software, speeding up the development cycle; removed the "works on my machine" development mentality.
Skype skype.com</a></h2>
Software Engineer. November 2004 — April 2013.
Worked on Linux version of Skype UI using Qt library. Then worked on Linux audio support for Skype on consumer electronics devices (TVs, MIDs, etc).
Implemented from the grounds up full audio stack support in Linux Skype UI, including ALSA, PulseAudio, and OSS4. Integrated with pre-existing audio library infrastructure. Implemented Android audio support using OpenCORE.
Infinet Wireless, Inc. infinet.ru</a></h2>
Software Engineer. June 2004 — July 2004.
Read more</summary> Implemented wireless router monitoring interface using native Infinet libraries and Qt. Implemented Qt3 version of monitoring software. Integrated with existing framework libraries. </details>
IA Neftegaz.RU neftegaz.ru</a></h2>
Web Developer. July 2003 — May 2004.
Read more</summary> Maintained a large Oil & Gas industry portal web site acting as both a web-programmer (writing PHP and Ruby code) and as a server administrator. Wrote a speed-optimized website statistics analyzer in Ruby. Implemented a big system upgrade by installing a new Linux system with fresh software and greatly optimized it for speed. Achieved better performance of the system by integrating better log files analysis. Improved site visitors log detail level compared to the previous implementation. </details>
Visual Mechanics vismech.ru</a></h2>
Web Developer. September 2001 — July 2003.
Read more</summary> Coded PHP for a lot of websites including several web shops. Took part in a big web-based document flow software project. Implemented web shop framework in PHP, which was used for several further projects. Created a visual table constructor</a> tool for a website backoffice. </details>
AG Courier zauralmedia.ru</a></h2>
Systems administrator, Developer. June 2000 — July 2001.
Read more</summary> Maintained a small network of non-linear video editing</a> PC stations. Wrote assorted in-house software.

Designed and implemented a small CRM tool in PHP.</li>
Reverse-engineered binary storage format used by the broadcasting hardware.</li>
Designed and implemented a news ticker (crawl) text input editor application for TV broadcasting in C++. The editor allows a human operator to enter multiple entries, enable and disable them based on a given schedule, and generate dumps for a set of calendar dates in a format supported by the video broadcasting hardware. It was used to organize and simplify maintenance of crawling texts by keeping an archive, automatically expiring entries, allowing quick search and replace within an archive. Usability (UX in particular) was of utmost concern during design phase - operator has to enter as many as 500 entries in one run, hence things like keyboard shortcuts, dictionary-based autocompletion, quick search and replace were implemented. The system was implemented using Borland C++ Builder.</li> </ul> </details>
Open Source Software projects</h1>
Metta OS metta.systems</a></h2>
Author, overall design, Rust and asm programming.
Metta is a novel operating system for creative nomads with hi-tech devices and ubiquitous Internet access. I'm exploring the future of Human-Machine interaction using augmented reality, associative data storage, data ownership, publishing and filtering facilities.
Vesper metta-systems/vesper</a></h2>
Author, overall design, Rust and asm programming.
Vesper is a single-address-space nanokernel for Metta. I am exploring a way to make minimalistic kernel where policy decisions will be mostly outside the privileged core while still performing decently. This is also an exercise in low-level no_std Rust.
aarch64-cpu rust-embedded/aarch64-cpu</a></h2>
Maintainer, Rust programming.
Co-maintaining ARM cpu crate as part of Rust Embedded WG. The crate provides essential low-level ARM abstractions for embedded systems and is widely used in the Rust Embedded ecosystem (55 official dependent crates on crates.io).
Interoptopus ralfbiedert/interoptopus</a></h2>
Maintainer, Rust and C# programming.
Contributing support for C#-Rust ffi interop, implemented `Wire<T></code> serialization format to support passing more complex types through the ffi boundary.`
`Criterion `criterion-rs/criterion.rs</a></h2> Maintainer, Rust programming. Revitalizing criterion through community efforts after it has been in neglect for a long while. Started a new org with the intent of allowing wider community contributions. GG metta-systems/gg</a></h2> Maintainer, Rust and Svelte programming. Contributing to GG (a GUI for Jujutsu VCS) by consolidating and staging multiple community PRs in repository while @gulbanana is busy or away. This is mostly a testing playground, with the hope that PRs get merged back into the main repository over time. Pijul nest:pijul/pijul</a></h2> Maintainer, Rust programming. Contributing to a powerful distributed VCS based on theory of patches. I work on improving the user experience, command-line interface and adding a GUI. Amarok amarok.kde.org</a></h2> Co-auther, C++ programming. Amarok is the KDE audio player. I have joined the team at version 0.6. I took part in localization effort, visual and user interaction design, system architecture design. I am no longer an active part of the development team. Akregator KDE/akregator</a></h2> Author, overall design, C++ programming. A KDE RSS aggregator. I wrote Akregator in the time KDE had no RSS aggregator software. Akregator is highly appreciated by many users. It has earned Application of the Month</a> status in January 2005 (interview</a>). It is now included in main KDE packages. I am no longer an active part of the development team, the version of Akregator you see on GitHub is a new rewrite without my contributions (over 20 years have passed). Hobbies</h1> I am interested in competitive multiplayer games (ARC Raiders ftw!), 3D printing and embedded electronics and software. I love making open source projects easier to maintain - by providing CI pipelines and release-plz publishing, so if you want to be able to easily publish your crates and have them continuously tested and well, give me a shout!

Premature generalization Unknown — Tue, 07 Oct 2025 00:00:00 +0000 It is hard for less experienced developers to appreciate how rarely architecting for future requirements / applications turns out net-positive. </blockquote> John Carmack, 18 June 2021</a> Treacherous Metaphors Unknown — Mon, 21 Jul 2025 00:00:00 +0000 The most treacherous metaphors are the ones that seem to work for a time, because they can keep more powerful insights from bubbling up. </blockquote> Alan Kay, 1984 related video</a> Web Design Museum Unknown — Thu, 26 Jun 2025 00:00:00 +0000 Web Design Museum - Golden Age of Web Design</a> Some nostalgic vibes! Prototyping in Rust Unknown — Thu, 23 Jan 2025 00:00:00 +0000 Prototyping in Rust</a> Approaches to make Rust prototypes easier than in any other language, even Python. Replace app icon automatically Unknown — Fri, 27 Dec 2024 00:00:00 +0000 Want to have your own custom app icon in the dock, but it always gets replaced by an app update? Inspired by the talks to replace Warp.app icon (in multiple</a> issues</a> on GH</a>), I've made a simple tool to automatically replace the icon after the app update. Learning JTAG Unknown — Fri, 08 Nov 2024 00:00:00 +0000 To understand how JTAG works I recommend a series of articles by Aliaksandr Kavalchuk. He describes details of the protocol and accompanies the text with amazing illustrations. Check it out: Part 1: Overview</a></li> Part 2: Debugging</a></li> Part 3: Boundary Scan</a></li> Part 4: BSDL</a></li> Part 5: Usage Scenarios</a></li> Part 6: Security</a></li> </ul> Also, there are a few articles from other authors, describing JTAG in a more practical way: JTAG Hacking unknown SSD drive controller</a></li> JTAG, SSDs and Firmware Extraction</a></li> </ul> Half-knowledge Unknown — Fri, 11 Oct 2024 00:00:00 +0000 Half-knowledge is very communicable; not so knowledge. </blockquote> Mary Coleridge OSdev tooling finished Unknown — Tue, 03 May 2022 00:00:00 +0000 January through May I was on and off on the project, fixing chainofcommand to work with the chain loading, in particular fighting the UNIX console and the TTY operations. Now the entire thing works, finished and merged into the main develop</code>ment branch. After that I started prodding the MMU setup and DTB (DeviceTree) parsing. OSdev tooling continued Unknown — Tue, 28 Dec 2021 00:00:00 +0000 This month I spent honing the tooling story. Partially it was driven by the desire to Rewrite All the Things in Rust, and partially by my attempt to integrate all the tooling in a convenient for me way to do things. Along the way I've done some refactoring and added support for Raspberry Pi 4-specific code. OSdev tooling Unknown — Thu, 11 Nov 2021 00:00:00 +0000 Since my first attempt at OSdev in x86 assembly I've constantly strived to make my setup comfortable. With rust I finally achieved a nearly zero-configuration flow. There are still some tools to install but they are either a cargo install just</code> away or entirely optional. Developing an OS in Rust gives an opportunity to apply the benefits of the entire Rust ecosystem, so I've decided to maximally utilise what it has to offer. Complex Systems Unknown — Wed, 15 Apr 2020 00:00:00 +0000 A simple system may or may not work. A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system. </blockquote> John Gall's Systemantics</a> Rust on Sipeed Longan Nano board Unknown — Sun, 17 Nov 2019 00:00:00 +0000 My Longan Nano board</a> has arrived and I tried to run Rust on it. It's a great success and here's how. Nano is a RISC-V microcontroller (GD32VF103) with impressive GPIO capabilities and connectivity - it has a serial, JTAG and USB Type-C ports plus numerous GPIO pins on breakout connectors. It is also very well documented: there are board schematics, CPU and Peripheral datasheets, and numerous programming examples. Escaping from old ideas Unknown — Sun, 03 Nov 2019 00:00:00 +0000 The difficulty lies not so much in developing new ideas as in escaping from old ones. </blockquote> John Maynard Keynes</a> Building WASM with Rust Unknown — Mon, 07 Oct 2019 00:00:00 +0000 There are several options to build Rust into WebAssembly. 📦 cargo-web</a> </a> was the preferred way for 📦 yew</a> </a> , but nowadays yew also supports 📦 wasm-bindgen</a> </a> and this opens up some possibilities for javascript interop. Useful cargo commands Unknown — Mon, 30 Apr 2018 00:00:00 +0000 Some additional cargo commands exist to provide unprecedented level of support and extensibility to regular cargo. Here's a list of commands I use (will be updated over time, last update 2025-01-12): Reboot to Rust Unknown — Fri, 09 Mar 2018 00:00:00 +0000 Fast forward four years...</h3> And the landscape is changed again. The idea to write a secure robust kernel and then build a secure robust operating system on it is still there. However, there are new tools, technologies as well as new hazards</a>. One of the new tools is Rust language. The tenets of Rust are speed, safety and fearless concurrency</a>. This makes it nearly ideal language for writing new secure software, including kernels. Robigalia project is also looking towards semi-automatic assurance of Rust-based software</a> by leveraging the MIR intermediate representation as containing the semantic information about the program, which we can reason about. Looking forward to seeing what this brings, meanwhile I set out to write an equivalent of seL4 kernel in Rust for 64-bit systems. I've intentionally dropped support for 32-bit systems at the moment, it should be possible to retrofit 32-bit support into the kernel APIs - they will just become either slower or more limited. Just don't focus on these now. So the primary targets are x86_64</code> and aarch64</code>. And I'm going to start by collecting the Embedded Rust community knowledge and using it to build a baremetal Rust "kernel" that could speak to some UART device, starting with Raspberry Pi 3 board - since I have that one and have JTAG debugger for it. Let's go. Xargo Build with Sublime Unknown — Mon, 19 Feb 2018 00:00:00 +0000 How to build your xargo package in Sublime</h3> Imagine you have a special OSdev project in Rust that you want to build from within Sublime Text. So you fire up the editor, choose the Tools</code>>Build System</code>>New Build System…</code> and write a little simple configuration file: { "shell_cmd": "xargo run --target aarch64-vesper-metta", "keyfiles": ["Xargo.toml"], "working_dir": "$project_path/vesper", "env": { "RUST_TARGET_PATH": "$project_path/vesper/targets/" }, "quiet": false } </code></pre> You save it and hit Cmd+B. Kotlin Unknown — Fri, 19 May 2017 00:00:00 +0000 Kotlin is the new Java with the announced Google support, and here is how it compares to other languages: Scala vs Kotlin</a></li> Swift vs Kotlin</a></li> Why you should totally switch to Kotlin</a> - contains more comparisons and highlights</li> </ul> License Unknown — Wed, 18 Jan 2017 00:00:00 +0000 Content license</h3> All non-code blog content is licensed under Creative Commons BY-NC-SA</a>. Code license</h3> All source code files and snippets found on this blog, unless otherwise explicitly noted, are licensed under the terms of Blue Oak Model license below. Blue Oak Model License</h4> Version 1.0.0 Purpose</h5> This license gives everyone as much permission to work with this software as possible, while protecting contributors from liability. Acceptance</h5> In order to receive this license, you must agree to its rules. The rules of this license are both obligations under that agreement and conditions to your license. You must not do anything with this software that triggers a rule that you cannot or will not follow. Copyright</h5> Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it. Notices</h5> You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to https://blueoakcouncil.org/license/1.0.0</a>. Excuse</h5> If anyone notifies you in writing that you have not complied with Notices</a>, you can keep your license by taking all practical steps to comply within 30 days after the notice. If you do not do so, your license ends immediately. Patent</h5> Each contributor licenses you to do everything with this software that would otherwise infringe any patent claims they can license or become able to license. Reliability</h5> No contributor can revoke this license. No Liability</h5> As far as the law allows, this software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim. Слои интернетов Unknown — Mon, 07 Mar 2016 00:00:00 +0000 (беркус: я болдом выделяю понравившуюся терминологию, чтобы было за что зацепиться) Я пока не знаю, с чего начать, поэтому попробую начать с чего-нибудь. Вот как бы я объяснял текущее положение вещей самому себе лет десять-пятнадцать назад? Что стало с Сетью?</h2> Metta architecture Unknown — Mon, 07 Mar 2016 00:00:00 +0000 System works as a federation of autonomous services distributed onto different machines across the network. The API between these services are described using interfaces. Each interface has a certain specific semantic. Interfaces also specify points at which separation of work could happen, where one service could delegate the work to another without bothering too much about where this service is located and how this work will be arranged. There are storage and computation services. They have some common properties, like latency (time between sending a request and receiving a result), and some specific ones, like capacity (the amount of data which can be stored onto the storage device). These values become the basis for QoS - quality of service control, which manages latency and bandwidth constraints to keep services useful, but not let less important services interrupt more important ones. For example, you wouldn’t want your audio-video conference to be interrupted by background file-sharing activity. Metta grabber (uvvy) Unknown — Mon, 07 Mar 2016 00:00:00 +0000 (Disclaimer: здесь и далее читать как «для меня», «в моём сегодняшнем понимании» и т.п.) Metta is about belongings.</h2> Метта в её текущем описании мной понимается как новый способ подходить к своему скарбу: к нажитому непосильным умственным трудом, приобретённому за презренные деньги, подаренному ближними людьми или ухваченному где-то по пиратскому случаю. Метта для меня выглядит не как новый способ «работать» — взаимодействовать — с материалом. Метта для меня — новый способ не терять нажитое, держать его под рукой, не заботиться о бренном. (Это ни плохо, ни хорошо, а product boundaries) Omnia metta mecum porto. Поэтому, когда вопрос стоит о том, какой же должен быть конкретный недалёкий инструмент, построенный на metta-идеях, я в первую очередь думаю о граббере. Metta - mashable techdemo storyboard Unknown — Mon, 07 Mar 2016 00:00:00 +0000 Fire up a console, we'll use two consoles for this demo - one will run the streaming video server, another will be our client. The $ </code></pre> prompt denotes a command line where you enter your commands. Metta outbound access framework Unknown — Mon, 07 Mar 2016 00:00:00 +0000 Постановка вопроса</h2> Смотри, у нас все ноды связаны друг с другом зашифрованными каналами. но это в идеале и если считать что нынешнего WWW нету. но он на самом деле есть и к нему надо как-то достукиваться. разрешать незашифрованный коннект? только для определенных нод или для всех? если для всех, чем это отличается от андроида с браузером? если не для всех, то какой added value - должны быть агентi, сортирующие и фильтрующие всё. в общем вопрос достукиваться пока звучит так: для получения информации из существующей инфраструктуры (зачем) тебе надо ее как-то оттуда вытаскивать. (кому) это может быть какой-то общий аггрегатор, но учитывая всякие разные настройки приватности они все равно привязываются к каким-то твоим логинам там и тут. "кому" это абстрактный юзер в вакууме у которого друзяки в фейсбуке и жожо. у него нужда болтать с друзяками Как было в свое время со скайпом, все друзья разом не пересядут на новую платформу, поэтому шлюзы очень важны. Anti-Mac Interface quote Unknown — Tue, 21 Jan 2014 00:00:00 +0000 A computer environment in which both humans and computer-based agents have active roles implies a mixed locus of control. The user's environment will no longer be completely stable, and the user will no longer be totally in control. For general sanity, users still need to determine the balance of control in the different parts of their environment, they need the means to find out what their agents have been up to, and they need mechanisms for navigating in the wider networked world; </blockquote> Anti-Mac Interface site</a> Manifesto Unknown — Wed, 15 Jan 2014 00:00:00 +0000 Metta</h3> Rewind and replay. Go back to the roots of the Internet: decentralised, self-maintained and self-healing. No policies, no political correctness and no overwhelming commercial interest. Own your data again. Take it back from Facebook or Google, Microsoft or Apple. Take it back from the government. Distributed across many nodes, resilient to server failures, agencies peeking, unsolicited censorship - we go all the way back to what Internet used to mean. We are working on a technology stack, enabling re-decentralisation of the Internet. We build humane, adaptive and affective computing environment. Yours, again. We call it Metta. Circles of Trust and Attention</h3> Heads or tails, attention or trust. There's so much noise in the world, we're broke on our attention. We have none left. Good thing the unlimited credit line is open for trust, right? Never mind the fine print. We gave all our trust (and then some) to the wrong people. We are now locked in a status quo with most private parts of our lives used for profit, to maximise shareholders returns - or worse. Big fish with long tails of our content in behemoth datacenters. Suggested pages, products, places and friends. Living a suggested life. Metta out</h3> You still can be what you choose to be. Egocentric internet is not technically worse to what we have now - and the upsides are huge: No realistic way to impose data lock-in on you.</li> Nigh impossible personal data centralisation (for monetization, analysis, targeting).</li> Extremely complicated censorship, control over your free speech.</li> Pseudonymous-friendly environment.</li> No administration, no policies - boiling soup of ideas and possibilities, fully autonomous small "clubs of interest" bubbles, with their own rules and self-governance.</li> </ul> Built on top of conventional Internet, building from within it, Metta strives to build The Net of the future. Join Metta development</h3> It won't get any better - unless we work it to be. You can observe the trend, the way things are going: corporate and government control over your data and over your life are not going away anytime soon. Metta works right now. Join us on github</a>. Bring in your ideas and thoughts, help us re-decentralise the internet, take our data back, break out from all forms of control by design. Be free! मेता Progress report: Audio services, congestion control Unknown — Sat, 28 Dec 2013 00:00:00 +0000 Progress report</h3> It's been a while since last update, so I wanted to show a little bit of what's happening in the repositories. Derived intelligence Unknown — Fri, 13 Dec 2013 00:00:00 +0000 Our lives are increasingly mediated by, filtered through, and experienced via technology. A plethora of mechanisms capture, store, examine, manipulate, derive intelligence from, and share our information. This happens either with our knowledge, consent, and intent or without. </blockquote> Aral Balkan site</a> Using libsss for communication Unknown — Wed, 30 Oct 2013 00:00:00 +0000 Introduction</h3> Structured Secure Streams provide secure encrypted and authenticated data connection between endpoints. It's a simple userspace library written in c++14 and boost. It uses standard UDP to provide reliable delivery, multiple streams, quick connection setup, end-to-end connection encryption and authentication. SSS is based on experimental, unfinished project under UIA - SST</a>. SSS is an experimental transport protocol designed to address the needs of modern applications that need to juggle many asynchronous communication activities in parallel, such as downloading different parts of a web page simultaneously and playing multiple audio and video streams at once. Bootstrapping node problem Unknown — Fri, 25 Oct 2013 00:00:00 +0000 The problem</h3> Absolutely every network needs a way to find a node's peers, for establishing connections, propagating updates and maintaining network integrity this is essential. Overlay networks based on DHT or similar mechanisms (Kademlia</a>, Chord</a>) use peer nodes to figure this information out. Usually in such network you have a node ID, 128 or 160 bits in length, which uniquely identifies the node and node's position in routing tables. Based on this ID you simply look up the IP address. But wait, look it up from where? libSSS progress Unknown — Mon, 07 Oct 2013 00:00:00 +0000 Structured Secure Streams</a> library is getting in shape. With C++11 and Boost it's relatively simple to write even without the tremendous help of Qt. Although I had to write some helpers which are factored into a separate library - grab arsenal</a> if you want - some nice things there are byte_array</code>, settings_provider</code>, binary literals, hash_combine</code>, make_unique</code>, contains()</code> predicate, base32 encoder-decoder and opaque big/little endian integer</a> types. Flurry Unknown — Sun, 08 Sep 2013 00:00:00 +0000 To continue work on the structured streams transport I decided to get rid of the XDR data representation, as well as slightly awkward boost.serialization</code> library. Compiling LLVM trunk Unknown — Thu, 23 May 2013 00:00:00 +0000 Just a very simple thing to try and build Clang with polly, LLVM, libcxx, lldb and lld from trunk. Isn't it? Using git, because cloning a git repo with full history is still faster than checking out svn repo with serf. Yay! These instructions are not for copy-paste, they show general idea and should work with minor changes. btsync Unknown — Thu, 25 Apr 2013 00:00:00 +0000 Here's a new technology from BitTorrent</a> that might be bad news because I'm working on about the same features in MettaNode and at the same time might be good news because my implementation is going to be open source from the start, and I still plan to use less of so-called servers in the infrastructure. But for the much loved p2p world it's absolutely awesome, gone to install and play with it. PS. OSX client is pretty unstable, crashes, loses added folders, but that's apparently a beta. PPS. It quickly went into proprietary no-sources-available mode, not relevant for me anymore. libsss or where to go from SST? Unknown — Wed, 24 Apr 2013 00:00:00 +0000 In the mean time, I'm slowly rewriting Bryan Ford's SST (Structured Streams Transport) library, using modern C++ and boost.asio, in the hopes that it will be easier to port to Metta. I called it libsss (Structured Secure Streams). As this work progresses I also plan to enter the description of this protocol into an RFC document, so there will be some reference point for alternative implementations. Current specification progress is available in libsss repo</a> on github. I'd like to take the chance to thank Aldrin D'Souza for his excellent C++ wrapper around openssl crypto functions</a>. He kindly licensed it for free use under BSD License. update: Oct 2014 repository moved. File sharing design considerations Unknown — Thu, 21 Mar 2013 00:00:00 +0000 Some issues that need tackling in design of file sharing (see Brendan's post here</a>): The issue of trust: right now, the file is only distributed across a range of devices you manually allow to access your data. This doesn't solve the problem per se, but just makes it easier to tackle for the initial implementation. The data and metadata could be encrypted with asymmetric schemes (private keys), but that doesn't give full security. assocfs note Unknown — Mon, 24 Dec 2012 00:00:00 +0000 While I'm still dabbling with fixing some SSS issues here and there I thought I'd post an old excerpt from assocfs design document. It's a non-hierarchical filesystem - in other words, associative filesystem. It's basically a huge graph database. Every object is addressed by its hash (content addressable, like git), knowing the hash you can find it on disk. For more conventional searches (for those who does not know or does not care about the hash) there is metadata - attributes, drawn from an ontology and associated with a particular hashed blob. NAT update Unknown — Sun, 09 Dec 2012 00:00:00 +0000 Turns out the problem was on the server side setup. After moving the server to Amazon EC2 cloud and setting up UDP firewall rules punching started working. At least that takes some burden off my shoulders. The regserver connection is not very robust, that should probably be modified to force-reconnect the session once you open the search window again. NAT woes Unknown — Sat, 01 Dec 2012 00:00:00 +0000 There's a slight fault with uvvy not quite punching through home routers' NAT. While the UDP punching technique described by Bryan Ford should generally work, it doesn't account for the port change hence the announced endpoint addresses as seen by the regserver are invalid. Responses don't go back because the reply port number is different from what router's NAT assigns. On patents Unknown — Mon, 12 Nov 2012 00:00:00 +0000 Over time I’ve come to believe that software should not be patentable; most any idea in software is something that a moderately experienced programmer could invent, and the definition of patents requires that patents be non-obvious. Nuff said. </blockquote> Patrick Wyatt</a> of Blizzard Events interface Unknown — Wed, 15 Aug 2012 00:00:00 +0000 I've ported events, sequencers and event-based communication primitives from Nemesis. It's a little bit messy at the moment (mostly because of mixing C and C++ concepts in one place), but I'm going to spend the autumn time on cleaning it up and finishing the dreaded needs_boot.dot</code> dependencies to finally bootstrap some domains and perform communication between them. Obviously, the shortest term plan is timer interrupt, primitive kernel scheduler which activates domains and events to move domains between blocked and runnable queues. There's some interesting theory behind using events as the main synchronization mechanism, described here</a> in more detail. For the vacation time I've printed some ANSA documents, which define architectural specifications for distributed computation systems and is very invaluable source of information for designing such systems. The full list of available ANSA documents can be found here</a>. A System Designer's Introduction to ANSA is available here</a>. Good reading. Meddle Grammar Unknown — Tue, 07 Aug 2012 00:00:00 +0000 Types</h2> Built-in types include int8</code>, int16</code>, int32</code>, int64</code> for signed integer types of given bit size, card16</code>, card32</code>, card64</code> for unsigned integer types with given size, octet</code> for 8-bit bytes, float</code> and double</code> for single and double precision floating point numbers, boolean</code> for true and false, and types integer</code> and cardinal</code> with generic unspecified bit size for use in non-local interfaces, these two types will be marshalled to a transport type of necessary size to represent the value. The types int8</code>, int16</code>, int32</code>, int64</code>, card16</code>, card32</code>, card64</code> are considered "unsafe" or "dangerous" types and can be used only in local interfaces (or should they be convertible to integer/cardinal for network communication?). octet</code> is considered safe and could be used to represent arbitrary sequences of bytes (sequence<octet> binary;</code>) Custom types can be enum</code>, set</code>, range</code>, type</code> alias, sequence</code>, array</code> and record</code>. Graphic dependency resolution Unknown — Mon, 16 Jul 2012 00:00:00 +0000 I needed to quickly check how much of Nemesis support has to be ported over before I can start launching some basic domains. I used a simple shell one-liner to extract NEEDS dependencies from the interface files. It's easy to do in Nemesis because of explicit NEEDS clause in each interface (would be nice to add this functionality to meddler, it also has the dependency information available). Here's the shell one-liner: echo "digraph {"; find . -name *.if -exec grep -H NEEDS {} \; | grep -v "\-\-" | sed s/ *NEEDS //g | sed s@^\./@@ | sed s/\.if// | awk -F: {print $1, "->", $2}; echo "}" </code></pre> This generated a huge graphic</a> with all dependencies, which I then filtered a bit by removing unreferenced entities and culling iteration after iteration. The resulting graphic is much smaller and additionally has a hand-crafted legend (green - leaf nodes, yellow - direct dependencies of DomainMgr and VP, my two interfaces of interest). This shows I need to work on about 10-12 interface implementations to be able to run domains. And my ticket tracker of choice, bugs-everywhere now has an entry 7df/0fe 'Generate dot files with dependency information in meddler'. Time to sleep. Brief update on Metta Unknown — Fri, 13 Jul 2012 00:00:00 +0000 I've been working on toolchain building script, now at least on Macs it's possible to build a standalone toolchain for building Metta and you can download it and try to build it yourself. All necessary details are descibed on SourceCheckout wiki page</a>. There is followup work to remove dependency on binutils and gcc (gcc will probably go first, then once lld is mature enough I could get rid of ld/gold). Another update is about type system. The operations on type system are implemented now, I can successfully register type information and query it - some examples of that are in the recently released iso image R925</code>. Next up is fixing some of naming context operations so I can actually create and operate hierarchical naming contexts. The real romance is out ahead Unknown — Fri, 13 Jul 2012 00:00:00 +0000 The real romance is out ahead and yet to come. The computer revolution hasn't started yet. Don't be misled by the enormous flow of money into bad defacto standards for unsophisticated buyers using poor adaptations of incomplete ideas. </blockquote> Alan Kay via folklore.org Type systems and introspection Unknown — Thu, 14 Jun 2012 00:00:00 +0000 Since I've decided to approach the system development from both low-level and high-level perspectives, one of the applications I have in mind for demo purposes is a little console tool which lets you activate various parts of the system, list available services and call operations on available interfaces. Imagine a little tool that allows you to pick a video file, seek it to a particular time and play it frame by frame, then run face recognition on each frame and make a database of recognized faces. Being able to make such applications "mashup style" by just fiddling with text and pictures in the command line should enable people to create more and more interesting tools from the basic building blocks presented by the system. This tool would need to inspect installed interfaces and types of the running components and be able to construct calls to these components directly from the command line. This requires introspection, or the ability to describe structure of objects in the system. At the moment I'm working on the extension of meddler that allows to generate introspection data from the interface IDL. It is generally simple and then the next step would be to somehow register this information in the system when a new interface type is introduced. This is harder and requires some design effort. In the first approach of course only boot image is loaded, so registering types is very simple. Next up is actual introspection interface - how to know what format a particular data type is and how to marshal/unmarshal it for the purpose of interchange and operations calls on interfaces. See this little script</a> for the possible demo storyboard. Museum of Endangered Sounds Unknown — Sun, 03 Jun 2012 00:00:00 +0000 Museum of Endangered Sounds</a> Hehe, this is a truly amazing museum! Sending network packets Unknown — Fri, 11 May 2012 00:00:00 +0000 A little sidetrack into the world of PCI probing and NE2000 network card emulation. Wanted to have a taste of sending and receiving network packets inside my little OS, so I went and implemented PCI scanning (extremely simple) and NE2000 card driver (fairly simple too, their doc is quite good although misses some crucial points). So, after some fiddling I was able to send a packet and receive it through the bochs virtual network card. I've then connected bochs to the host network card and stared at network packets for a while. Cool stuff. Here's the screen dump of the sent and then received broadcast packet. IRQ11 enabled. Finished initializing NE2000 with MAC b0:c4:20:00:00:00. Received irq: 0x0000000b Packet transmitted. Packet received. Received packet with status 33 of length 68, next packet at 82 0x004f0064 ff ff ff ff ff ff 28 cf da 00 99 f5 00 10 48 65 ......(.......He 0x004f0074 6c 6c 6f 20 6e 65 74 20 77 6f 72 6c 64 21 00 00 llo net world!.. 0x004f0094 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ </code></pre> sjlj and exception handling Unknown — Sun, 08 Apr 2012 00:00:00 +0000 Of course, the clang's implementation of setjmp</code> is very generic and uses quite an abstraction of program state, which makes it hardly suitable for the ad-hoc local exception support I'm using. Since my requirements for setjmp were quite simple (just give me back my damn registers and stack frame), I went and implemented a very custom-tailored versions __sjljeh_setjmp</code> and __sjljeh_longjmp</code> which do just what I need. With that stuff</a> out of the way, my entire boot sequence now works and I can finally fiddle with more interesting stuff. Type system and introspection, here we go. Bret Victor's Kill Math Unknown — Mon, 02 Apr 2012 00:00:00 +0000 Bret Victors Kill Math</a> How to stop worrying and love your visualization tools. Optimizations Unknown — Sun, 25 Mar 2012 00:00:00 +0000 The reason for not booting was simple - Clang, seeing that target is Pentium 4 and above, optimized some memmoves into SSE operations. Bochs didn't expect that. Now everything boots up until exceptions, at which point I believe the __builtin_longjmp</code> primitive fails. Debugging it. Clanged now Unknown — Sat, 24 Mar 2012 00:00:00 +0000 Anyway, I've done doing the craziest port of recent times - at the same time GCC to Clang and from waf 1.5 to 1.6. Quite a bit of quirks to work around. waf has changed a lot internally, and from occasional backtraces I still see that I'm using compatibility mode somewhere. Oh well, one day when I'm bored… Clang is also full of quirks. First, I had to build a cross-gcc for it anyway, because otherwise it totally refuses to link or assemble anything. Second, the freestanding standard C headers are not quite finished it seems - stdint.h for example spits out about 20-30 warnings about redefined macros, so I had to disable -Werror</code> for now just to get it to compile. Third, the generated code, obviously, doesn't run. I got only first couple functions of kickstart bootloader to work in bochs, after that it just GPFs. Now if it keeps raining tomorrow like today, I'll certainly will go and look what happens there, otherwise it might have to wait until next weekend (actually, in two weeks). Magic Ink Unknown — Sun, 05 Feb 2012 00:00:00 +0000 Magic Ink</a> Highly recommend this read to all programmers and designers. Very inspirational. It intersects with Metta's ideas of supporting creativity freedom, and is written a lot better than I could ever dream to write myself. Font rasterization theory and techniques Unknown — Mon, 03 Oct 2011 00:00:00 +0000 Font rasterization theory and techniques</a> Metta MMU module init Unknown — Tue, 07 Jun 2011 00:00:00 +0000 MMU initialisation</h3> First off, we start by loading the needed modules - mmu_mod</code>, frames_mod</code> and heap_mod</code>. mmu_mod</code> will allocate and map the first chunk of memory to use. It does so without knowing much about memory allocation - just takes a first fit chunk from the physical memory map, passed to us by the bootloader. Parts of this memory will be used by frames_mod</code> and heap_mod</code> as well, so we need a way to know how much memory they would need. A historical moment Unknown — Sat, 23 Apr 2011 00:00:00 +0000 OMAP3 beagleboard.org # mmcinit OMAP3 beagleboard.org # fatload mmc 0 0x82000000 kernel.bin reading kernel.bin 640 bytes read OMAP3 beagleboard.org # go 0x8200024c ## Starting application at 0x8200024C ... hello, world! ## Application terminated, rc = 0x0 </code></pre> Apple's Attention to Detail Unknown — Tue, 31 Aug 2010 00:00:00 +0000 In July 2002, Apple filed a patent for a “Breathing Status LED Indicator” (No. US 6,658,577 B2</a>). They described it as a “blinking effect of the sleep-mode indicator in accordance with the present invention mimics the rhythm of breathing which is psychologically appealing.” </blockquote> Apple's attention to detail is legendary. Metta progress report one Unknown — Fri, 23 Jul 2010 00:00:00 +0000 I have cleaned up the booting mess more or less and now my loader is able to enter the root domain - the startup component, which initialises all other components in order and passes control on to userspace loader component, which is supposed to finish system initialisation by starting up all user interface services. It is better to live alone Unknown — Thu, 31 Dec 2009 00:00:00 +0000 "330. It is better to live alone, there is no companionship with a fool; let a man walk alone, let him commit no sin, with few wishes, like an elephant in the forest." </blockquote> The Dhammapada To remain the web weavers Unknown — Wed, 30 Dec 2009 00:00:00 +0000 To remain the web’s weavers and not its ensnared victims, we must merge with our electronic exocortex, wiring greater memory, thought processing and communication abilities directly into our brains. </blockquote> James Hughen About Unknown — Wed, 30 Dec 2009 00:00:00 +0000 To dream a dream as big As big could ever dream to be Then dream a dream ten times as big As that one dream you see. </blockquote> Hi and welcome to Metta hub!</h2> Here I develop decentralised communication systems for the future, called Metta nodes or uvvies. You can join in by helping us develop, document, promote and use the software. What I'm working on and why</h3> My biggest project so far is Metta - a humane, social and multimedia OS. While multimedia and social are pretty much all over the place, humane part is still unexplored widely. Bits and pieces are appearing in different systems from different vendors, but they still haven't integrated enough. A user interface that helps and optimizes workflows, rather than gets in the way.</li> A scalable system that works across all your devices - laptops, smartphones, TVs - without the need to explicitly manage every single file, address book record or configuration setting.</li> An environment that doesn't only passively executes your direct commands, but a living federation of agents working on your behalf to bring you the best and most interesting things you wouldn't even find yourself - something much more useful than idly browsing through 9gag.</li> Something that could become your actual exocortex device, after some sufficient advances in neural interfacing development.</li> </ul> This is a huge undertaking and given that neither Apple nor Microsoft is near achieving it yet, chances are I won't make it alone either. But I have to try anyway. Ongoing Projects</h3> One side - the low-level platform, which supports secure, distributed, federated, peer-to-peer systems - is being developed at metta</a>. It supports an entirely different programming paradigm of component-based composable system, where interfaces between components make it possible to remote parts of the system without ever changing the application itself; and introspection facilities allow to build mashable applications out of existing components without ever needing anything else. A fast, portable, peer-to-peer foundation platform. Another side - the user-space interaction and social facilities - developed at uvvy</a>. Uvvy is a tool for fully decentralized communications - grab data you like and store it forever, share data with your friends, start chats, voice or video calls, form groups by interest, transparently keep all your notes between all of your devices; all based on a simple ideas of UIA</a>. It is still in its infancy and only base transport protocol is done, work is now going on on overlay routing network. This project is no less ambitious, but better progress is being made here, since it is a simple application ran on regular off-the-shelf operating systems. Grabbing the data</h3> The grabber comes from Latin saying "Omnia mea mecum porto" - grab, snapshot things I need and forever keep them available to me. This is one of the current research topics in the humane part. How much data do I need? Where do I need it? How my life changes if I always can find what I need, wherever I am? Final target is to have a bunch of clients for desktop and mobile platforms (Win, Mac, Linux, Android, iOS) as well as own operating system implementation (Metta) running together. Support or contact</h3> Ping @berkus</a> if you have any questions or ideas. Be free! मेता

Mettā

Resumé

Skills</h1> Strong collaborative leadership</strong> (good at organizing people and keeping them involved).</li> Strong technical documentation and communication</strong> ("write it down", ELI5).</li>

Previous jobs</h1>

Open Source Software projects</h1>

Premature generalization

Treacherous Metaphors

Web Design Museum

Prototyping in Rust

Replace app icon automatically

Learning JTAG

Half-knowledge

OSdev tooling finished

OSdev tooling continued

OSdev tooling

Complex Systems

Rust on Sipeed Longan Nano board

Escaping from old ideas

Building WASM with Rust

Useful cargo commands

Reboot to Rust

Xargo Build with Sublime

Kotlin

License

Blue Oak Model License</h4> Version 1.0.0</p>

Purpose</h5> This license gives everyone as much permission to work with this software as possible, while protecting contributors from liability.</p>

Acceptance</h5> In order to receive this license, you must agree to its rules. The rules of this license are both obligations under that agreement and conditions to your license. You must not do anything with this software that triggers a rule that you cannot or will not follow.</p>

Copyright</h5> Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it.</p>

Reliability</h5> No contributor can revoke this license.</p>

No Liability</h5> As far as the law allows, this software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim.</em></p>

Слои интернетов

Что стало с Сетью?</h2>

Metta architecture

Metta grabber (uvvy)

Metta - mashable techdemo storyboard

Metta outbound access framework

Anti-Mac Interface quote

Manifesto

Metta out</h3> You still can be what you choose to be.</p> Egocentric internet is not technically worse to what we have now - and the upsides are huge:</p>

Join Metta development</h3> It won't get any better - unless we work it to be. You can observe the trend, the way things are going: corporate and government control over your data and over your life are not going away anytime soon.</p> Metta works right now.</p>

Progress report: Audio services, congestion control

Progress report</h3> It's been a while since last update, so I wanted to show a little bit of what's happening in the repositories.</p>

Derived intelligence

Using libsss for communication

Bootstrapping node problem

The problem</h3> Absolutely every network needs a way to find a node's peers, for establishing connections, propagating updates and maintaining network integrity this is essential.</p>

libSSS progress

Flurry

Compiling LLVM trunk

btsync

libsss or where to go from SST?

File sharing design considerations

assocfs note

NAT update

NAT woes

On patents

Events interface

Meddle Grammar

Graphic dependency resolution

Brief update on Metta

The real romance is out ahead

Type systems and introspection

Museum of Endangered Sounds

Sending network packets

sjlj and exception handling

Bret Victor's Kill Math

Optimizations

Clanged now

Magic Ink

Font rasterization theory and techniques

Metta MMU module init

A historical moment

Apple's Attention to Detail

Metta progress report one

It is better to live alone

To remain the web weavers

About

Hi and welcome to Metta hub!</h2> Here I develop decentralised communication systems for the future, called Metta nodes or uvvies. You can join in by helping us develop, document, promote and use the software.</p>

Blue Oak Model License</h4>
Version 1.0.0</p>

Purpose</h5>
This license gives everyone as much permission to work with this software as possible, while protecting contributors from liability.</p>

Acceptance</h5>
In order to receive this license, you must agree to its rules. The rules of this license are both obligations under that agreement and conditions to your license. You must not do anything with this software that triggers a rule that you cannot or will not follow.</p>

Copyright</h5>
Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it.</p>

Reliability</h5>
No contributor can revoke this license.</p>

No Liability</h5>
As far as the law allows, this software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim.</em></p>

Progress report</h3>
It's been a while since last update, so I wanted to show a little bit of what's happening in the repositories.</p>

Hi and welcome to Metta hub!</h2>
Here I develop decentralised communication systems for the future, called Metta nodes or uvvies. You can join in by helping us develop, document, promote and use the software.</p>