If we want to close Human <-> Machine loop as much as possible(pre-neuralink).
Assuming that today the most efficient way for human to transfer information to machines is via voice.
Assuming for machines to convey rich information to humans that's by printing html.
Then a combination of screen + eye tracking + voice is all you need.
The mouse doesn't make sense anymore.
I definitely trust Google's team (and large trillion dollar companies with sufficient resources to do this) to make reasonable choices for their users... said, perhaps, someone ever? Certainly not me.
(I wanted to write something far snarkier and sarcastic but getting annoyed at google is like getting annoyed at a lawnmower/Oracle. That plus HN guidelines.)
DSLA Protocol | Paris Berlin Tokyo Dubai | DevOps / SRE / DevSecOps | Remote | Full Time
Our team is opening up multiple network engineer positions to further accelerate the development of DSLA Protocol, our Third Party Risk Management (TPRM) solution for developers and infrastructure operators.
Available on a growing number of blockchain networks, DSLA Protocol is a framework that enables anyone to design, roll out and execute peer-to-peer risk management strategies, based on historical application and network performance analytics.
In practice, DSLA Protocol connects stakeholders that want to underwrite risk, with stakeholders that want to hedge against risk, using zero-sum performance prediction markets.
As a DSLA Protocol core contributor, you will be responsible for the continuous improvement of the infrastructure supporting the protocol, our oracles and the other components of our technical stack.
We are looking for ambitious network engineers operating in a full DevOps capacity, with hands-on experience with EVM-compatible and non-EVM networks, Chainlink, Application & Network Performance Monitoring (APM/NPM) GCP, Kubernetes, Hardhat, Ethers.js and Typescript.
DSLA Protocol is a risk management framework that enables infrastructure operators and developers to reduce their users' exposure to service delays, interruptions and financial losses, using self-executing service level agreements (SLA), bonus-malus insurance policies, and crowdfunded liquidity pools.
DSLA Protocol’s flagship use case is to offset the financial losses of Proof-of-Stake delegators and DeFi users, while incentivizing the connectivity, performance and availability of staking pool operators and DeFi service providers.
The Stacktical Blockchain engineer is responsible for the Protocol' Smart Contract efforts to build the current and future products of the platform.
We are looking for a skilled Blockchain Engineer with hands on experience deploying Smart Contracts that are well documented, tested and reviewed while communicating with dApp maintainers(https://dsla.protocol), community and partners.
This is the opportunity to enjoy working in a true Decentralized team in the booming DeFi industry. You will provide quality matching the institutional adoption we are facing.
DSLA Protocol is a risk management framework that enables infrastructure operators and developers to reduce their users' exposure to service delays, interruptions and financial losses, using self-executing service level agreements (SLA), bonus-malus insurance policies, and crowdfunded liquidity pools.
DSLA Protocol’s flagship use case is to offset the financial losses of Proof-of-Stake delegators and DeFi users, while incentivizing the connectivity, performance and availability of staking pool operators and DeFi service providers.
The Stacktical Blockchain engineer is responsible for the Protocol' Smart Contract efforts to build the current and future products of the platform.
We are looking for a skilled Blockchain Engineer with hands on experience deploying Smart Contracts that are well documented, tested and reviewed while communicating with dApp maintainers(https://dsla.protocol), community and partners.
This is the opportunity to enjoy working in a true Decentralized team in the booming DeFi industry. You will provide quality matching the institutional adoption we are facing.
Stacktical | Blockchain & ITSM | SRE / DevOps / Backend | Remote | Full time
DSLA Protocol is a risk management framework that enables infrastructure operators and developers to reduce their users exposure to service delays, interruptions and financial losses, using self-executing service level agreements, bonus-malus insurance policies, and crowdfunded liquidity pools.
We are looking for SRE/DevOps engineers to join the most exciting project of the Blockchain industry:
Passionate Site Reliability Engineer with 10+ years of experience in IT Service Governance and Management, software architecture and software development. Speaks 5 languages and constantly on the lookout to bring more scalable and highly reliable software systems.
Available for contractor/consultant/part-time missions.
Open for exciting opportunities as co-founder|CTO|VP Engineering|Head of Infrastructure at early-stage startups.
That's the trust issue with current agreements we are solving.
If an API is down the bound agreement is enforced instantly with our platform, no lies, no call, no pain.
We are actually onboarding companies to try it out!
https://stacktical.com
TLDR: Because Smart Contracts on the blockchain are the right tool for Secure Digital Agreements.
Paperweight contracts are irrelevant in a world of data
* A Smart Contract is cheaper to publish that the stack of paper handled by lawyers.
* Code is cheap to iterate from whereas traditional SLA are expensive/slow to renegociate.
Over time, SLAs drive behaviors that are focused on delivering a minimum level of service at minimum cost to the provider.
* A Smart Contract is a code you can trust, understand and expect to behave instantly compared to the traditional SLM.
so, are you saying we should replace social media platforms w/ decentralized sharing & aggregation driven by smart contracts? sounds intriguing but daunting
unscheduled outages are always painful and people will always call, I agree.
But instant compensation is doing a better job at damage control that a status page.
Keeping customer satisfaction even in bad situation is key in a world of high availability expectations.
And with a distributed, non partisan metric sourcing about the availability of an API, it's not possible for a Service Provider to lie anymore.
I don’t understand something: what kind of company is so down to the wire with cash flow that an outage requires income within seconds/minutes instead of weeks? Anyone with a financial runway so short that it can be described as “instantaneous” doesn’t sound like a customer you would want to be in business with.
The kind that will make a lot of noise as publicly as possible and create ample work for your support/admin people if you don't keep them happy...
> doesn’t sound like a customer you would want to be in business with
I could say that about most of the companies I have had the dubious pleasure of doing business with! Very few are pleasant when something goes awry even for a moment.
I wrote "buyer," not "user" or "complainer." I have no problem with self-appointed Good Samaritans who leave anti-Lexmark Amazon reviews. But a buyer of a car requiring the manufacturer's gas would understand what he or she was getting into.
Assuming that today the most efficient way for human to transfer information to machines is via voice. Assuming for machines to convey rich information to humans that's by printing html.
Then a combination of screen + eye tracking + voice is all you need. The mouse doesn't make sense anymore.
Links: https://x.com/trq212/status/2052809885763747935