Can't upload images
M
M
M
M
An unexpected error occurred. Please try again later.
M
If a girl likes you she will assume that every woman likes you. If a girl doesn't like you she assumes that no woman will like you either.
Based
Master fix your fucking forum you retarded nigger. You spend your entire time on looksmax then use the .is Twitter account post retarded shit for clout
M
I got banned for making a troll post. It was a make believe post. I had to convince myself I'm a slayer so that I could be confident enough because I had exams at that period. I needed to hang on to something.
Public buckets
Public Bucket is a feature that allows users to expose the contents of their R2 buckets directly to the Internet. By default, buckets are never publicly accessible and will always require explicit user permission to enable.
Public buckets can be set up in either one of two ways:
Expose your bucket as a custom domain under your control.
Expose your bucket using a Cloudflare-managed https://r2.dev subdomain for non-production use cases.
These options can be used independently. Enabling custom domains does not require enabling r2.dev access.
To use features like WAF custom rules, caching, access controls, or bot management, you must configure your bucket behind a custom domain. These capabilities are not available when using the r2.dev development url.
Note
Currently, public buckets do not let you list the bucket contents at the root of your (sub) domain.
Custom domains
Caching
Domain access through a custom domain allows you to use Cloudflare Cache to accelerate access to your R2 bucket.
Configure your cache to use Smart Tiered Cache to have a single upper tier data center next to your R2 bucket.
Note
By default, only certain file types are cached. To cache all files in your bucket, you must set a Cache Everything page rule.
For more information on default Cache behavior and how to customize it, refer to Default Cache Behavior
Access control
To restrict access to your custom domain's bucket, use Cloudflare's existing security products.
Cloudflare Zero Trust Access: Protects buckets that should only be accessible by your teammates. Refer to Protect an R2 Bucket with Cloudflare Access tutorial for more information.
Cloudflare WAF Token Authentication: Restricts access to documents, files, and media to selected users by providing them with an access token.
Warning
Disable public access to your r2.dev subdomain when using products like WAF or Cloudflare Access. If you do not disable public access, your bucket will remain publicly available through your r2.dev subdomain.
Minimum TLS Version
To specify the minimum TLS version of a custom hostname of an R2 bucket, you can issue an API call to edit R2 custom domain settings.
Add your domain to Cloudflare
The domain being used must have been added as a zone in the same account as the R2 bucket.
If your domain is already managed by Cloudflare, you can proceed to Connect a bucket to a custom domain.
If your domain is not managed by Cloudflare, you need to set it up using a partial (CNAME) setup to add it to your account.
Once the domain exists in your Cloudflare account (regardless of setup type), you can link it to your bucket.
Connect a bucket to a custom domain
Go to R2 and select your bucket.
On the bucket page, select Settings.
Under Custom Domains, select Add.
Enter the domain name you want to connect to and select Continue.
Review the new record that will be added to the DNS table and select Connect Domain.
Your domain is now connected. The status takes a few minutes to change from Initializing to Active, and you may need to refresh to review the status update. If the status has not changed, select the ... next to your bucket and select Retry connection.
To view the added DNS record, select ... next to the connected domain and select Manage DNS.
Note
If the zone is on an Enterprise plan, make sure that you release the zone hold before adding the custom domain.
A zone hold would prevent the custom subdomain from activating.
Disable domain access
Disabling a domain will turn off public access to your bucket through that domain. Access through other domains or the managed r2.dev subdomain are unaffected. The specified domain will also remain connected to R2 until you remove it or delete the bucket.
To disable a domain:
In R2, select the bucket you want to modify.
On the bucket page, Select Settings, go to Custom Domains.
Next to the domain you want to disable, select ... and Disable domain.
The badge under Access to Bucket will update to Not allowed.
Remove domain
Removing a custom domain will disconnect it from your bucket and delete its configuration from the dashboard. Your bucket will remain publicly accessible through any other enabled access method, but the domain will no longer appear in the connected domains list.
To remove a domain:
In R2, select the bucket you want to modify.
On the bucket page, Select Settings, go to Custom Domains.
Next to the domain you want to disable, select ... and Remove domain.
Select ‘Remove domain’ in the confirmation window. This step also removes the CNAME record pointing to the domain. You can always add the domain again.
Public development URL
Expose the contents of this R2 bucket to the internet through a Cloudflare-managed r2.dev subdomain. This endpoint is intended for non-production traffic.
Note
Public access through r2.dev subdomains are rate limited and should only be used for development purposes.
To enable access management, Cache and bot management features, you must set up a custom domain when enabling public access to your bucket.
Avoid creating a CNAME record pointing to the r2.dev subdomain. This is an unsupported access path, and we cannot guarantee consistent reliability or performance. For production use, add your domain to Cloudflare instead.
Enable public development url
When you enable public development URL access for your bucket, its contents become available on the internet through a Cloudflare-managed r2.dev subdomain.
To enable access through r2.dev for your buckets:
In R2, select the bucket you want to modify.
On the bucket page, select Settings.
Under Public Development URL, select Enable.
In Allow Public Access?, confirm your choice by typing ‘allow’ to confirm and select Allow.
You can now access the bucket and its objects using the Public Bucket URL.
To verify that your bucket is publicly accessible, check that Public URL Access shows Allowed in you bucket settings.
Disable public development url
Disabling public development URL access removes your bucket’s exposure through the r2.dev subdomain. The bucket and its objects will no longer be accessible via the Public Bucket URL.
If you have connected other domains, the bucket will remain accessible for those domains.
To disable public access for your bucket:
In R2, select the bucket you want to modify.
On the bucket page, select Settings.
Under Public Development URL, select Disable.
In Disallow Public Access?, type ‘disallow’ to confirm and select Disallow.
Public Bucket is a feature that allows users to expose the contents of their R2 buckets directly to the Internet. By default, buckets are never publicly accessible and will always require explicit user permission to enable.
Public buckets can be set up in either one of two ways:
Expose your bucket as a custom domain under your control.
Expose your bucket using a Cloudflare-managed https://r2.dev subdomain for non-production use cases.
These options can be used independently. Enabling custom domains does not require enabling r2.dev access.
To use features like WAF custom rules, caching, access controls, or bot management, you must configure your bucket behind a custom domain. These capabilities are not available when using the r2.dev development url.
Note
Currently, public buckets do not let you list the bucket contents at the root of your (sub) domain.
Custom domains
Caching
Domain access through a custom domain allows you to use Cloudflare Cache to accelerate access to your R2 bucket.
Configure your cache to use Smart Tiered Cache to have a single upper tier data center next to your R2 bucket.
Note
By default, only certain file types are cached. To cache all files in your bucket, you must set a Cache Everything page rule.
For more information on default Cache behavior and how to customize it, refer to Default Cache Behavior
Access control
To restrict access to your custom domain's bucket, use Cloudflare's existing security products.
Cloudflare Zero Trust Access: Protects buckets that should only be accessible by your teammates. Refer to Protect an R2 Bucket with Cloudflare Access tutorial for more information.
Cloudflare WAF Token Authentication: Restricts access to documents, files, and media to selected users by providing them with an access token.
Warning
Disable public access to your r2.dev subdomain when using products like WAF or Cloudflare Access. If you do not disable public access, your bucket will remain publicly available through your r2.dev subdomain.
Minimum TLS Version
To specify the minimum TLS version of a custom hostname of an R2 bucket, you can issue an API call to edit R2 custom domain settings.
Add your domain to Cloudflare
The domain being used must have been added as a zone in the same account as the R2 bucket.
If your domain is already managed by Cloudflare, you can proceed to Connect a bucket to a custom domain.
If your domain is not managed by Cloudflare, you need to set it up using a partial (CNAME) setup to add it to your account.
Once the domain exists in your Cloudflare account (regardless of setup type), you can link it to your bucket.
Connect a bucket to a custom domain
Go to R2 and select your bucket.
On the bucket page, select Settings.
Under Custom Domains, select Add.
Enter the domain name you want to connect to and select Continue.
Review the new record that will be added to the DNS table and select Connect Domain.
Your domain is now connected. The status takes a few minutes to change from Initializing to Active, and you may need to refresh to review the status update. If the status has not changed, select the ... next to your bucket and select Retry connection.
To view the added DNS record, select ... next to the connected domain and select Manage DNS.
Note
If the zone is on an Enterprise plan, make sure that you release the zone hold before adding the custom domain.
A zone hold would prevent the custom subdomain from activating.
Disable domain access
Disabling a domain will turn off public access to your bucket through that domain. Access through other domains or the managed r2.dev subdomain are unaffected. The specified domain will also remain connected to R2 until you remove it or delete the bucket.
To disable a domain:
In R2, select the bucket you want to modify.
On the bucket page, Select Settings, go to Custom Domains.
Next to the domain you want to disable, select ... and Disable domain.
The badge under Access to Bucket will update to Not allowed.
Remove domain
Removing a custom domain will disconnect it from your bucket and delete its configuration from the dashboard. Your bucket will remain publicly accessible through any other enabled access method, but the domain will no longer appear in the connected domains list.
To remove a domain:
In R2, select the bucket you want to modify.
On the bucket page, Select Settings, go to Custom Domains.
Next to the domain you want to disable, select ... and Remove domain.
Select ‘Remove domain’ in the confirmation window. This step also removes the CNAME record pointing to the domain. You can always add the domain again.
Public development URL
Expose the contents of this R2 bucket to the internet through a Cloudflare-managed r2.dev subdomain. This endpoint is intended for non-production traffic.
Note
Public access through r2.dev subdomains are rate limited and should only be used for development purposes.
To enable access management, Cache and bot management features, you must set up a custom domain when enabling public access to your bucket.
Avoid creating a CNAME record pointing to the r2.dev subdomain. This is an unsupported access path, and we cannot guarantee consistent reliability or performance. For production use, add your domain to Cloudflare instead.
Enable public development url
When you enable public development URL access for your bucket, its contents become available on the internet through a Cloudflare-managed r2.dev subdomain.
To enable access through r2.dev for your buckets:
In R2, select the bucket you want to modify.
On the bucket page, select Settings.
Under Public Development URL, select Enable.
In Allow Public Access?, confirm your choice by typing ‘allow’ to confirm and select Allow.
You can now access the bucket and its objects using the Public Bucket URL.
To verify that your bucket is publicly accessible, check that Public URL Access shows Allowed in you bucket settings.
Disable public development url
Disabling public development URL access removes your bucket’s exposure through the r2.dev subdomain. The bucket and its objects will no longer be accessible via the Public Bucket URL.
If you have connected other domains, the bucket will remain accessible for those domains.
To disable public access for your bucket:
In R2, select the bucket you want to modify.
On the bucket page, select Settings.
Under Public Development URL, select Disable.
In Disallow Public Access?, type ‘disallow’ to confirm and select Disallow.
Same prolly a 4shit or the Sharty LOL
M
The Stanley Parable.
Happening to me too
What do you mean
doubt it
M
Stanley felt the bucket calling to him, begging him to pick it up.
Why was he not doing it?
Why was he not doing it?
M
Maybe Stanley would never pick up the bucket.
A lonely bucket; lonely and miserable, and Stanley-less.
Such a sad fate for a bucket.
A lonely bucket; lonely and miserable, and Stanley-less.
Such a sad fate for a bucket.
Gray-san no one gives a fuck about this forum. It’s just hosted like shit and is down all the time
M
Stanley, pick up the bucket.
M
Stanley picked up the bucket.
Stanley lifted the bucket into his arms, and a wave of comfort rushed over him.
The confusion and the chaos all seemed to melt away as Stanley embraced the bucket.
Warmth spread through Stanley's arms. With the bucket in his arms again, he was home.
Stanley picked up the bucket and smiled. He'd never be alone again. Not truly alone. Not with the bucket around.
The good ol' bucket. Just Stanley and the bucket, off on another thrilling adventure together.
The bucket made Stanley want to be a better man, and a better co-worker. In time, perhaps he would become both of those things.
Ahh, Stanley's bucket. The only coworker he would ever truly need.
As Stanley lifted his bucket, he felt a connection to all buckets everywhere. This adventure, he decided, was for all of them.
A good bucket. A strong bucket. A humble bucket. A committed bucket. A bucket of culture and distinction.
Ah, the embrace of an old friend. A weathered companionship that stands the test of time.
Is Stanley without the bucket really Stanley at all? No, no surely not.
One man. One bucket. One chance to seize their destiny, together.
Finally, yes. The bucket! Yes, yes, yes! I love that bucket.
''Where are we going today?'' the bucket asked. Stanley just smiled. Anywhere they went together would be perfectly fine with him.
Stanley cradled the bucket in a gentle embrace. Protective yet delicate, assertive yet compassionate.
It's bucket time! (After all the other dialogue has been heard, this will be heard for all times in the future when the Bucket is picked up.)
Stanley lifted the bucket into his arms, and a wave of comfort rushed over him.
The confusion and the chaos all seemed to melt away as Stanley embraced the bucket.
Warmth spread through Stanley's arms. With the bucket in his arms again, he was home.
Stanley picked up the bucket and smiled. He'd never be alone again. Not truly alone. Not with the bucket around.
The good ol' bucket. Just Stanley and the bucket, off on another thrilling adventure together.
The bucket made Stanley want to be a better man, and a better co-worker. In time, perhaps he would become both of those things.
Ahh, Stanley's bucket. The only coworker he would ever truly need.
As Stanley lifted his bucket, he felt a connection to all buckets everywhere. This adventure, he decided, was for all of them.
A good bucket. A strong bucket. A humble bucket. A committed bucket. A bucket of culture and distinction.
Ah, the embrace of an old friend. A weathered companionship that stands the test of time.
Is Stanley without the bucket really Stanley at all? No, no surely not.
One man. One bucket. One chance to seize their destiny, together.
Finally, yes. The bucket! Yes, yes, yes! I love that bucket.
''Where are we going today?'' the bucket asked. Stanley just smiled. Anywhere they went together would be perfectly fine with him.
Stanley cradled the bucket in a gentle embrace. Protective yet delicate, assertive yet compassionate.
It's bucket time! (After all the other dialogue has been heard, this will be heard for all times in the future when the Bucket is picked up.)
M
Error 403
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
M
Nothing responded to the bucket's touch, but it did little to discourage Stanley's belief in the magic of the bucket.
brutal falling apart pill
Soys are tryna t8 is down
M
As soon as Stanley noticed that the door to his office was still open
he rushed in with his bucket and shut the door.
The pressure of going out and finding another bucket variant on one of The Stanley Parable's classic endings
was simply too much for him.
“It's nothing but swapped out dialogue describing a bucket!” he screamed to himself.
“It's not nearly different enough to be considered a sequel!”
No. He would stay right here in his office where things were safe. Familiar.
If others were happy with the bucket endings... well, good for them.
But Stanley knew that one day, somehow, a true sequel would emerge with actual new content.
If only he had waited long enough.
Just a little longer, Stanley. Keep waiting, you'll get it one day, surely. Eventually.
Just keep waiting. Just a little longer now.
he rushed in with his bucket and shut the door.
The pressure of going out and finding another bucket variant on one of The Stanley Parable's classic endings
was simply too much for him.
“It's nothing but swapped out dialogue describing a bucket!” he screamed to himself.
“It's not nearly different enough to be considered a sequel!”
No. He would stay right here in his office where things were safe. Familiar.
If others were happy with the bucket endings... well, good for them.
But Stanley knew that one day, somehow, a true sequel would emerge with actual new content.
If only he had waited long enough.
Just a little longer, Stanley. Keep waiting, you'll get it one day, surely. Eventually.
Just keep waiting. Just a little longer now.
M
Error 403
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
W
this is suspicious since all other forums are fine
M
"Yes," whispered the bucket into Stanley's ear.
"We've done it. We've escaped from that dull office and that pesky narrator. At last, out here in the white void, we are alone. Now, and for the first time, I can reveal to you my true self."
The bucket began to tell Stanley of its life and its history.
Of the countless wars it witnessed desecrating the land and lives of untold numbers of innocent humans and the bucket's own complicity therein.
Of sadness and regret and the many years it spent dwelling on the actions it might have taken to curb the madness and the decay.
If only it had been stronger.
Of hope and redemption and its crusade to uplift the stock of life for the common man. To manifest justice where none existed.
And the bittersweet reality of time, to see one's dreams and wishes met halfway.
Meted out in parcels like charity and abandoned as soon as the warm glow of inspiration begins to dim.
The opportunities to do so much more.
There was so much it could have done.
"Perhaps..." The bucket wondered to itself.
Perhaps if it had seen its own darkness with a clearer perception... This was way too much for Stanley.
"What are you talking about?!" He screamed. "You're a bucket!"
To this, the bucket furrowed its brow.
"No," said the bucket. "Not since the evil wizard Gambhorra'ta first ensnared me in his machinations as payback for the sacred amulet I stole from his treasured vaults.
I was young back then, and could not conceive the ramifications of -"
"NO!!" Stanley screamed even louder this time. "This... is... stupid!! You... are... a... bucket!!
This is so stupid! Why are we even doing this?!"
As Stanley screamed and screamed and screamed, the bucket revealed its true form,
transforming into a mighty beast of untold power, its fangs glistening like-
My god. Stanley, you did it!
You saved us from the bucket!
Thank god you already had all twelve Emblems of Sages and knew the incantations to summon their true power.
Otherwise we would have easily been overwhelmed by the bucket's power.
I'm speechless. You've demonstrated such bravery here today.
Come, let's restart the game! And we'll agree to never again go trifling with this bucket, nor the dark magic cast away inside of it.
"We've done it. We've escaped from that dull office and that pesky narrator. At last, out here in the white void, we are alone. Now, and for the first time, I can reveal to you my true self."
The bucket began to tell Stanley of its life and its history.
Of the countless wars it witnessed desecrating the land and lives of untold numbers of innocent humans and the bucket's own complicity therein.
Of sadness and regret and the many years it spent dwelling on the actions it might have taken to curb the madness and the decay.
If only it had been stronger.
Of hope and redemption and its crusade to uplift the stock of life for the common man. To manifest justice where none existed.
And the bittersweet reality of time, to see one's dreams and wishes met halfway.
Meted out in parcels like charity and abandoned as soon as the warm glow of inspiration begins to dim.
The opportunities to do so much more.
There was so much it could have done.
"Perhaps..." The bucket wondered to itself.
Perhaps if it had seen its own darkness with a clearer perception... This was way too much for Stanley.
"What are you talking about?!" He screamed. "You're a bucket!"
To this, the bucket furrowed its brow.
"No," said the bucket. "Not since the evil wizard Gambhorra'ta first ensnared me in his machinations as payback for the sacred amulet I stole from his treasured vaults.
I was young back then, and could not conceive the ramifications of -"
"NO!!" Stanley screamed even louder this time. "This... is... stupid!! You... are... a... bucket!!
This is so stupid! Why are we even doing this?!"
As Stanley screamed and screamed and screamed, the bucket revealed its true form,
transforming into a mighty beast of untold power, its fangs glistening like-
My god. Stanley, you did it!
You saved us from the bucket!
Thank god you already had all twelve Emblems of Sages and knew the incantations to summon their true power.
Otherwise we would have easily been overwhelmed by the bucket's power.
I'm speechless. You've demonstrated such bravery here today.
Come, let's restart the game! And we'll agree to never again go trifling with this bucket, nor the dark magic cast away inside of it.
M
Error 403
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
M
Okay I don't think we can fix this gang.
M
Abort mission.
What is bucket
Servers crashing tismspam until it vvorks better
M
Error 403
This bucket cannot be viewed
You are not authorized to view this bucket
This bucket does not exist or is not publicly accessible at this URL. Check the URL of the bucket that you’re looking for or contact the owner to enable Public access.
Is this your bucket?
Learn how to enable Public Access
Similar threads
Calamari Sun
Users who are viewing this thread
