Giggle: The decentralized video stream platform

TBL
1

Basic Information

Project Name: Giggle
Project Track: consumer-social
Team Name: Geeks
Team Members: 2 (@arman, @elluminazk)

Social Info

Telegram: @Arman @elluminazk
Website: TBA

Project Overview

Project Goal:

Giggle aims to be the Netflix of the Decentralized Web, offering a peer-driven video streaming platform built entirely on BTFS. Videos are uploaded, chunked, and streamed using BTFS-native distribution. No centralized servers, no hidden intermediaries — just pure content, owned and distributed by users.

Unique Value Proposition:

WE ARE OPEN TO SUGGESTIONS, please your valuable response.

Giggle’s innovation is to take any of the one Scenario, which would you prefer to exist.

  • Scenario 1 – Standalone Web2-style DApp: Uses Renthub’s BTFS infrastructure to serve as a public frontend. Easily accessible to anyone without BTFS-node setup.
  • Scenario 2 – Zap-Integrated App: Embeds Giggle directly into the ZAP browser, providing an ultra-secure environment with deep BTFS integration. Content is non-trivially accessible, defeating standard Web2-style scraping/downloading.
  • Scenario 3 – Lightweight Cross-platform App: A bundled desktop/mobile app (~60–100MB) with embedded BTFS node running in viewer-only mode, allowing streaming without setup, but retaining content security.
0 voters

Each path has its unique reach and performance profile, offering adaptability as the ecosystem (especially ZAP) evolves.

We would love to hear your responce before we move any forward.

2 Likes
2

I voted for scenario three, I think you should start off with that as your core product.

1 Like
3

Thanks for your input, would love if you could tag your peers in to cast their vote!!
again thanks you🙏

1 Like
4

gm @elluminaZK
got my vote on 3.
reason… i feel it something users( with desktop/mobile) can easily make use.

i dont really know how case 1 and 2 could be complex.

1 Like
5

The reason the scenario 1 and 2 are less reliable as:
for scenario 1 a robust Archi would totally work but relaying on a bowser where the Cid are exposed makes the platform not the only source to view videos, like the we can easily download the video. jus by the aws s3 manifest file.

in case 2 it does work but it prolongs the release of the zap, well the zap utilizes cross language communication. well is challenging to stream data over them, where as for a delegated cross-platform system (scenario 3) which would be natively written in go, damm well easy to integrate and along side is a closed environment, with high cohesion between the btfs and the framework itself.

6

Ok, here’s a few of the best to do it in the forum: @Prince-Onscolo @Nweke-nature1.com @Relate101 @Lumison @ines_valerie @fabsltsa @HODL etc
(I didn’t miss out on any tag intentionally, so apologies if I missed some names.)

6 Likes
7

Thanks for tag @manfred_jr !

2 Likes
8

I think scenario 1 is good that way use your existing service Renthub.
Team geeks with 2 members have submitted now 3 projects under Frontlabs. I have concern that all three projects submitted by your team seem big ambitious projects to me. How a team of 2 members will manage all three plus codehive and renthub simultaneously? Also what is the reason to make 4 different posts when you could have submitted your whole ecosystem under one?

2 Likes
9

Thank you for the tagging

2 Likes
10

I choose the option 3 and I will say all of the 3 options are cool ones why you don’t want to join all of them as 1 project, it will be better for you that way, thank you

2 Likes
11

Welcome to TBL , thanks @manfred_jr for Calling my attention, i will still proofread to cast my vote :ballot_box_with_ballot: but before then what really inspired the name giggle? Hope you are aware that CZ of binance is building Giggle academy, i don’t know how it feels for taking the same name

1 Like
12

hi @HODL, thanks for your suggestion. Yes, all three projects are big and ambitiouss, so they will take time to build. We have three more developers working on these projects. Regarding your question about the four different posts, these are separate posts explaining each project in depth to make it easier for the community to evaluate and have a discusstion on the projet , rather than dumping everything in one Frontlabs ecosystem project post. However, we are also open to posting each project’s details under the Frontlabs ecosystem post if that is preferredd.

1 Like
13

Well that’s great, but each scenario required a totally different development process.

and honestly we can do all of them, but the development won’t start before 3 months. or Q4
And the poll will be open till then. So a throught discussion is apperciable.

1 Like
14

I too am hearing about Binance form you. Honestly its a mere coincident, as the name was totally inspired from the BiliBili an chinese platform, which giveds off a fun vibe, so similar to that, we decided on Giggle.
It has no relation with Binance what so ever and it is jus a meri-coincidence that the name turns out to be same.

1 Like
15

Okay it is good to know that there are three more developers working on these projects.

Yeah this makes sense. I am looking forward to development of these projects. Waiting to know more about your development timeline. I will check the other two projects soon. Good luck team !

1 Like
16

Okay good to know all the best👍

1 Like
17

I would go for the scenario 3, specially as it describes a well known process, just using an app for quick deployment and that is it.

1 Like
18

3 month is plenty time to make all right decision, I wish you all the best

1 Like
19

Thank you for the tag. But the thing is I don’t really understand the project. But I will try my best to read again to my understanding. Thank you