Avatar
Richi
6d0c4eec4c38427bab81bfef29997204dd0654ab3614ce90ee3e9839c0a47008
Passionate about Self-Improvement & Freedom-Tech

nostr:nprofile1qyghwumn8ghj7mn0wd68ytnvv9hxgtcqypex583xrnryw3n5aq59uw23kwa38xlf5aeart85nhyx3kuxrgwpzjh056v Just curious, what is the difference between nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qpq0r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7s85uvay and https://accrescent.app/ ?

You have wonderfully explained the differences between the various app stores in this post. nostr:nevent1qvzqqqqqqypzq7xwd748yfjrsu5yuerm56fcn9tntmyv04w95etn0e23xrczvvraqqszz6w8ff60gn8rvlrye559jpv3s2eckjxx0qqgy7g0k8c78f98plcs93eac

I already posted this answer elsewhere.

The problem is that we are stuck in the ideation phase. The sooner we launch a website or an app, the more clearly we will identify the challenges that may arise. We just need a proficient developer to organize this matter.

Replying to Avatar Ryan

Decentralized Video Hosting

I used to frequent private torrent trackers. Megabytes was the currency on these sites. The more you uploaded, the more you could download. This ensured torrents would be well seeded and remained available with fast downloads.

Could this be adapted to Nostr with a lightning twist? A market for decentralized video hosting?

Anyone with a VPS or a home server could run a seed box, providing bandwidth and disk space for a fee. Users who require video hosting could buy "upload credit" compensating the seed box operators. In return they get decentralized censorship resistant video hosting.

People viewing content could also be involved. Clients could be able to cache and seed a certain amount of video, just like any torrent client. This would ensure that popular videos would have more sources, ensuring their wide availability as they become more popular. This way anyone can earn sats or "upload credit", just by seeding the videos they have viewed.

I'm not sure if this is realistic or even possible, but it's an idea that always sits in the back of my head.

AI thoughts, including blossom integration:

If Blossom servers act as the initial hosting layer, the workflow could evolve as follows:

* Video Upload and Initial Hosting on Blossom:

* A user uploads a video to a Blossom server. Blossom, being a federated and potentially more censorship-resistant alternative to traditional centralized hosting, provides the initial availability and distribution.

* The video is still likely broken down into chunks for more efficient distribution later.

* The Blossom server generates the content hash and metadata.

* Nostr Announcement with Blossom Location:

* The video uploader announces the video on Nostr, including the content hash and crucially, the initial location(s) on the Blossom network where the video chunks can be obtained.

* The Nostr note would also detail the terms for long-term seeding (sats/MB offered) and potential rewards for viewers who cache and re-seed.

* Initial Viewing and Caching:

* When a user wants to watch the video, their client connects to the specified Blossom server(s) to begin streaming the chunks.

* As they watch, their client can, with their consent, cache portions of the video locally.

* Becoming a Seeder (Post-Blossom):

* The client software, having cached some video chunks, can now advertise itself as a seeder for those specific chunks via Nostr or a separate peer discovery mechanism.

* They would indicate their Lightning address or a mechanism for receiving sats for providing bandwidth.

* Payment and Incentives:

* Other viewers downloading from these client-seeders would initiate micro-payments via Lightning.

* The original uploader's "upload credit" pool (funded with sats) could also be used to incentivize these longer-term seeders, even after the initial demand from the Blossom servers subsides.

Advantages of Starting with Blossom:

* Easier Bootstrapping: Blossom provides a more readily available and user-friendly initial hosting solution compared to relying solely on a completely distributed network from the outset. Uploaders wouldn't need to immediately grapple with setting up their own infrastructure.

* Potentially Faster Initial Speeds: Blossom servers, presumably well-connected, could offer good initial streaming speeds for early viewers.

* Gradual Decentralization: The system can gradually decentralize as more viewers cache and become seeders, reducing reliance on the initial Blossom servers over time.

#asknostr

The problem is we are stuck in the ideation phase. The sooner we launch a web or an app, the more clearly we will identify the challenges that may arise.

We just need a proficient dev to organize that matter.

Can nostr:nprofile1qqsxare7m73ghlyq2ltn2720w6mf008337ufffdr0gfjdyltmgc6geqpzpmhxue69uhk2afwwf38ytnzd9hszynhwden5te0wp6hyurvv4cxzeewv4esf3hzja answer questions in German?

Better = Boring

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ks3f750r Why is Fedora as an OS not supported for either the Web Installer or the CLI Installer? I read somewhere that there is a bug with fastboot on Fedora.

Running #GrapheneOS (finanally)

I like this AI-style. How can I reproduce it?

theoretical question for #askNostr #askaDev:

Where is the limit in the #Nostr protocol? Does the analogy work that the current protocol is similar to Layer-1 in Bitcoin, and therefore a Layer-2-like-solution will be needed in the future.

Why is nobody building a client that is similar to YouTube? Is the infrastructure missing? Is something missing in the protocol?

What is the problem?

#nip #nostr #askNostr #YouTube nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcpz4mhxue69uhkzet8d9ejuat50phjummwv5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5zgwjy3