Filebase (@Filebase) header
Filebase (@Filebase) profile picture

Filebase

@Filebase

Fast S3-Compatible Object Storage with Free Egress ⚡ Reliable, scalable storage for developers and businesses. 5 GB free ↓

 Boston, MA
filebase.com
Joined May 2019
  • Tweets4.5K
  • Following142
  • Followers4.3K
HTTP success is not proof every requested object was deleted. With S3 DeleteObjects, inspect the per-key results and error entries. Filebase supports batches of up to 1,000 keys. Review the candidate list first; then reconcile the response: filebase.com/docs/s3-api/com…
Filebase graphic: 200 IS NOT THE WHOLE RESULT. Read the per-key outcome before declaring success. KEY; RESULT; old-a.json; DELETED; old-b.json; ERROR: INSPECT; old-c.json; DELETED. Illustrative response. Review deletion candidates before sending.

ALT Filebase graphic: 200 IS NOT THE WHOLE RESULT. Read the per-key outcome before declaring success. KEY; RESULT; old-a.json; DELETED; old-b.json; ERROR: INSPECT; old-c.json; DELETED. Illustrative response. Review deletion candidates before sending.

76
A cache hit is not automatically free bandwidth. Reuse in a browser can avoid a gateway fetch; bytes served by a Filebase dedicated IPFS gateway count toward Gateway bandwidth. Measure where the response was served. Billing categories: filebase.com/docs/ipfs/bandw…
Filebase graphic: WHICH CACHE SERVED THE BYTES?. The response path matters more than a hit-rate headline. BROWSER REUSE; NO NEW GATEWAY FETCH; GATEWAY RESPONSE; OUTBOUND BYTES COUNT. Dedicated IPFS gateway response size contributes to Gateway bandwidth.

ALT Filebase graphic: WHICH CACHE SERVED THE BYTES?. The response path matters more than a hit-rate headline. BROWSER REUSE; NO NEW GATEWAY FETCH; GATEWAY RESPONSE; OUTBOUND BYTES COUNT. Dedicated IPFS gateway response size contributes to Gateway bandwidth.

65
A peer being online does not guarantee a direct connection. libp2p can use relays and attempt direct connection upgrades across NATs. A relay forwards a connection; it is not a promise to persist your IPFS content. #libp2p
Filebase graphic: REACHABLE != RETAINED. A relay carries a connection. Storage retains content. PEER A; RELAY PATH; PEER B; DIRECT PATH WHEN POSSIBLE. Network reachability is separate from data persistence.

ALT Filebase graphic: REACHABLE != RETAINED. A relay carries a connection. Storage retains content. PEER A; RELAY PATH; PEER B; DIRECT PATH WHEN POSSIBLE. Network reachability is separate from data persistence.

1
74
Renaming a bucket file is a path operation. Filebase RPC files/mv takes the source and destination as two arg values. Test argument ordering and destination behavior in a disposable fixture before adapting a script. RPC reference: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: TWO PATHS. ONE MOVE.. Repeated arg parameters have distinct roles. POST /api/v0/files/mv; arg=/old.txt; arg=/new.txt; FIRST = SOURCE | SECOND = DESTINATION. Use a query builder that preserves repeated parameter names.

ALT Filebase graphic: TWO PATHS. ONE MOVE.. Repeated arg parameters have distinct roles. POST /api/v0/files/mv; arg=/old.txt; arg=/new.txt; FIRST = SOURCE | SECOND = DESTINATION. Use a query builder that preserves repeated parameter names.

76
A key containing spaces, + or # is not ready to paste into a URL. Give the SDK the actual key and let it build the request. Don't double-encode a pre-signed URL after signing. Key naming and URL encoding are different steps. Filebase S3: filebase.com/docs/s3-api/sup…
Filebase graphic: KEY != ENCODED URL. Let one layer own request construction. Stored key: reports/Q1 + Q2.pdf; SDK input: actual object key; Request URL: encoded by SDK; Pre-signed URL: preserve as returned. Avoid double encoding or edits after signing.

