38 karma · joined July 31, 2025
Tons of ads? Really? I had to turn off my adblocker to check, but there is a single ad block on the bottom left. Is that considered a ton?
https://github.com/LawnchairLauncher/lawnchair/blob/b0ecfb84...
https://www.reddit.com/r/Android/comments/7azc2i/deleted_by_...
https://github.com/LawnchairLauncher/lawnchair/issues/940
https://github.com/LawnchairLauncher/lawnchair/pull/902
From the dev themselves in that PR
> @dasBiest: It's our business to prevent unauthorized use of iconpacks.
> Just like Substratum is keeping you away from using pirated themes for example.
"Two samples from the air induction elbow were subjected to testing, using a heat-flux differential scanning calorimeter, to determine their glass transition temperature. The measured glass transition temperature for the first sample was 52.8°C, and 54.0°C for the second sample"
Yeah, they might have used ABS-CF filament, but unless they got it from a good brand that uses good resin and proper printing parameters, the actual Tg will be lower, plus the stress from the vibration/load could have made the part fail if it was not for the heat later in flight.
https://hackerone.com/reports/2823554
Where the reporter says, "Sorry didnt mean to waste anyones time Badger, I thought you would be happy about this.".
People using LLMs think they are helping but in reality, they are not.
Prusa isn't fully opensource, but has the worst enclosed chamber printer imo.
Bambu isn't open source in the slightest (beside the slicer).
You are never going to print PC on a bambu either way, at least not Pure PC. Blends, sure, you need at least 100c chambers for pure PC.
diy kits are the way to go, but it is going take you a LONG time. a voron, ratrig, or annex k3 are your best bets with the requirements you want. each kit has their weaknesses, and most of them, are going to require upgrades from their BOM.
Complete the XPath 1.0 implementation. (Done!)
Implement all XSLT v1.0 functionality. (Done!)
Improve XDM, XPath; achieve v2.0 compliance.
Add v2.0 features to the XSLT engine.
Further improve XDM, XPath; achieve v3.1 compliance.
Add remaining v3.0 features to the XSLT engine.
NB. We're picking the low-hanging fruit first. So major, fundamental features of the languages are being implemented to begin with. The fine detail will be added later. Although the eventual desire is to implement all of XSLT v3.0 functionality, some more advanced features will be implemented sooner rather than later.
https://gitlab.gnome.org/World/Rust/markup-rs/xrust#the-plan