kepford's avatar
kepford
kepford@nostrplebs.com
npub1qqqq...hq0q
Jesus follower | Bitcoiner | Freedom Maximalist | Javascript | Drupal | Newsletter Publisher
kepford's avatar
kepford 9 months ago
My friend thats an XRP maxi... Bitcoin is old. Bitcoin is slow. Me. Nah.
kepford's avatar
kepford 10 months ago
Economics in Three Lessons and One Hundred Economics Laws Any stackers read this book. I've never heard of it but I love and recommend the book it is inspired by "Economics in One Lesson". I heard about it while listening to the "[Haman Nature](https://hamannature.substack.com/p/how-profits-actually-tend-to-lower)" podcast. Which is worth a listen by the way. I'm wondering if this is a good book to recommend people as an easy primer on econ. Economics in One Lesson really opened my eyes when I first read it many years ago. I sent me down a train of thought with many questions. Questioning many things I had just taken at face value. It wasn't a hard read and it was entertaining. Few econ books can make those claims.
kepford's avatar
kepford 11 months ago
What I see 99% of time in Bitcoin culture is ego. It's not logic. There are a few exceptions but most of the arguments and disagreements are mostly proud men with huge egos wanting to be right. There are exceptions but over and over again these beefs come down to ego, not problem solving and arriving at consensus.
kepford's avatar
kepford 11 months ago
AOSP isn't dead, but Google just landed a huge blow to custom ROM developers Others have [mentioned](https://stacker.news/items/1005055) this but this article is a pretty good summary. ## Is AOSP going away? Google says no >As promised, Google published the source code for Android 16 this week, allowing independent developers to compile their own builds of the new operating system. This source code was uploaded to the Android Open Source Project (AOSP), as usual, under the permissive Apache 2.0 license. >However, multiple developers quickly noticed a glaring omission from the Android 16 source code release: the device trees for Pixel devices were missing. Google also failed to upload new driver binaries for each Pixel device and released the kernel source code with a squashed commit history. Since Google has shared the device trees, driver binaries, and full kernel source code commit history for years, its omission in this week’s release was concerning. >These omissions led some to speculate this week that Google was taking the first step in a plan to discontinue AOSP. In response, Google’s VP and GM of Android Platform, Seang Chau, refuted these claims. He addressed the speculation in a post on X, stating that “AOSP is NOT going away.” ## How does this impact developers of OS's like Graphene and CalyXOS? > Previously, Google made it simple for developers to build AOSP for Pixel devices, but that support is now gone. Developers simply had to “pull the configurations [that] Google created,” add their customizations, and then build. Now, however, they will need to take the old device trees that Google released for Android 15 and “blindly guess and reverse engineer from the prebuilt [binaries] what changes are needed each month.” So this is not good at all but not game over. > These omissions led some to speculate this week that Google was taking the first step in a plan to discontinue AOSP. In response, Google’s VP and GM of Android Platform, Seang Chau, refuted these claims. He addressed the speculation in a post on X, stating that “AOSP is NOT going away.” > He also confirmed the omission of Pixel device trees is intentional, stating that “AOSP needs a reference target that is flexible, configurable, and affordable — independent of any particular hardware, including those from Google.” Instead of supporting AOSP builds on Pixel devices, Google will support the virtual Android device “Cuttlefish” as its reference target. Cuttlefish runs on PCs, allowing Google and platform developers to test new hardware features. Google will also continue to support GSI targets, which are generic system images that can be installed on nearly any Android device. And this little tidbit seems very concerning. > Furthermore, Google’s decision to squash the kernel source code’s commit history also hinders custom development. The Pixel’s kernel source code was often used as a “reference point for other devices to take features, bug fixes, and security patches from,” but with the history now reduced to a single commit, this is no longer feasible. ## My Take Google is doing this intentionally and strategically to limit the reach and competition it is getting from alternative ROMS. The popularity of Graphene and other ROMS has grown since 2020 when I first started trying these systems out. This is a pattern we have seen in companies built on open source over the past few years. There are business reasons for some of the changes but also there are technical reasons. I don't like it one bit. Google has long claimed to be a champion of open source and honestly while the custom ROM space is growing the idea that its a threat to Google is laughable. It is possible that this is just Google tightening the belt and reducing dev overhead. Either way its not good for people who develop more privacy respecting mobile computers and signals a massive need for open hardware and a truly open phone OS.
kepford's avatar
kepford 11 months ago
Comedian T.J. Miller Tries to Give People Bitcoin There are a few lines Miller has in response to some bitcoin haters that I loved. I found the whole idea of trying to give people bitcoin while doing stand-up pretty entertaining. What do you think? Should this be in bitcoin or the lol territory?
kepford's avatar
kepford 1 year ago
I'm not really interested in running Knots but it seems to me that there should be more effort in getting more devs working on it.
kepford's avatar
kepford 1 year ago
Firefox could be doomed without Google search deal, says executive > Firefox could be put out of business should a court implement all the Justice Department’s proposals to restrict Google’s search monopoly, an executive for the browser owner Mozilla testified Friday. “It’s very frightening,” Mozilla CFO Eric Muhlheim said. The irony is wild. originally posted at