概念: Coordination problem

Recursive coordination portfolio

+1  

Portfolios are really effective at managing bets and risk. You own a little bit of everything to return as much as you can. What if we could manage our coordinations with others as a portfolio. People could decide to change their behaviour to benefit someone else. Such as writing documentation how some of their code works. Or adding an API

YAML 想法

Everyone announces what they ARE doing.

Everyone comments on everybody else's what they are doing and says what they could do to benefit me. How to do that thing you're doing in my interest.

If the person doing the thing accepts that work, they add it to their portfolio.



(别通知) (可选) 请,登录

稍等一下。我想,我会让项目结果通知与评论通知一起进行,这样我们就可以参与这个过程,同时在它们所属的地方分享工作结果——在特定项目下。

Wait for a bit. I think, I'll make projects results notifications go along with comment notifications, so that we could engage with this process, while sharing work results where they belong -- under particular projects.


我一直在研究负载平衡循环,但我的第二个想法是负载平衡虚拟进程 虚拟进程是一系列嵌套的循环。 软件可以创建为一系列过程。 我想学习如何安排流程并因此安排循环。 我需要在每个循环上调用 .tick ,以推进其执行。 我希望流程具有不同的优先级并相互成比例 我可能会为每个进程执行 2 个循环。 我还想为相互依赖的进程安排 .ticks

I've been looking at load balancing loops but my second idea is to load balance virtual processes A virtual process is a series of loops some nested. Software can be created as a series of processes. I want to learn how to schedule processes and consequently loops. I need to call .tick on each loop, in an order to advance its execution. I want the processes to be of different priorities and proportionate to eachother I might execute 2 loops of one process for every one of another. I also want to schedule .ticks for processes that depend on eachother


我发现了如何实现智能 DNS。

您可以将 PowerDNS 与管道后端一起使用,并使用请求 IP 地址动态解析 DNS 查询。这可以找到您附近的服务器。

然后您可以对 Haproxy 进行健康检查,以找到一个健康的负载均衡器。那就是智能DNS。

I found out how to implement intelligent DNS.

You can use PowerDNS with the pipe backend and to dynamically resolve a DNS query using the requests IP address. This could find servers that are near you.

Then you can health check Haproxies to find a load balancer that is healthy. That is intelligent DNS.


我现在正在考虑可扩展性,特别是使用开源软件的可扩展性。 我在一个项目中提供了一个跨 3 个可用区的可靠应用程序,其中包含 3 个 F5 负载平衡器和 DNS 负载平衡。 F5 知道其他 F5,并且可以对其他可用区域中的其他 F5 进行负载平衡。

I am now thinking of scalability, specifically scalability using open source software. I was on a project that provided a reliable application across 3 availability zones with 3 F5 load balancers with DNS load balancing. The F5 knew of other F5s and could load balance to other F5s in other availability zones.


今天我在思考时间和杠杆的不可逆转性。

我们使用他人创造的东西来获得最大的成功机会。例如,我们使用亚马逊等行业标准公司进行购物或在我们的软件中使用开源软件,我们不需要手动创建所有内容。

考虑到每一个决定都有机会成本,而且你不能在蛋糕烘烤时从蛋糕中提取鸡蛋,你如何推断​​周围的东西会留下来?我们需要使用可靠的公司并依靠可靠的技术来取得成功。 我们也有限制我们或使我们受益的心理模式。

Today I'm thinking of the irreversibility of time and leverage.

We use things created by others for maximum opportunity of success. For example we use industry standard companies such as Amazon for our shopping or use open source software in our software, we don't need to create everything by hand.

Given there is an opportunity cost to every decision, and you cannot extract egg from a cake when it's baked, how do you reason what is around to stay? We need to use solid companies and rely on solid technologies for success. We also have mental patterns that either limit us or benefit us.


我要做一个社会实验。在接下来的几天里,我将在这个评论页面上写下我的想法和所做的事情。

尝试与我协调是您的责任,我会尝试与您协调。

