YRAL Q1 2025 Updates

image

btw it was a good effort to try and hide this by sending nicp in small transfers to make tracking more difficult. Just a waste of a bot burning cycles though. talk about clogging the network for no reason.

Perhaps sharing knowledge would be the most beneficial thing for ICP.

1 Like

oh yeah, it was me, sorry I have a lot on my plate right now

this narrative is not false,

The fact that ICP can host these things on chain (AT ALL) puts them miles ahead of the competition. Is it currently the best user experience for these specific applications? no.

There are fundamental tradeoffs between security, decentralization, and scalability. This is a new software paradigm still in fledgling stage, we are figuring it out through trial and error. People are still working on writing software that scales successfully, but open Chat is a good example of a dapp that does this well already.

1 Like

Why you say 10 seconds? Tagger was using onchain images, and it didn’t last 10 seconds, were immediately loaded

How? You can stream video and images?

You’re probably NOT.

I mean to say this with the utmost amount of respect and NOT meaning to imply that you don’t know what you’re doing

You’re either

  • using the asset canister that Dfinity built for serving web frontends. But this is limited to that use case. It’s not built for video streaming. It’s built for serving web assets, which might include the occassional marketing video or the cool background video behind the wall of text that you see on the background on landing pages
  • built a chunking mechanism where uploaded videos get chunked and stored as binary blobs on canisters. But then you need a LOT of JavaScript on the client side to do the heavy lifting of downloading those binary blobs and assimilating them to form a complete video on the client device and only when the entire video is completely downloaded is it available to play. Which means you’re not REALLY streaming video

The industry accepted standard of streaming video is primarily HLS or DASH compliant streaming. Mostly HLS as Apple devices don’t support DASH

For NFT marketplaces, we would advise the 1st approach. The 2nd approach is overkill and will cause unnecessary delays on the client loading time.

We know because we’ve done similar for NFT marketplaces we’ve helped build

But I’m happy to be proven wrong. When you’re ready to share the marketplace, we’re happy to provide technical feedback if you’re soliciting feedback

2 Likes

Now we just have to work out how their application is connected to the IC

Debatable

We’ll let our results show for themselves

This is UNTRUE

Denied on multiple counts by Dfinity team members, so this is FALSE

Here’s one of them:

Please do. And give us ALL of your BRUTAL feedback. We always value your feedback

We are focused on building an awesome dapp. That’s what we’ll do

Not casting shade but the video calling functionality on OpenChat is built on cloud

Anything that’s text based or lightweight images, the IC can handle really well

Video at scale is something that’s currently a challenge.

It’ll get figured out, but we’re not there yet

1 Like

Video compression could mean a couple of things in this case. I’m going to assume you mean lossy compression for video transmitted over the network. We already do that but there’s always areas of improvement possible

I’m going to assume you mean memory in this case. Sadly this is a bit out of our hands, as this relates to the WASM runtime that is executing our app

Most incumbent competing apps that you referred to are built using JavaScript based frameworks like React or Svelte or the countless others. JavaScript is the predominant language of the web and browsers JS runtimes have been optimised for it for decades.

Compared to that, WASM is EXTREMELY new and it’s consistently getting better. Having said that the browser WASM runtime is still some way away compared to the JS one.

However, we expect this situation to rapidly keep improving and that is what we’re betting the future of our app on.

Similar to how the IC isn’t currently the best at everything but we expect things to rapidly keep improving.

Our app Yral is actually quite a bit of cool tech. If you’re a dev that can read Rust, I’d invite you to take a look at our repos. You’ll find some delightful/unconventional choices we’ve made

We’re trying to do our best to see that this goes through

However, our understanding is that the SNS hasn’t been built with this scenario in mind. Rolling back an SNS atomically hasn’t been done yet and the FuelEV team is seeking Dfinity’s help in doing this. It is in Dfinity’s CAPABLE hands and the FuelEV team will do whatever Dfinity will advise them to do. That’s what I’m currently aware of and am sharing

