Maybe #PurpleStack can get updated to do this in the future. "Convert https://example.com into an apk" or something like that.

YakiHonne does not show content warnings, so be careful!

... but Chrome is still needed to be installed so these apps won't work with Android TV. But I especislly want VidStr to work on Android TV.

How did you do this? I know that when I add PWA functionality, I can install these pages like apps. On Android, Chrome even makes them APKs.

*to YouTube videos ...

This doesn't work. You can't link tobYouTube videos in NIP-71 video events!

Seriously? (Look at the video url)

Do you mean these kind 30005 lists? Would they still work with kind 34235? And can entries in this list be reordered? That new music custom NIPs also define their own plsylist format.

Ok, this is great. My VidStr supportd 3 variations of NIP-71, two of them archived as custom NIPs. Now there is one thing I need to think about... playlists. Video clients need playlists. Only then can they become a potential full replacement of YouTube.

Is this NIP-71 support just kind 21/22? Or did they add support for the old kind 34235/34236 as well?

This happens now when installing an app in Zapstore Alpha.

Former german constitutional judge Voßkuhle wants mandatory use of real names on social media. This won't be possible with #Nostr, thankfully. https://www.tagesschau.de/inland/innenpolitik/vosskuhle-demokratie-100.html

This comes in a moment where my phone's battery is broken. Nice.

This in red is the error that happens when trying to push changes now.

The thing is, normally when pushing a repo to ngit for the first time, this error doesn't happen, and I can push code changes afterwards as long as I don't click on "Save" next to the remote url field.

It worked for a time, but then it was struggling again.

I just created this prompt for a PWA smarthome/IoT dashboard. I want to use this with Opus. If there's anything I missed, please let mw know, _____ Create a dashboard app for smarthome and IoT. It is very important that this is a PWA that can run offline. I want it to be able to connect to devices in a local network, but also online. The dashboard should support HTTP requests (all methods), WebSocket and MQTT, including support for multiple MQTT brokers or WebSocket servers. Optionally, you can add support for the Constrained Application Protocol (CoAP). The user should be able to create as many dashboards as he wants. The dashboards can use a JSON-based file format. Make sure the JSON is well formatted so that it can be read by humans using any text editor. Dashboards can be saved as a file and loaded from a file. A dashboard can contain the following elements: - text display that shows output - text fields for data to send to a server or broker - checkboxes with multiple choices - radio buttons with one out of multiple choices - buttons with one action - switches with 2 actions - non-binary switches with 3 or more actions - image and video feed display for webcams - variables and other things that enable elemwnts to take data from other elements Server and broker URLs can be defined either per dashboard or per element. Maybe also a mix of both. Optionally, you could implement some premade templates, including one for Tasmota devices. But please also let the user create a dashboard from scratch. For future expansions, add Nostr login, just in case a custom or official NIP for smarthome or IoT should ever emerge. _____

Do they know about nostrhub.io for custom NIPs?

Shakespeare told me the limitations of this demo, as it says, as well. Should I try these things?

Like I said to Vitor, I quickly asked Shakespeare: https://relay-deployer.shakespeare.wtf/

I quickly asked #Shakespeare about this. https://relay-deployer.shakespeare.wtf/ Would you mind taking a look? But Shskespeare stated also that this is more like a demo.

Have you taken down the update and reverted to the old version?

I would prefer to keep 0.2.7 in parallel even after the 1.0 release. Just in case.

New problems emerge...