ourcat

And we had kill files for spam.

Claude is in the contributor list on the repo.

Actually, after closer inspection of the screen on the third image of the device in the article, there does appear to be a Bluetooth icon.

Confirmed in the Dev Portal. https://docs.flipper.net/one/hardware/wifi-bluetooth

The 'Layers' comparison image suggests that there would be no Bluetooth in the Flipper One. I would have thought that would still be very useful in 'Layer One'?

Genius. And also terrifying.

I call it "furapy".

Nicely done. I started a simple idea/project based on PeerJs (with self-hosted CoTURN) to make a little private 'zoom-like' chat.

I'd been considering doing an Omegle clone too, but have been side-tracked.

I also might take a look at the p2p file transfer ability WebRTC has for some other ideas.

In the video he says the Full-Duplex SDR (Nuand bladeRF X40) hardware can be quite expensive. But he found one on ebay for $270.

Ahhh, WWWBoard. Those were the days!

app.net was great for developers. We made money each month based on user feedback. It was worth the higher membership fee to access all that too.

Sadly, and despite the way it was originally funded (by the users), I believe they took some VC funding, which ultimately killed the platform since it wasn't getting the growth that the investors wanted.

Actually, if Elon wants 'X' to become an 'everything app', one way which that could be done is through opening up to more app devs to build their own apps on the platform, as it used to be. Sadly, I don't think they've got the will or the manpower to do that these days.

I assume this is to cover any losses from them soon making it possible to use the Quest without a Facebook account? ie: The data they will not be able to sell.

The cross-browser support and standardisation for `input=date` (and `input=datetime`) has been notoriously poor for years. It's still only listed as 'partially' supported on some browsers on caniuse.

That's why so many people roll their own.

That's not a million miles away from how Second Life operated (and still does). Where the 'Land' & 'Estates' (and parcels within them) were servers. Each has their own limitations to how many user avatars they can support at one time.

People flock to places they identity with. Buy parcels. Build their own space and communities within communities.

As far as 'voting' and governance goes, I think there's room for development with blockchain login/identity/ownership and Decentralised Autonomous Organisations (DAOs) which support that.

For querying and subscribing to events for defi, using the Uniswap and ETH Subgraphs, it's great for building 'web3' apps.

Nice. But I searched for 'Aluminium'. It gave me results for 'Aluminum' (American English).

I must report about 10-15 of these every week to YouTube. Recently, it's been Shiba Inu due to the pump it's been getting.

Most of the scam live streams I've seen and reported are channels which appear to have been 'taken over'/'hacked' and their content changed or deleted to then kick off a 'giveaway' stream which are all scams.

They all have the same basic layout on screen, so really YouTube's bots should do a better job of detecting them. YouTube are literally recommending content which perpetrates fraud, at this point.

OPML is the tree. RSS are the vines. Items (articles, podcasts etc.) are the fruit.

And with OPML's ability of 'inclusion' (to any remote tree or branch), it makes creation, curation and 'harvesting' the fruit, a joy.

That's more or less what Shakespeare did 500 years ago. ;)

Out of interest, what's to stop them publishing some 'version' of the modified code, but actually running a different version on their servers? Would that be easy to detect?

Oh! Ha! I did not notice that! I thought something seemed weird though. ;)

He says "Interestingly, Apple has removed the fingerprint reader and its associated dedicated chip", but both models have Touch ID in the keyboard. Top right.

I find it incredible how this article has no mention of Snow Crash, Neal Stephenson, Second Life or Linden Labs.

Very useful info. Thanks!

Hi Jake! (I watch your videos ;)) Many times, the (Angular) ServiceWorker has given us CORS headaches on various requests to our APIs and AWS storage files. The only method we've found, after various AWS configs and ngsw-config.json attempts, was to add `ngsw-bypass=true` to all requests. I'll see if I can find the Github issue, where this has come up before.

Incidentally, while you're here, I'm planning on building something which will require use of SharedArrayBuffer. Will adding the (now) required Cross-Origin isolation COOP/COEP headers cause any issues to existing CORS setups?

:)

ServiceWorkers also don't play nice with CORS in my experience. We often need to bypass them in Angular when making certain requests.

You can catch the 'invalidity' of the input with the `oninvalid` JS event, then use that to `e.preventDefault()` and show a message as to why it it failed.

Here's the guy who wrote the original Windows Task Manager explaining this hack : https://www.youtube.com/watch?v=oKQ1X_4JCn0

Doesn't the HTML input `pattern` attribute help solve this with a RegEx?

Here too. Just had the "We're having some trouble serving your request. Sorry!" error.

Indeed. People seem to forget that when Facebook goes down, it's not just your feed of depressing posts, photos and messages that go away, but also the entire Oculus VR platform, since they demanded a FB account to use Quest headsets.