In reply to @pointoffailure:monero.social
If I host a 1TB file(contract state) will freenet try to download the whole terabyte on disks of all unfortunate users who "discovered"(clicked on the link) my contract?

While we don't currently have a hard limit I'd recommend against having contract state larger than 10 megabytes, a large file would need to be broken up.

However like I said Freenet isn't optimized for distribution of large files, other Freenet peers will treat it as antisocial behavior and will disconnect from your peer.

In short, Freenet isn't well suited to the BitTorrent usecase, think of it more as a distributed computer rather than a content distribution network.

In reply to @philientaylor:gitter.im
This is cool to learn about. I have some static files I thought about sharing over Hyphanet because they were in the size of GB. Does that mean I could similarly use Freenet instead to share these large files as part of the latest state of the contract? I'm hoping that, as I'm trying to only manage the deltas of these big files, the contracts might similarly space-manage? Since you're speaking only about web apps, I'm thinking I'll still benefit from Hypha to share the versions of these large files, ideally with distribution to match demand as designed, even if I'd use Freenet to receive the state and access the download of assets via the Hyphanet.

In theory there is no limit to the size of files that can be shared over Freenet however it really isn't optimized for large files so I wouldn't recommend it.

There are some features on our roadmap that will make it a bit better at handling large contract states but even then I want to discourage people from using it like BitTorrent as that's not what it's designed for.

In reply to @quilnux:fulltermprivacy.com
You do realize though, humans will be humans and "not recommended" != "won't". You'll have people that will host large files whether you want them to or not. Humans abuse things.

In reply to @pointoffailure:monero.social
I was just wondering whether big files can cause a partial DDOS of the network and if it's possible to fill up user drives with junk this way or not. So currently downloads are terminated if they take too long, yes?

In reply to @pointoffailure:monero.social
Or even simpler: a hidden cryptominer in the contract code which essentially runs on a huge distributed computer. Horrific! I was going to sleep but I can't, I'm dreaming of attack vectors :)

In reply to @pointoffailure:monero.social
Or even simpler: a hidden cryptominer in the contract code which essentially runs on a huge distributed computer. Horrific! I was going to sleep but I can't, I'm dreaming of attack vectors :)

In reply to @gogo2464:matrix.org
He probably means to serve other programming languages thab rust or typescript...

That's not what I mean, I'm just asking about serving static assets without needing to compile it into WASM. Ideally, I could push the data straight into the DHT, literally a JPEG or JavaScript file like in Hyphanet, and then retrieve the asset unchanged.

It's common to have two-tiered applications like this. Most web frameworks let you attach a static directory that just serves the files, you don't need to manually write a handler for each one. In AWS you'd use S3 for static assets and lambda for contracts.

In reply to@nsotelo:matrix.org

That's not what I mean, I'm just asking about serving static assets without needing to compile it into WASM. Ideally, I could push the data straight into the DHT, literally a JPEG or JavaScript file like in Hyphanet, and then retrieve the asset unchanged.

It's common to have two-tiered applications like this. Most web frameworks let you attach a static directory that just serves the files, you don't need to manually write a handler for each one. In AWS you'd use S3 for static assets and lambda for contracts.

1. e. apart from volume, that's just a matter of tooling sitting on top of the platform. If someone implements it, there you are

1. e. apart from volume, that's just a matter of tooling sitting on top of the platform. If someone implements it, there you are. The platform itself offers enough flexibility to support the use case

In reply to @elvecent_not:matrix.org
There could be a default contract to be reused whenever you just need to distribute a small volume of static assets. Could also be some kind of tool to incorporate it, with a simple interface where you just specify a file path and hit "publish". But larger files are gonna need to be offloaded to IPFS or whatever else. At least that's what I understood

Definitely can be done but it's extra tooling to manage, extra resource to compile and extract it from the contract at runtime. Hyphanet already solves this problem, you just upload a dumb blob of bits and retrieve it with the key.

Maybe it's too difficult to store blobs alongside contracts and delegates in the "backend". But at surface value looks like this is supported.

To be clear I'm not talking about large files, rather things like CSS, icons, fonts, scripts, etc that usually don't go beyond a few MB.

In reply to@nsotelo:matrix.org
Definitely can be done but it's extra tooling to manage, extra resource to compile and extract it from the contract at runtime. Hyphanet already solves this problem, you just upload a dumb blob of bits and retrieve it with the key.
Maybe it's too difficult to store blobs alongside contracts and delegates in the "backend". But at surface value looks like this is feasible and supported by the architecture.
To be clear I'm not talking about large files, rather things like CSS, icons, fonts, scripts, etc that usually don't go beyond a few MB.

In reply to @nsotelo:matrix.org

That's not what I mean, I'm just asking about serving static assets without needing to compile it into WASM. Ideally, I could push the data straight into the DHT, literally a JPEG or JavaScript file like in Hyphanet, and then retrieve the asset unchanged.

It's common to have two-tiered applications like this. Most web frameworks let you attach a static directory that just serves the files, you don't need to manually write a handler for each one. In AWS you'd use S3 for static assets and lambda for contracts.

You won't need to compile static assets into WASM, the wasm is the contract or "key", the data is the "value". You can also reconfigure contracts without recompiling them because each contract has a block of bytes containing its configuration parameters that can be changed without recompilation.

So a contract that, for example, distributed data that must be signed with a specific signing key could be reused by anyone without recompilation, they just need to change the signing key which would be provided in the contract's parameters.

In reply to @quilnux:fulltermprivacy.com
From a user perspective, how would they get the key to retrieve the data? Is there a search engine that can be used or does the user have to magically find out what they key is, and then remember it to get to it later?