It's been a while and we're overdue for a new release. Not a whole lot has changed, mostly refinements here and there. The same, but better.
tedu Now • 100%
We're all trying to figure out where these headlines came from. The stable channel with all the fixes does not (at this time) bundle the warning. How is that users have become confused and believe the dev channel is the only way to get security fixes?
tedu Now • 100%
I don't know why you'd jump to the dev channel, though. Just apply the stable channel update.
tedu Now • 98%
I'm going to go way out on a limb here and guess nothing will happen if I do neither.
tedu Now • 100%
Should have gone with Barclay as Kovitch.
tedu Now • 100%
I'm sure it still works in photoshop or whatever, just not the windows stuff.
tedu Now • 100%
Because it comes from a laptop with rounded corners on the top of the lid and a flat hinge on the bottom.
tedu Now • 95%
What critical information are people putting in the six missing pixels?
tedu Now • 100%
Now people want recall?
tedu Now • 100%
What?
tedu Now • 39%
Are these millions of potential customers in the room with us?
There's now a (none) group, which is where posts that don't belong to a group land, instead of being dropped. This improves compat with microblog oriented services. You can't browse the none group yet; the URL just 404s, which actually seems appropriate. I still think different interfaces for different purposes is the way, but this was pretty low effort. Maybe there's one person always posting links and you'd like to see their posts on your cool links aggregator. I pulled in a few honks from [myself](https://azorius.net/u/tedu@honk.tedunangst.com).
tedu Now • 90%
A simpler explanation is that users are tired of everybody with a customer support issue running to daddy HN and making a big fuss trying to get their way.
tedu Now • 100%
UTM may be somewhat shinier, but you can run anything you like in qemu on a mac.
tedu Now • 100%
Jesus, what clickbait. It's a bug in fluent bit.
tedu Now • 100%
I'm impressed the verge was able to refer to the issue without using the word nudes in the headline.
tedu Now • 86%
I will never use a Windows laptop because it wakes up in the middle of the night to apply some stupid update, then glitches out, and can't go back to sleep. So every morning I find a laptop with a dead battery. Sometimes if I wake up early, it'll still be hot from whatever it was doing.
Fixing that stupid bug should have been easier than porting the whole OS and app stack and emulator to a new CPU arch. And I have no faith they fixed the bug anyway, so it'll probably still happen to ARM models. So no thank you.
tedu Now • 100%
Why was the reddit post source deleted?
tedu Now • 100%
Honestly, the mastodon obsession seems like a you problem. Talk about what you want on the fediverse. Maybe mastodon users see it, maybe they don't, who cares.
Tags are now linked at the bottom of each post and viewable on the web, such as [/tag/activitypub](/tag/activitypub) or [/tag/c](/tag/c). Didn't get to parsing hashtags out of the post body yet, but that's not so urgent. *[#done](/tag/done).*
I've implemented basic support for composite groups (groups of groups). (Formerly named meta groups.) There's a lot of redundancy because of the federated nature of the azoriverse, with similar groups duplicated across multiple servers. Composite groups are a solution, by presenting users with a (somewhat transparent) single group that collects all of the posts. I've created two groups, [metaprog](https://azorius.net/g/metaprog) and [technoscience](https://azorius.net/g/technoscience), for demo and testing. This is still preliminary, so federation doesn't quite work yet, but eventually the goal would be that you can follow a composite group, and it will forward activities. Instead of having to individually chase down every new programming group that gets created, you could delegate that the metaprog admin (me) to keep the group list updated. Some basic federation is now working. I think it probably won't work from Lemmy, ironically, but azorius, honk and mastodon, etc. should be able to follow these groups. (Don't follow from azorius until after updating.)
Mostly bugfixes and some refinements. * Some performance improvements. * Newest sort for comments. * Activity tab shows active threads. * Add some improved support for compat with Note activities. * Only accept and serve activities with the correct content type.
There's a few changes in the pipeline to work a little better with mastodon (sigh). It's gone through a few iterations of live testing, but once I think it's stable will release. Don't want to wait too long, this also has the security fix for activities served with the wrong content type. A few other tweaks that I may get to, or not.
Minor update. A few refinements and fixes. * Fix 32 bit support. * Close database to give the wal file a chance to checkpoint. * Reply notif links to comment. * Collapse and expand threads. * Dedupe posts across groups.
Finally got around to fixing a common annoyance. There's four different groups covering "technology" and the same link gets posted to all of them every time. These are now deduped in the main feed.
New release. Not a lot of changes, mostly bug fixes and some interop improvements. Biggest feature of note is post previews. There's not a lot happening. I like it.
antonz.org
> Based on the Go 1.22 release notes from the Go team (3-Clause BSD License), with many interactive examples added. This blog post is synchronized with the source document as it gets updated.
www.fourbardesign.com
> High pressure, high forces, long lever arms...all of that meant heavy and strong (read: expensive) parts which I was not looking forward to having to fabricate. Instead, I settled on the simpler idea of harnessing the power of compressed gas. Instead of using a high mechanical advantage lever to push a piston, compressed CO2 would be dispensed from a small and inexpensive 12g or 16g cartridge which would then generate the requisite pressure to properly extract espresso. This concept is not actually novel; both an unsuccessful kickstarter and a now-defunct handheld espresso maker (with a fanatical user base) employed this mechanism.
> In this write-up, we’ll delve into how, through differential fuzzing, we uncovered a bug in Go’s exp/net HTML’s tokenizer. We’ll show potential XSS implications of this flaw. Additionally, we’ll outline how Google assessed this finding within their VRP program and guide how to engage and employ fuzzing to evaluate your software.
go.dev
> Go 1.21 adds a new port targeting the WASI preview 1 syscall API through the new GOOS value wasip1. This port builds on the existing WebAssembly port introduced in Go 1.11. > WebAssembly (Wasm) is a binary instruction format originally designed for the web. It represents a standard that allows developers to run high-performance, low-level code directly in web browsers at near-native speeds. > Go first added support for compiling to Wasm in the 1.11 release, through the js/wasm port. This allowed Go code compiled using the Go compiler to be executed in web browsers, but it required a JavaScript execution environment. > As the use of Wasm has grown, so have use cases outside of the browser. Many cloud providers are now offering services that allow the user to execute Wasm executables directly, leveraging the new WebAssembly System Interface (WASI) syscall API.
> Cgo calls take about 40ns, about the same time encoding/json takes to parse a single digit integer. On my 20 core machine Cgo call performance scales with core count up to about 16 cores, after which some known contention issues slow things down.
Release day classic! Fixed two bugs not noticed until just after release. One was a crash in the markdown parser which ironically broke the 0.2 release announcement. Pushed an emergency fix, will resolve with a better fix in time. Also trying out committing release numbers to the in tree version string.
New release. Lots of features and fixes. Notifications, chat, (experimental) filters. The UI is basically the same, but lots of stuff reworked so it's more obvious what you're doing and where you're going. I think this is approaching my vision for the software. It's not done, but all the pieces are in place. \=== 0.3.0 Imperfect Future * Subscribe to post for comment notifications. * Very basic search feature. * Syntax highlighting for code blocks. * More consistently useful logging. * Experimental filters. * Inline images in posts. * Cleaner UI and navigation. * Dark mode. * Improved URL scheme. * Previews for picture groups. * Normalize some links (youtube only atm). * Improved federation. * Include replies collection in posts. * Background refresh. * Group chat. * A little more tag support. * Nicer online help. * Detect recent duplicate links. * Site alerts, woop, woop. * Initial support for featured posts. * Notifications for most events.
> It was obvious already before that NVD really does not try very hard to actually understand or figure out the problem they grade. In this case it is quite impossible for me to understand how they could come up with this severity level. It’s like they saw “integer overflow” and figure that wow, yeah that is the most horrible flaw we can imagine, but clearly nobody at NVD engaged their brains nor looked at the “vulnerable” code or the patch that fixed the bug. Anyone that looks can see that this is not a security problem.
> The vulnerability should be obvious: at some point in the boot process, the VMK transits unencrypted between the TPM and the CPU. This means that it can be captured and used to decrypt the disk.
go.dev
> The new log/slog package in Go 1.21 brings structured logging to the standard library. Structured logs use key-value pairs so they can be parsed, filtered, searched, and analyzed quickly and reliably. For servers, logging is an important way for developers to observe the detailed behavior of the system, and often the first place they go to debug it. Logs therefore tend to be voluminous, and the ability to search and filter them quickly is essential.
Very basic, only the site: operator and plain text is implemented, but if you were worried that you may have missed out on some twitter drama, it's now only a few keystrokes away.
tedu
tedu@ azorius.netI'm the boss! Please enjoy my finely curated links.