Untitled attachment

Notices where this attachment appears

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Monday, 09-Jun-2025 02:46:07 JST silverpill

   APx is finally available on crates.io / docs.rs

   https://docs.rs/apx_sdk/latest/apx_sdk/

   This is an ActivityPub library used internally in Mitra and in other my projects.

   Unlike some other ActivityPub libraries, this library is low-level. It doesn't restrict what databases or frameworks could be used, and doesn't care about object types or properties. There are only URIs, keys, signatures, JSON documents and HTTP requests.
   It also contains primitives for building nomadic applications (FEP-ef61).

   The license is AGPL-3, but I might consider changing it to a more permissive one.

   #apx #activitypub #rust

2. Embed this notice
   Lynnesbæn :bune_ylw: (lynnesbian@fedi.lynnesbian.space)'s status on Saturday, 15-Mar-2025 17:46:44 JST Lynnesbæn :bune_ylw:

   in reply to

   if there are any #GNOME designers/artists (gnomes? gnome heads? gnomish sourcerers? gnaphic gnesigners?) seeing this, does it comply with the HIG in your opinion? what would you suggest changing if not?

   the cheesecrater icon uses the standard rustacean image, which doesn't have that smooth, rounded look the HIG usually suggests, but i lack the skill to make a "blobby" version of ferris. :ferris_og:

   the crates browser, with its triple-pane layout (third screenshot), is the most complicated of them, but it's based on the design of the crates.io website, which displays the readme alongside a right-aligned "metadata" pane.

   (also: either it's very hard to write descriptive alt text for UI design screenshots, or i am very bad at it. possibly both.)

   #design #adwaita

3. Embed this notice
   Lynnesbæn :bune_ylw: (lynnesbian@fedi.lynnesbian.space)'s status on Saturday, 15-Mar-2025 17:46:44 JST Lynnesbæn :bune_ylw:

   working on a little GUI for browsing crates.io. i've spent about a week on it and this is what i've got so far

4. Embed this notice
   Jeff "never puts away anything, especially oven mitts" Cliff, Bringer of Nightmares 🏴‍☠️🦝🐙 🇱🇧🧯 🇨🇦🐧 (jeffcliff@shitposter.world)'s status on Friday, 28-Feb-2025 11:53:47 JST Jeff "never puts away anything, especially oven mitts" Cliff, Bringer of Nightmares 🏴‍☠️🦝🐙 🇱🇧🧯 🇨🇦🐧

   in reply to
   @aristoh4ck8r
   
   >What you're seeing in my Cargo.toml file are standard Rust crates (not cranes
   
   No shit. That is the problem. Standard rust crates AND THE ENTIRE LANGUAGE is tightly coupled with microsoft's walled garden
   
   >Using crates from repositories like crates.io is actually the recommended approach in the Rust ecosystem, similar to how developers use npm packages in JavaScript or pip packages in Python
   
   AGAIN THAT IS THE FUCKING PROBLEM. Also NPM is microsoft and is part of the microsoft walled garden.
   
   I have now spent THOUSANDS of hours recovering software in the python ecosystem from github because people assume it's totally OK to have software that relies on microsoft's walled garden
   
   > These crates are typically well-tested, maintained by the communit
   
   Do not fucking start with me.
5. Embed this notice
   aristoh4ck8r (aristoh4ck8r@nicecrew.digital)'s status on Friday, 28-Feb-2025 11:53:47 JST aristoh4ck8r

   in reply to
   @jeffcliff I appreciate your feedback on my code, but I wanted to clarify something about Rust development practices. What you're seeing in my Cargo.toml file are standard Rust crates (not cranes I made a typo in the previous messages), which are the equivalent of libraries or packages in other programming languages.
   
   Using crates from repositories like crates.io is actually the recommended approach in the Rust ecosystem, similar to how developers use npm packages in JavaScript or pip packages in Python. The Rust core team and community have designed the language specifically to work with these modular components.
   
   These crates are typically well-tested, maintained by the community, and follow Rust's strong safety guarantees. Using them is considered a best practice rather than a shortcoming, as it allows developers to build on established foundations rather than reimplementing everything from scratch.
   
   I'd be happy to discuss specific concerns you might have about any particular dependencies I've chosen if you'd like."
6. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 16-Feb-2025 01:18:26 JST Haelwenn /элвэн/ :triskell:

   in reply to
   @bortzmeyer Maybe you can publish and still have it usable outside of crates.io though? Quite like how you can publish & use python libraries without using PyPi for everything.
   (I haven't done any Rust, so I wouldn't know)