Added the qualifier to the title as web3 understandably earns a lot of eyerolls haha. At the same time, a lot of web3 focused places seem to have a specific mindset about what "should" be done so I wanted to ask here.

I worked in the space at startup (ironically making web2 services to assist in web3 so I’m still an extreme novice). But my time there was a constant push / pull between convention and money and innovation and the unknown. The company I was at would try to appeal to big companies in hopes of finding a product market fit, who looked to us for guidance on what to do in this new space where they hoped to make money. Trend after trend would pass and it would be entertained whether we’d jump on it because product market fit.

The most desirable companies were household names with non-web3 userbases because they meant unprecedented reach. But to make web3 approachable to them, you’d have to define a UX that didn’t exist and would be pulled in a tug of war between two forces. The first mindset optimises for the purest idea of giving the user power— UXs that were obvious about the concepts of transactions and transferrable assets. The other wanted to replicate web2 UXs in web3, to the degree that a user gives temporary control of their wallet to a developer so the developer performs transactions as them.

Then, there is the data and pseudonymity piece. Companies have been taught that data is valuable, and one of the values of a blockchain is an identity that exists outside of any one company. But if all of your assets are on a blockchain— either under your public key or perhaps under a few that might transfer assets only between each other— then your identity can be known (not so private) and also cannot be monopolized and sold (because your data is public).

In the background, as this all happens, is the decentralization argument. At the end of the day, my company used EVM nodes operated by another company (which themselves might be wrappers around something offered by AWS). What is meaningful decentralization alongside specialization of labor? What is decentralization in a world that has billionaires and enormous companies who has the means to buy resources and set up tons of nodes?

Being out of the space now, I do think a decentralized database with immutable scripts, user-managed transferrable assets, and transferrable identity has enormous value. But recently I’ve been wondering how much of that can be accomplished in the private sector. In my time there it felt like the startup needs (enterprise customers, increased ARR) constantly compromised the will for innovation efforts.

I've been looking around online at compatibility for HTML5 browser streaming. It looks like straight up AV1 in a MP4 container is becoming absolutely fine for browser playback on devices.

Is anyone using this on webpages yet? The sooner we move to AV1, the sooner we can have high quality video stored at smaller file sizes, which is a massive bonus.

Right now my company video hosting is purely in MP4 with H264, moov atom to the front as per the requirement, and it plays back on everything with no fallback in a straight HTML5 video container. What's the chance of switching to AV1 and not having to worry about the fallback for the most part?

Edit: I should have used a better title. I used FFMpeg for MP4 and AV1 creation/encoding. This is more about HTML5 video container code and direct AV1 file playback.

Web devs: what's up with this trend? For enterprise apps, I get it…single sign-on needs to detect what your email domain is to send you to your identity provider. For consumers, I feel like it's gotta be one of these reasons:

• Users don't know about the tab key being able to move to other fields on a page
• Mobile users don't really have a tab key, despite there being "previous/next field" arrows on the stock iOS keyboard since its inception (Android users, help me out please)
• Users tend to hit Enter after typing in their username, leading to a form submission with a blank password
• Security, maybe? In the past I have sent a link and a password in separate emails or separate communication methods entirely. Are you hashing/salting these separately for better MITM mitigation?

Did your UX team make a decision? Are my password managers forever doomed to need a "keyboard combo" value for every entry from now on?

Non-devs: do you prefer one method over the other? If so, why?

Tildes maintainers: selfishly, thanks for keeping these together :)

The more I think about it, the more I'm convinced of it.

The biggest selling point of Node folks has been the "single threaded, event driven" model, right? Unlike JavaScript, other languages work on a "blocking" basis i.e. you run a statement or command and the program "waits" until the I/O is complete. For example, you issue open('xyz.txt', 'rb').read() in python and the program waits or blocks until the underlying driver is able to read that whole text file (which could take arguably long time if said file is too large in size).

But with the Nodejs equivalent, you just issue the statement and then pass the "event handler" so that your program is never in the "waiting state". The whole premise of Node/JS event-callback is that "you don't call us, we will call you".

This is all nice in theory but if this were indeed true then Nodejs scripts should be blazing fast compared to Python and even Java considering that most programs we write are I/O heavy and 99% of time, they're just waiting for an input from a File/URI/User? If this event callback model indeed worked as effectively as claimed, Node would have been the numero one and only language being used today?

I think I'm starting to understand why that isn't the case. This whole "single threaded, event driven" thing is just a farce. You can also replicate the same thing that Node.js is doing in your Java or Python too by applying multi-threading (i.e. one thread just "waits" for the I/O in the background while the other keeps doing its job). All you've done here is just handed or delegated that complexity of multi-threading to Node.js?

Realistically, it's impossible to wait or block an I/O request while at the same time also letting the other part of the code engage in other tasks, that's the very definition of multi-threading. Doing "async" is impossible without multiple threads in that sense. Node must have a thread pool of sorts where one of them is engaged in the wait/block while another is running your JS code further. When the wait is over, the control is then passed to the "event handler" function it was bound to in that other thread.

What Node is selling as "single threaded" applies to application or business logic we are writing, node itself can't be single threaded. I feel it's better to just implement multi-threading in your own code (as needed) instead of using something convoluted and confusing like Node.js. What say you?

I've been trying to set up a dev enviornment for Tildes, mainly so that I can actually test my MR (!136), and I've been running into a few issues.

However, since we also have a new influx of people who might be interested in contributing to Tildes, it seems like a good time to collect resources on setting up the dev environment, as well as helping anyone running into issues.

So, if you have issues or advice, post them here! I'll be adding my questions in a comment shortly.

Relevant wiki pages:

• Development / Initial Setup
• Development / General Development Info

Edit: A more recent post on setting up the dev environment on Apple Silicon / M1 Macs

This is more focused towards those that use custom domains for their email. My current plan is up at Zoho for my team in a month, and even though I've used them for the past few years its been hit-or-miss (especially when using third-party apps or programs).

Who do you use? Who do you not trust? Who would you never go back to?

Sidenote: I hope this might eventually kick off a ~privacy group, one day.