After 20 months and nearly 1000 commits, we're releasing version 1.0 of LiveKit. This also includes 1.0 releases for these client SDKs:
- JS 1.0
- Swift 1.0 (iOS and MacOS)
- Kotlin 1.0 (Android)
- Flutter 1.0
- React Core 1.0 and React Components 1.0
- Unity Web 1.0
This looks amazing and it is open source.
WebRTC "enables Web applications and sites to capture and optionally stream audio and/or video media, as well as to exchange arbitrary data between browsers without requiring an intermediary". Think of Zoom or Google Meet. Now you can built it into your own system.
One of the most distinguishing features of "web3" is the sheer level of handwaviness surrounding it. While you can find no end of press releases, Twitter crypto bros, and venture capitalists extolling the virtues of web3, you will have a much harder time finding any definition that's not so full of buzzwords that it becomes meaningless.
Generally speaking, web3 is an umbrella term to refer to the "future of the Internet", which believers say will be decentralized and based on the blockchain. Proponents tend to tout how data won't be controlled by "Big Tech", and how it will be uncensorable and egalitarian. There is, however, no shortage of examples in this timeline of how many "web3" projects are indeed centralized in similar ways to Big Tech, as well as instances where "uncensorable" or "unmodifiable" platforms have removed or modified data.
Skeptics of web3 tend to point out that decentralization was a founding tenet of the Internet and is not something that is only (or best) achieved with the blockchain. They also tend to point out the enormous environmental impacts of blockchain technology (particularly proof-of work blockchains, including Bitcoin and Ethereum). They also often mention that an awful lot of web3 projects sound quite a bit like Ponzi or pyramid schemes, and question the lack of regulation, oversight, and taxation that makes fraud, tax evasion, and other criminal behavior particularly rampant in the space.
Ideas described as web3 tend to incorporate some of the following:
- various cryptocurrencies
- decentralized autonomous organizations (DAOs)
- decentralized finance (DeFi)
- non-fungible tokens (NFTs)
- smart contracts
Yeah we are a web3 skeptics as well. web3isgoinggreat is a fantastic blog dedicated to cover this issue.
Real-Time Bidding (RTB) operates behind the scenes on websites and apps. It tracks what you are looking at, no matter how private or sensitive, and it records where you go. Every day it broadcasts this data about you to a host of companies continuously, enabling them to profile you. This report presents the scale of this data breach for the first time.
- RTB is the biggest data breach ever recorded. It tracks and shares what people view online and their real-world location 294 billion times in the U.S. and 197 billion times in Europe every day.
- On average, a person in the U.S. has their online activity and location exposed 747 times every day by the RTB industry.
- In Europe, RTB exposes people’s data 376 times a day.
Privacy on the web is terrible. The industry needs to be much better.
Now it has
- Zero Byte Reads
- Multi-value header matching
- HTTP/3 Support
- Multiple configuration sources
- Http.Sys delegation
- APIs for Middleware
They recently introduce their first SQL database in their offering based on SQLite
Read replication With D1, we want to take configuration off your hands, and take advantage of Cloudflare's global network. D1 will create read-only clones of your data, close to where your users are, and constantly keep them up-to-date with changes.
Batching D1’s API includes batching: anywhere you can send a single SQL statement you can also provide an array of them, meaning you only need a single HTTP round-trip to perform multiple operations. This is perfect for transactions that need to execute and commit atomically:
Embedded compute With D1, it will be possible to define a chunk of your Worker code that runs directly next to the database, giving you total control and maximum performance—each request first hits your Worker near your users, but depending on the operation, can hand off to another Worker deployed alongside a replica or your primary D1 instance to complete its work.
Backups and redundancy D1 will automatically save snapshots of your database to Cloudflare's cloud storage service, R2, at regular intervals, with a one-click restoration process.
Importing and exporting data If you’re not creating a brand-new application, you may want to import an existing dataset from another source or database, which is why we’ll be working on allowing you to bring your own data to D1.
then they introduced Pub/Sub based on MQTT-based Messaging
Critically, one of our priorities is to cover as much of the MQTT v5.0 specification as we can, so that customers can migrate existing deployments and have it “just work”. Useful capabilities like shared subscriptions that allow you to load-balance messages across many subscribers; wildcard subscriptions (both single- and multi-tier) for aggregation use cases, stronger delivery guarantees (QoS), and support for additional authentication modes (specifically, Mutual TLS) are just a few of the things we’re working on.
In summary, now you can run a full fledged web system on cloudflare using a RDBMS (D1), store large files on R2, implement the backend using Workers, handle eventing using Pub/Sub and host the system frontend using Pages - all at the cost of almost nothing on tops of cloudflare massive infrastructure.
For .NET stack, you can deploy a Blazor Web Assembly project on Pages.