Forest @forestjohnson@pixie.town

@astrid why 🤮 for homebrew? Im asking from a position of ignorance lol

@TomF

the omniscient nutrition provider aggregator

(https://video.strongthany.cc/watch?v=y8OnoxKotPQ)

@filippo

AP/mastodon is so bizzare because its populated by ppl who really DONT want publishing, preferring privacy+control+community-ownership over discoverability.

But PUB is literally in the name!!!! And its in the design, too; it feels like there's a big effort to shoe horn essentially e2ee group chat into something that was absolutely never intended to be used that way.

IMO it might eventually come time to start over w/ a new protocol more like SSB. Separate the server convenience service from the data ownership and authentication.

I think bitcoin wallet ui (electrum) has a lot to teach us about how to make e2ee live up to its security hype without falling into the same usability black hole of gpg

And that doesn't mean everyone *has* to have that level of control/responsibility. Just that its always an option. Can still have a server that owns your privatekey and has "forgot my password".

Demo Day at layer zero is starting soon! just streaming some dashcam footage right now while we wait

https://stream.layerze.ro/

Also, it goes without saying, but its ridiculous that if I want this capability, the only way to get it is to bootleg it like this.

Google finally achieved a technology that can transcribe spoken conversation, but they want to hoard it behind proprietary APIs and services. This bootleg is a small glimpse at what technology could be like if its goal was to provide utility instead of just make money: Accessibility technology that actually works!

Ok, ok, maybe that's a bit of a grandiose claim for something like this which is just barely demo-able and still has tons of difficult fundamental problems to overcome... But the point is, this capability would probably be commonplace already if it was open technology. The only reason this is remarkable is because I went through the effort to hack it together with DACs on both sides, special audio cables, android UI testing libraries, and heaps of good old-fashioned software duct-tape. And despite all that, it still out-performs the "Open" state of the art like "OpenAI" Whisper, while using 1/10th of the energy.

Also, here is the massive alt-text I wrote for the video :P A thorough description of wtf is going on in this video:

video of multi-user audio transcription system based on Pixel 6 phone with a neural network chip that enables the Google Live Transcribe app to convert audio into text without the ability to reach the internet.

The Pixel 6 is connected to a combo charger + microphone adapter. The Linux server has a sound card with its output connected to the microphone adapter's input, mediated by a special attenuator audio cable.

The linux server is running a web application that connects to a mumble server, enqueues audio from a conversation, and plays it back one-speaker-at-a-time.

The linux server is also attached to the android phone via ADB. The linux server join's the android phone's WiFi Hotspot. The linux server is running a "uiautomator" UI test which constantly polls the transcribed text element of the Google Live Transcribe app and posts the text to the server via WiFi.

The web application synthesizes the data of who was talking when, and what text was displayed when, in order to display the live conversation on a web-page, similar to a chat log.

These are the repos involved:
https://git.sequentialread.com/forest/mixtape-mumble
https://git.sequentialread.com/forest/mixtape/src/branch/main/mixtape.uiautomator

Here's a link to the video on my server: https://picopublish.sequentialread.com/files/mixtape-demo5.mp4

its kinda hard to hear @fack, I had my phone sitting on my headphones while recording this and it didn't work out too well

About 5 watts at the wall. A purely self-hosted live transcription of a Mumble audio chat. Transcription annotated by the speaker's name.

A friend recommended yt-dlp ( a fork ) and it worked!