Bloat refers to something wastefully and unnecessarily large. In software, it may refer to the presence of program code that is perceived as unnecessarily long, slow, or otherwise wasteful of resources, but a considerable amount of bloat originates from external dependencies.
Blob store design challenges
It's just hashed data, what's so complex about a blob store anyway?
Complete Guide: Remove Android Bloatware Safely with App Manager & Canta
Learn how to safely remove Android bloatware using App Manager and Canta. Step-by-step tutorial with screenshots, safety tips, and app alternatives.
Blobs Against The Sky (@bats.skydrops.app)
Horrible thoughts. Permanent data. Official hub for decentralized cards, and questionable life choices. Built by @v.skydrops.app as a testament to human error. Game Engine @blobs.skydrops.app
Tiles: take a blob's mimeType from what uploadBlob returns #11
The tiles appendix recommends `application/octet-stream` as the `mimeType` of every blob reference. On some PDS implementations that recommendation makes a tile unpublishable as soon as it contains a file whose type can be recognised from its bytes. The reference implementation (bluesky-social/atproto, packages/pds, actor-`store/blob/transactor.ts`) does two things that together cause it: - On `com.atproto.repo.uploadBlob` it sniffs the bytes and stores the blob under the type it recognises (`image/png`, `audio/wav`, `font/woff2`, ...). The type the upload declared is used only when nothing is recognised, which is the case for HTML, CSS, JavaScript and JSON. - When a record that references a newly uploaded blob is written, it compares the reference's `mimeType` with the stored type and refuses the whole write if they differ: "Referenced Mimetype does not match stored blob. Expected: image/png". So a publisher that follows the appendix and writes `application/octet-stream` everywhere succeeds for a tile made only of text, and fails at the `com.atproto.repo.putRecord` of the tile's record for any tile with an image, a sound or a font in it. appmosphe.re's publish page does exactly this and fails that way, for example with "Expected: audio/wav" for a tile carrying a WAV sample. `atile publish` does not fail, because it sniffs each file itself with the same file-type library and writes what it finds; that only works as long as its sniffing agrees with that of the implementation it publishes to. `uploadBlob` already answers with the complete blob reference, `mimeType` included. Using that reference as the resource's src is correct on every implementation: one that sniffs reports the type it stored, and one that does not reports the declared `application/octet-stream`, which is what the appendix recommended before. The content-type the tile is served with stays separate and unaffected.
BitChat cache poisoning and replay in Bluetooth mesh
BARGHEST found a cache poisoning attack in BitChat and replay flaw in BLE mesh synchronization that enabled durable network disruption before patching.
Blorp – A Threadiverse client for Lemmy and PieFed
Blorp – A Threadiverse client for Lemmy and PieFed. Web, iOS & macOS, and more!
Bluvy — A suite of free and open applications for the AT Protocol ecosystem
Discover Bluvy, an ecosystem of modern, private, and open-source applications built around the AT Protocol (Bluvy Messenger, Bluvy Dex, Bluvy Tube).
at this point for each day that goes i hate the atproto blob type more and more. like. not blobs themselves at all. but the damn data model representation of a blob reference. why does it have the mime type there ... arguably even the size. could technically even just be a plain CID link but cant
Each time someone says "Bluesky" and means one specific thing—or all four things at once—the conceptual fog thickens.
Talking in a room with no name.
wecanjustdothings.leaflet.pub
