Post audio data to an API

[shailendramaurya]

It would be cool to display what one is listening on ytify.......

Implementing a feature that posts audio data or just the youtube I'd to an API specified by the user would be great !!!!!!

[n-ce]

Rough Sketch
So first things first. This definitely requires a backend server.
Our ytify client here would send a POST request to this server with the { id , streamLength, currentTime } everytime the user undergoes audio event changes.
So when you access the backend api it would return your current listening stream data.
It seems we need an API key to sync the sender and the receiver, which can be accessed post authentication on the backend.

[shailendramaurya]

So, are you planning to provide backend along with ytify, or let the user selfhost it? As both will require different approach.
The original idea was to provide some input fields in ytify settings which includes:

1. An API URL, audio data will be posted to it.
2. Just another input field, for custom JSON data to be sent along with audio data for authentication purpose.
   Then just provide the backend script and let the user selfhost it.

For providing backend along with ytify, just remove the inputs from settings UI and host own backend.

But there may be an intresting approach, as ytify has been migrated to nodejs....... It may expose a public path /api, which will function as (long texts typed and erased here), but there may be a problem with storage of data or auth I guess 🤔

[n-ce]

So, are you planning to provide backend along with ytify, or let the user selfhost it?

I thing hosting it on a separate backend is a better idea as these are separate 'value added services' which are not necessary for the full ytify experience.

The original idea was to provide some input fields in ytify settings which includes:
An API URL, audio data will be posted to it.

Yes this was my intention as well. Just like right now ytify uses some piped instance but also allows adding custom.

[shailendramaurya]

Great, I can provide the backend server, but the only challenge lies with the domain name.

[shailendramaurya]

Have a look at Deta Space it provides a variety of script choices including python, rust and node, Also a drive, database for data storage and a dummy domain for public interface........ Almost perfect for this use case. Deta Docs
But I've not tested their speeds which may be concerning for real-time APIs.

[n-ce]

I've used deta.sh before, the speeds were fine for an API. Although the CLI for everything was really cumbersome to work with. I don't know how things have changed since deta.space but it looks a lot bloated with space os and stuff.