ALT Filebase graphic: KEY != ENCODED URL. Let one layer own request construction. Stored key: reports/Q1 + Q2.pdf; SDK input: actual object key; Request URL: encoded by SDK; Pre-signed URL: preserve as returned. Avoid double encoding or edits after signing.

1
129
Three identical exports under three keys can be avoidable application work. Check content before creating another object and map consumers to the retained export. Don't assume Filebase provides an automatic deduplication discount. Current pricing: filebase.com/pricing/?utm_so…
Filebase graphic: ONE EXPORT. MANY REFERENCES.. Avoid redundant payloads in the application workflow. IDENTICAL EXPORT INPUT; ONE RETAINED OBJECT; CONSUMER A; CONSUMER B. Application-level reuse. No automatic deduplication discount assumed.

ALT Filebase graphic: ONE EXPORT. MANY REFERENCES.. Avoid redundant payloads in the application workflow. IDENTICAL EXPORT INPUT; ONE RETAINED OBJECT; CONSUMER A; CONSUMER B. Application-level reuse. No automatic deduplication discount assumed.

1
80
For browser apps, gateway URL shape is an isolation decision. Path-style URLs can share an origin; CID subdomains give content separate origins on a correctly configured gateway. An IPFS content address alone does not set browser boundaries. #IPFS
Filebase graphic: URL SHAPE SETS THE ORIGIN. Content addressing and browser isolation are different layers. gateway/ipfs/CID; SHARED HOST ORIGIN; CID.ipfs.gateway; CID-SPECIFIC ORIGIN. Requires a correctly configured subdomain gateway.

ALT Filebase graphic: URL SHAPE SETS THE ORIGIN. Content addressing and browser isolation are different layers. gateway/ipfs/CID; SHARED HOST ORIGIN; CID.ipfs.gateway; CID-SPECIFIC ORIGIN. Requires a correctly configured subdomain gateway.

3
141
Need a filename beneath an IPFS root? Filebase RPC add supports wrap-with-directory=true. The returned CID identifies the wrapper directory, so retrieval uses that CID plus the file path, not the directory as file bytes. Route details: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: THE WRAPPER IS THE ROOT. A wrapped upload needs its file path at retrieval. invoice.pdf; add + directory wrapping; DIRECTORY CID; /invoice.pdf. Not a Bucket CID or an incremental release workflow.

ALT Filebase graphic: THE WRAPPER IS THE ROOT. A wrapped upload needs its file path at retrieval. invoice.pdf; add + directory wrapping; DIRECTORY CID; /invoice.pdf. Not a Bucket CID or an incremental release workflow.

1
146
A failed download need not restart at byte zero. Filebase supports Range GETs. Resume from the saved byte offset, check Content-Range, and confirm the object hasn't changed before appending. Supported operations: filebase.com/docs/s3-api/com…
Filebase graphic: RESUME THE DOWNLOAD. Append only when the object and range still match. SAVED BYTES; 0; OFFSET; REQUEST REMAINING RANGE; VERIFY BEFORE APPENDING. A changed object requires a different recovery path.

ALT Filebase graphic: RESUME THE DOWNLOAD. Append only when the object and range still match. SAVED BYTES; 0; OFFSET; REQUEST REMAINING RANGE; VERIFY BEFORE APPENDING. A changed object requires a different recovery path.

72
An illustrative 4 GB text export compressed to 1 GB uses 3 GB fewer stored bytes. Filebase does not automatically transcode gzip/Brotli delivery; set Content-Encoding when serving compressed content. Check the header guidance: filebase.com/docs/concepts/c…
Filebase graphic: STORE THE SMALLER REPRESENTATION. Measure compression. Configure delivery headers. 4 GB; ILLUSTRATIVE ORIGINAL; 1 GB; COMPRESSED PAYLOAD; 75%; FEWER STORED BYTES. Illustrative 4:1 compression. Not a benchmark or bill-savings claim.

ALT Filebase graphic: STORE THE SMALLER REPRESENTATION. Measure compression. Configure delivery headers. 4 GB; ILLUSTRATIVE ORIGINAL; 1 GB; COMPRESSED PAYLOAD; 75%; FEWER STORED BYTES. Illustrative 4:1 compression. Not a benchmark or bill-savings claim.

2
134
Load more