Gregory's Server
|
Another piece of risky code that relies on Go compiler internals is added to the Rube Goldberg machine that is the #GoActivityPub library... Sigh. The link to the code: https://git.sr.ht/~mariusor/ssm/tree/af069f49e3607f1233a0680bb779d236c8dcb897/item/error.go#L86 I hope Pleroma devs have seen this pseudo bug report from Rachel Kroll: Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse. I'm the creator of @fedify, an #ActivityPub server framework in #TypeScript, and @hollo, an ActivityPub-enabled microblogging software for single users. I'm also very interested in East Asian languages (so-called #CJK) and #Unicode. Feel free to talk to me in #English, #Korean (#한국어), or #Japanese (#日本語), or even in Literary Chinese (#文言文, #漢文)! Fun fact: #Letterbook contributors can now get a page on our docs site, complete with rel=me verification In case you wanted another check mark on your profile It's been a high volume social media day for me, apologies to all followers that had to sit through me arguing about democracy. I promise I'll stop. :) @veronica someone seems to be working on a way for projects (and probably services or people) to advertise their preferred monetization options: https://floss.fund/funding-manifest/ I remember you were curious about options that could be used for that on Fediverse platforms. This looks like it could fit the bill with some elbow grease. Happy to release #bofied v1.2.0, the latest version of my modern, scriptable OSS netboot server after a two year hiatus! It has a modernized #Go backend and almost completely rewritten PWA frontend (in #WebAssembly), plus standard WebDAV and gRPC management APIs! https://github.com/pojntfx/bofied I've finally got off my ass and created a Codeberg account in order to submit my first PR to the #FEP repository. I'm not very familiar with the FEP submission etiquette so any pointers from more experienced people would be helpful. The PR: https://codeberg.org/fediverse/fep/pulls/452 Mailing list thread for feedback: https://lists.sr.ht/~mariusor/go-activitypub-discuss/%3Cwecobrezdaeqzfsukst42hncuuimomii5oeixonirrksrvs4md@4l76dr4obisi%3E I'm working to build an ethical home for #Musicians that doesn't siphon their work into the #AI torment nexus. Today, I've installed a new firewall on #Bandwagon called "Silicon Dome" that blocks every known AI and malicious bot. With regular monitoring and updates, Silicon Dome will actively protect human creativity from the rampant AIs already out in the wild. I think it's a win for humanity. Whelp, we finally committed to releasing an experimental release of Pidgin 3.0 by the end of the year! To be clear, this is a **pre-alpha** release, but you can read more here https://discourse.imfreedom.org/t/pidgin-3-0-0-experimental-1-announcement/216 For today's #ThankYouTuesday, I want to send my regards to all people that have contributed any piece of code to #snac or that have sponsored me via one way or another.
You, people, are great. 4️⃣ Here's the 4th post highlighting key new features of the upcoming v257 release of systemd. #systemd257 One of the key features of systemd we have talked about in the past years are UKIs, i.e. "unified kernel images", which is a combination of a Linux kernel, an initrd, and more into a single unified PE binary, that can be signed as a whole for SecureBoot, measured as a whole and updated as a whole. In my PoV UKIs are a central concept of securing the Linux boot process.  But: they do have some disadvantages. They typically imply (not strictly, but typically) that they are built on OS vendor build systems instead of locally. This is different from the status quo ante, where the initrd is typically built on the deployed system (at least on generic distros), and thus highly adapted to the local system. UKIs being vendor-built hence means they are a lot more rigid, less flexible than the traditional way. So far this meant you'd have to settle…  @pid_eins UKIs are fine, but systemd-stub churn every release makes it more of a liability than a stable foundation to build on. Stuff like sysexts etc could poke holes in established security models similar (but restricted in scope) to how systemd poked giant holes into full disk encryption when it added DDI automount. It's a massive effort to keep up with changes and validate them and it's pretty concerning. So you might end up not doing that, and end up with vulnerabilities in your product. Since I'm such a fan of handmade programming, I find myself this fine eve implementing document indexing from scratch(ish) for my #GoActivityPub library storage backends. Backend stuff for domain permission drafts is in place, working on the frontend / settings panel stuff now. Domain permission drafts will let you create domain block or domain allow drafts either manually or from a block / allow list subscription. You can then remove the draft if you decide you don't want it, or accept the draft and put it into force as a block or allow. |