这可以是一个低技术的递归协调组合组织空间。

从我与您的协调开始,Mindy,我将提供我对您的想法和感受的反应。集成 ODOO 听起来很辛苦。我怀疑这会很困难并且需要很多时间。付出很多努力是可以实现的。您还需要学习如何托管 ODOO 多租户,以便您可以在您的计算机上运行它以供我们使用,除非您希望我们也设置它,这可能也需要大量时间并且需要大量设置工作并保持最新。 我想专注于同时可以实现和令人印象深刻的解决方案。

今天我花了一天的时间在 Quora 上工作,有人解决了我的这个 stackoverflow 问题 - https://stackoverflow.com/questions/72882207/whats-the-mathematical-formula-for-a-nested-loop 我设法得到了一个平衡的笛卡尔积。我想负载平衡循环。当你有一个三层的嵌套循环时,你运行的内循环比外循环多。我编写了代码来对循环进行负载平衡。

我有一个想法,可以将类似于 Erlang 的并发添加到任意数量的循环中。

我也在考虑为我的 M:N 调度程序编写一个简单的解释器。并使用简单的汇编程序将代码写入内存。并执行它。然后添加多线程。我希望能够创建新线程并在多个线程中运行代码。 Java 和 C

I'm going to do a social experiment. I'm going to write what I'm thinking of and doing on this comment page over the next few days.

It's your responsibility to try coordinate with me and I'll try coordinate with you.

This can be a low tech recursive coordination portfolio organising space.

To start with my coordination with you Mindey, I shall provide my reaction to your thoughts and feelings. Integrating ODOO sounds like hard work. I suspect it shall be difficult and take a lot of time. It's achievable with lots of effort. You would also need to learn how to host ODOO multitenanted so you could run it on your computer for us to use, unless you expect us to set it up too which is probably also uses lots of time and is a lot of work to set up and keep up to date. I want to focus on solutions that are achievable and impressive at the same time.

Today I spent my day working on Quora and someone solved this stackoverflow problem of mine - https://stackoverflow.com/questions/72882207/whats-the-mathematical-formula-for-a-nested-loop I managed to get a balanced Cartesian product. I want to load balance loops. When you have a nested loop of three levels, you run the inner loop more than the outer loops. I wrote code to load balance the loops.

I have an idea for adding similar to Erlang concurrency to any number of loops.

I am also thinking of writing a simple interpreter to my M:N scheduler. And using a simple assembler to write code to memory. And execute it. Then add multithreading. I want to be capable of creating new threads and running code in multiple threads. Java and C# did it so why can't I? It's hard but I kind of know what I need to do. I wrote a parser before. I have written assembly before. I need to write some assembly patterns and write code to generate that assembly. I'll need a new thread primitive. And primitives for compareAndSet and loops. I can write basic assembly to do all these things then write a generator of that assembly and parameterise it. It's like Java's template interpreter.

It won't be portable but it would be good


// 每个人都宣布他们在做什么。

这需要“状态更新”或“项目作为状态”,这些流是公开的。

我对此有一些想法(发布协议),它与 as-of-yet-unpublished-yet-viewable-with-this link [https://0oo.li/method/111001/0x111111? l=en

// Everyone announces what they ARE doing.

This requires "status updates" or "projects as statuses", those streams be public.

I have something emergent in my head about this (publishing protocol), and it is related to as-of-yet-unpublished-yet-viewable-with-this link https://0oo.li/method/111001/0x111111?l=en&secret=2a9ede86681f0bb4f7b7485c913488b3&c=26cc7033 vision for Odoo. I'm thinking of that Python ERP as a P2P publishing system. It currently is not P2P, but it has a good base. For example, it has eBay, banking and other integrations, that allows it to be a central assets management place for businesses. I don't see why it couldn't shine as a central place to manage social publishing, and inter-operation between thinking spaces like Infinity (I'll have a chance to finalize the API for that), LessWrong, Halfbakery, and other similar places. Publishing follow up streams of events about projects would then be quite easy too.


语言