99% of the funding was HotOrNot ICP, same as Estate DAO. I’m going to campaign that these funds should never be returned to the original scammers.

And yes, you’re overloading subnets on purpose, the chance of it being anything else is miniscule. Exactly 451GiB right?

ā€œOverloadingā€ is questionable.

The PURPOSE is to have headroom for a large successful scalable dapp. We paid for those canisters. We have every right to run them. I don’t see what the problem is.

This is UNTRUE

The evidence posted here shows so

It was a public sale that went through its due diligence via the NNS.

However, owing to overwhelming feedback provided, we, Yral dapp, will course correct and are going to be doing whatever Dfinity and the broader community advises us to do.

We are ALWAYS willing to engage respectfully and HUMBLY listen to feedback

3 Likes
  • It was done before the current treasury restrictions came into being. So, the entire amount could be withdrawn to a single principal and then refunded
  • Currently not possible anymore because a single proposal has limits on how much can be withdrawn so you can’t follow the same mechanism
  • Is inelegant because now you still have a husk of a defunct SNS existing on the SNS subnet without any way to clean up

So, it’s not technically feasible for Fuel EV to do because they can’t withdraw the entire amount and send it back to the original contributors

Happy to be corrected if the above is still feasible. We will ensure to pass on that feedback to the FuelEV team

2 Likes

I agree.

Yes this is what i mean.

1 Like

If your dapp is great why you can’t even onboard 1% of your locals? (Indian)

To be honest you missed the practical utility of your application,but instead rebranding it whenever you like .

When you first launched hot or not I shared it to my friends. But you know what are their comments? Ouch disgusting it’s like a soft porn app.

On the first place since it’s a decentralized app it’s very challenging for content moderation .(maybe you already develop an ai.)

If your app can’t gain traction and can’t generate revenue it will end up dying after 2 years . And you will fade in the shadows leaving sns treasury drained.

If you have plan for onboarding masses and revenue model .I would glad to read and share it.

1 Like

Ok, correct me if I am wrong here but didn’t you close Hot or Not to put your ā€œlaser-like focusā€ on developing YRAL? How are they both live or is this some weird Schrƶdinger’s dapp situation where neither YRAL or Hot or Not are really alive or dead.

Also why aren’t you adding your other ā€˜projects’ to DOLR? You know the literal car crash and the imaginary apartment rental?

You need to stop spouting nonsense and show everyone exactly what you have built and running on the IC and how that benefits the IC ecosystem.

Open user metrics so you can see how many daily downloads, active users that sort of thing would go a significant way to convincing everyone that you aren’t just spouting your normal blast of hot air to try to buy more time so you can workout how to drain more IC from the neurons fund or naive investors.

Ohh actually I see now..

It is your normal blast of hot air to try to fool people that you should be allowed to withdraw yet more money for producing nothing…

4 Likes

That’s one of our objectives. We have a couple of strategies on how to do this.

We are making grassroots progress on this and making inroads. We believe this will take some more time to play out but we are already seeing positive signs.

Here’s one of those ways we plan to:

The core idea of the app has stayed the same with us making constant improvements. The rebrand has been a new skin for marketing to try out some new ideas. Why is a rebrand objectionable?

And we took that very seriously. We worked on it and solved it at scale by training our own AI models that perform this at scale. Please give it a try again and give us your valuable feedback.
You’ll find your friends will have a different take on it this time. The NSFW content is now safely gated behind a NSFW toggle and only shows up if you voluntarily turn it on.

It’s reliable to the point that we’ve managed to list on the Apple App Store by passing Apple’s stringent app store policies around objectionable content on social apps

I believe we are probably the ONLY SNS project at this time who is listed on the Apple App Store. Please pardon my ignorance if I’m wrong and another project is also available. Happy to be corrected.

You can find it here:

We do have. My colleague Utkarsh covered it here:

1 Like