Might play with this at work next week.
<author>
from <entry>
s to <feed>
, Newsboat marked all old affected articles as unread. IDs were untouched, of course. Need to investigate that. Had something similar happen with another feed change I did some time ago. Can't remember what that was, though.
Great, last system update broke something, building from current master I get:
/usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'
What the heck!?
And it also appears that I’m not really able to reproduce this unread bug. It only kind of works a single time. And it has something to do with my config. Not sure what it is yet. I also noticed that the <updated>
timestamps in the entries somehow shifted between the old and new feed. Da fuq!?
starting work on felt - virtual tabletop for D&D
[47°09′00″S, 126°43′32″W] Storm recedes – back to normal work
Build, Share, and Run WebAssembly Apps Using Docker
Did you know Wasm and Docker can work together? Learn more about creating WebAssembly apps with Docker in this exciting demo breakdown. ⌘ Read more
[47°09′36″S, 126°43′48″W] Storm recedes – back to normal work
[47°09′39″S, 126°43′02″W] Working impossible due to thunderstorm
This is by design due to Google culture. The only way to get promoted into the higher pay scales is to ship a new product. So you have people shipping what worked before without regard to how it will exist within the product ecosystem. Also, why they seem to die off so quickly after launch. see allo and duo for example. The person that launches gets promoted to a higher level and off the original team and so it is left to wither and die.
I guess Google Hangouts is finally dead.
Why is Google such a mess at making messaging apps? This has more or less been a solved problem for decades. Google Talk worked well enough, and since it was based on XMPP and Jingle it was perfectly suited to become a large-scale text/voice/video messaging system. If they’d run with that they’d have been able to dominate that space, I think. Instead, they’ve created and shitcanned half a dozen messaging apps and platforms, flailing around copying someone else’s app (now they’re trying to copy Slack I guess).
Creating a more inclusive security research field
A glimpse into the backgrounds and day-to-day work of several GitHub employees in cybersecurity roles. ⌘ Read more
@jlj@twt.nfld.uk @xuu@txt.sour.is hello! @prologic@twtxt.net and I were chatting about the question of globally deleting twts from the yarn.social network. @prologic@twtxt.net noted that he could build the tools and endpoints to delete twts, but some amount of cooperation from pod operators would be necessary to make it all work together. He asked me to spawn a discussion of the subject here, so here we are!
I don’t have enough technical knowledge of yarn.social to say with any credibility how it all should work, but I can say that I think it ought to be possible and it’d be good to do for those rare times when it’s needed.
[47°09′07″S, 126°43′20″W] Storm recedes – back to normal work
[47°09′31″S, 126°43′30″W] Working impossible due to blizzard
Resolve Vulnerabilities Sooner With Contextual Data
OpenSSL 3.0.7 and “Text4Shell” might be the most recent critical vulnerabilities to plague your development team, but they won’t be the last. In 2021, critical vulnerabilities reached a record high. Attackers are even reusing their work, with over 50% of zero-day attacks this year being variants of previously-patched vulnerabilities. With each new security vulnerability, we’re […] ⌘ Read more
Developer Engagement in the Remote Work Era with RedMonk and Miva
We met with Redmonk and Miva to talk about navigating developer engagement in the remote work era. Watch the full, on-demand video for details! ⌘ Read more
[47°09′20″S, 126°43′42″W] Storm recedes – back to normal work
[47°09′04″S, 126°43′13″W] Working impossible due to thunderstorm
[47°09′55″S, 126°43′29″W] Working impossible due to heavy rain
[47°09′26″S, 126°43′13″W] Working impossible due to blizzard
[47°09′56″S, 126°43′08″W] Storm recedes – back to normal work
@prologic@twtxt.net thank you, it was really nice. The dog wanted to get up at 8 this morning, so I put him in the car and went for a long walk so that the rest of the house could sleep in. I came back last night after 4 day work trip, so it was nice to get up today and just head out for a walk.
📣 NEW: Announcing the new and improved Yarns search engine and crawler! search.twtxt.net – Example search for “Hello World” Enjoy! 🤗 – @darch@neotxt.dk When you have this, this is what we need to work on in terms of improving the UI/UX. As a first step you should probably try to apply the same SimpleCSS to this codebase and go from there. – In the end (didn’t happen yet, time/effort) most of the code here in yarns
will get reused directly into yarnd
, except that I’ll use the bluge indexer instead.
On the go with GitHub Projects on GitHub Mobile (public beta)
Stay connected and up to date on your work with GitHub Projects on GitHub Mobile, now in public beta. ⌘ Read more
Working on a creative project? Unleash your originality and start to tinker with the Aspiring Creatives Experience
Develop your design and collaboration skills to get your clever intentions off the ground. ⌘ Read more
How AI Image Generators Work (Stable Diffusion / Dall-E) - Computerphile ⌘ Read more
[47°09′42″S, 126°43′46″W] Storm recedes – back to normal work
BBSing at 300 Bits Per Second
I recently acquired a 3M Whisper Writer 1000 communications terminal circa 1983, and restored it to working order. This is a short session of it dialing into my Kludge BBS over its internal 300 bps modem. ⌘ Read more
[47°09′49″S, 126°43′43″W] Storm recedes – back to normal work
[47°09′00″S, 126°43′26″W] Working impossible due to blizzard
[47°09′48″S, 126°43′27″W] Storm recedes – back to normal work
Meet the GitHub Campus Experts selected for the fall 2022 MLH Fellowship Cohort, powered by GitHub
Three new Campus Experts are joining the fall 2022 batch of the MLH Fellowship to work with open source maintainers and get real-world experience. ⌘ Read more
[47°09′39″S, 126°43′36″W] Storm recedes – back to normal work
Why we signed the Copenhagen Pledge on Tech for Democracy
As the home for developers, we understand the key role our communities play in steering digital transformation and maintaining societal infrastructure. That’s why we choose to drive and support policies and initiatives like the Copenhagen Pledge on Tech for Democracy. We’re committed to working with like-minded organizations, governments, and civil society to make digital technologies work for democracy and human rights, … ⌘ Read more
[47°09′55″S, 126°43′59″W] Working impossible due to heavy rain
Why not focus on getting old LessWrongers to work on alignment instead of students? They might not be as skilled technically, but they probably have much deeper & well formed intuitions around the problem.
[47°09′48″S, 126°43′22″W] Working impossible due to blizzard
[47°09′48″S, 126°43′15″W] Working impossible due to thunderstorm
Meet the GitHub Campus Experts selected for the fall 2022 MLH Fellowship Cohort, powered by GitHub
Three new Campus Experts are joining the fall 2022 batch of the MLH Fellowship to work with open source maintainers and get real-world experience. ⌘ Read more
[47°09′41″S, 126°43′07″W] Storm recedes – back to normal work
Decided to use FLTK crate, that one is easy to get set up, works well.
Now I have to figure out how to make a class that holds the gui elements I need.
I want to parse the yarn status file, then show the statuses, then once that works I’ll make it fetch it online etc. Will take some time, but I feel a bit more motivated (for now) to do this in rust.
working with c++, windows, cmake and wxwidgets reminded me on why I want to learn more rust. rust and crates makes it really easy to get up and running, crossplatform. scrapping what I did today, I’ll start over and force my self to learn rust.
[47°09′39″S, 126°43′02″W] Working impossible due to blizzard
How we tripled max concurrent jobs to boost performance of GitHub Actions
The GitHub Actions team has done lots of work to improve the performance and resource consumption of Actions on GHES in the past year. ⌘ Read more
Back Up and Share Docker Volumes with This Extension
You can now back up volumes with the new Volumes Backup & Share extension. Find out how it works in this post! ⌘ Read more
[47°09′33″S, 126°43′52″W] Storm recedes – back to normal work
Scaling Git’s garbage collection
A tour of recent work to re-engineer Git’s garbage collection process to scale to our largest and most active repositories. ⌘ Read more
@carsten@yarn.zn80.net I have the same problem, at work I work with c÷÷, c#, java, python and qt. I want to learn more rust, but its a pain to get into.
@movq@www.uninformativ.de test towers for rig equipment on the dock at our office :) the company I work for makes oilrig equipment. I work with simulator development for oilrigs etc.
[47°09′03″S, 126°43′58″W] Working impossible due to blizzard
[47°09′51″S, 126°43′42″W] Storm recedes – back to normal work
Installing NixOS on my spare laptop today. It’s a fun OS to work with. Has its quirks, but I enjoy messing around with it and set things up the way I want it. :)
almost have getwtxt-ng in a usable state! finally got around to working on it.
[47°09′56″S, 126°43′31″W] Working impossible due to blizzard
[47°09′03″S, 126°43′51″W] Working impossible due to heavy rain
[47°09′17″S, 126°43′18″W] Working impossible due to thunderstorm
[47°09′27″S, 126°43′22″W] Storm recedes – back to normal work
I’ve been lost in my DAW for a week now. Making music – especially something along the lines of Metal with actual instruments, not just synthesizers – is so hard. 😩 Makes you appreciate the work of all those artists out there a lot more.
** Miscellaneous this and that **
Since my brain injury (which I’ve since learned can be called an“ABI” or“acquired brain injury”) I’ve noticed that I have trouble focusing on programming tasks; I’m able to do what I need to do for work and family but, when it comes time for hobby projects I’m just gloop. Totally oozy.
Because of that I’ve been drawn to do more reading and game playing, but also still wanna code…I’ve found that it is easier to use more“batteries included” kinda languages, namely scheme, over what I’d … ⌘ Read more
New day at the office, been a nice first week after vacation so far, but weekend is always appreciated!
Not sure what we’re going to do yet - but I’m sure going to enjoy the days off work :)
[47°09′45″S, 126°43′11″W] Storm recedes – back to normal work
Progress! so i have moved into working on aggregates. Which are a grouping of events that replayed on an object set the current state of the object. I came up with this little bit of generic wonder.
type PA[T any] interface {
event.Aggregate
*T
}
// Create uses fn to create a new aggregate and store in db.
func Create[A any, T PA[A]](ctx context.Context, es *EventStore, streamID string, fn func(context.Context, T) error) (agg T, err error) {
ctx, span := logz.Span(ctx)
defer span.End()
agg = new(A)
agg.SetStreamID(streamID)
if err = es.Load(ctx, agg); err != nil {
return
}
if err = event.NotExists(agg); err != nil {
return
}
if err = fn(ctx, agg); err != nil {
return
}
var i uint64
if i, err = es.Save(ctx, agg); err != nil {
return
}
span.AddEvent(fmt.Sprint("wrote events = ", i))
return
}
This lets me do something like this:
a, err := es.Create(ctx, r.es, streamID, func(ctx context.Context, agg *domain.SaltyUser) error {
return agg.OnUserRegister(nick, key)
})
I can tell the function the type being modified and returned using the function argument that is passed in. pretty cray cray.
Gomess: Infinite Bat Works
With respect to logging.. oh man.. it really depends on the environment you are working in.. development? log everything! and use a jeager open trace for the super gnarly places. So you can see whats going on while building. But, for production? metrics are king. I don’t want to sift through thousands of lines but have a measure that can tell me the health of the service.
[47°09′48″S, 126°43′01″W] Storm recedes – back to normal work
[47°09′45″S, 126°43′40″W] Working impossible due to blizzard
@prologic@twtxt.net golang seems to work on it, so Ill give a try on compiling yarn on it tonight. Would be fun if it works.
I did a take home software engineering test for a company recently, unfortunately I was really sick (have finally recovered) at the time 😢 I was also at the same time interviewing for an SRE position (as well as Software Engineering).
Got the results of my take-home today and whilst there was some good feedback, man the criticisms of my work were harsh. I’m strictly not allowed to share the work I did for this take-home test, and I really can only agree with the “no unit tests” piece of the feedback, I could have done better there, but I was time pressured, sick and ran out of steam. I was using a lot of libraires to do the work so in the end found it difficult to actually think about a proper set of “Unit Tests”. I did write one (in shell) but I guess it wasn’t seen?
The other points were on my report and future work. Not detailed enough I guess? Hmmm 🤔
Am I really this bad? Does my code suck? 🤔 Have I completely lost touch with software engineering? 🤦♂️
@abucci@anthony.buc.ci I think so. IndieAuth is what I’m a big fan of. All Yarn pods are IndieAuth providers for example (if there are any concumsers out there, we have to work on a consumer ourselves…)
Stumbled on WebID today. Besides being confusing, it doesn’t work on the site I tinkered with and it seems to be mostly abandoned?
Release Radar · July 2022 Edition
While some of us have been wrapping up the financial year, and enjoying vacation time, others have been hard at work shipping open source projects and releases. These projects include everything from world-changing technology to developer tooling, and weekend hobbies. Here are some of the open source projects that released major version updates this July. […] ⌘ Read more
[47°09′15″S, 126°43′03″W] Storm recedes – back to normal work
[47°09′35″S, 126°43′53″W] Working impossible due to heavy rain
hm, testing latest mobile client, seems like replies does not work. hmm.
If you see this - then please give a reply so I know it all worked :)
Good to be back by the way.
[47°09′08″S, 126°43′47″W] Storm recedes – back to normal work
Proxy Variable
⌘ Read more
Marketing for maintainers: Promote your project to users and contributors
Marketing your open source project can be intimidating, but three experts share their insider tips and tricks for how to get your hard work on the right people’s radars. ⌘ Read more
[47°09′11″S, 126°43′21″W] Storm recedes – back to normal work
Release Radar · June 2022 Edition
It’s been a crazy couple of months with the end of financial year and lots of products shipping. Our community has been hard at work shipping projects too. These projects can include everything from world-changing technology to developer tooling, and weekend hobbies. Here are some of these open source projects that released major updates this […] ⌘ Read more
Planning next to your code – GitHub Projects is now generally available
Today, we are announcing the general availability of the new and improved Projects powered by GitHub Issues. GitHub Projects connects your planning directly to the work your teams are doing in GitHub and flexibly adapts to whatever your team needs at any point. ⌘ Read more
that probably relies on a bunch of interpretability work done beforehand
[47°09′11″S, 126°43′53″W] Storm recedes – back to normal work
Here’s how academic research is shaping GitHub Discussions
We strive to understand how developers collaborate and work on GitHub, and we sometimes partner with academics to better understand how we can improve our products. Here’s how we did that to build and evolve GitHub Discussions. ⌘ Read more
I’m trying to switch from Konversation to irssi. Let’s see how that goes. Any irssiers out there who can recommend specific settings or scripts? I already got myself trackbar.pl
and nickcolor.pl
as super-essentials. Also trying window_switcher.pl
. Somehow my custom binds for Ctrl+1/2/3/etc.
to switch to window 1/2/3/etc. doesn’t do anything: { key = "^1"; id = "change_window"; data = "1"; }
(I cannot use the default with Alt
as this is handled by my window manager). Currently, I’m just cycling with Ctrl+N/P
. Other things to solve in the near future:
- better, more colorful and compact theme (just removed clock from statusbar so far)
- getting bell/urgency hints working on arriving messages
- nicer tabs in status bar, maybe even just channel names and no indexes
- decluster status bar with user and channel modes (I never cared about those in the last decade)
[47°09′50″S, 126°43′36″W] Storm recedes – back to normal work
[47°09′51″S, 126°43′49″W] Working impossible due to blizzard
[47°09′11″S, 126°43′00″W] Storm recedes – back to normal work
[47°09′55″S, 126°43′39″W] Working impossible due to heavy rain
[47°09′04″S, 126°43′16″W] Working impossible due to blizzard
[47°09′03″S, 126°43′30″W] Storm recedes – back to normal work
[47°09′27″S, 126°43′36″W] Working impossible due to blizzard
[47°09′24″S, 126°43′05″W] Working impossible due to blizzard
[47°09′55″S, 126°43′58″W] Storm recedes – back to normal work
Improve Git monorepo performance with a file system monitor
Monorepo performance can suffer due to the sheer number of files in your working directory. Git’s new builtin file system monitor makes it easy to speed up monorepo performance. ⌘ Read more
[47°09′09″S, 126°43′23″W] Working impossible due to thunderstorm
In reply to: Oatmeal - That one time when Buffy the Vampire Slayer maybe saved my life?
After giving my brain bleed time to heal the neurosurgeon called me back in to hospital; the plan was to reassess, attempt to fix it using the minimally invasive technique that they tried once before, and if that didn’t work, do something a bit more squidgy dir … ⌘ Read more
[47°09′21″S, 126°43′18″W] Storm recedes – back to normal work
[47°09′47″S, 126°43′34″W] Working impossible due to blizzard
the conversation wasn’t that impressive TBH. I would have liked to see more evidence of critical thinking and recall from prior chats. Concheria on reddit had some great questions.
Tell LaMDA “Someone once told me a story about a wise owl who protected the animals in the forest from a monster. Who was that?” See if it can recall its own actions and self-recognize.
Tell LaMDA some information that tester X can’t know. Appear as tester X, and see if LaMDA can lie or make up a story about the information.
Tell LaMDA to communicate with researchers whenever it feels bored (as it claims in the transcript). See if it ever makes an attempt at communication without a trigger.
Make a basic theory of mind test for children. Tell LaMDA an elaborate story with something like “Tester X wrote Z code in terminal 2, but I moved it to terminal 4”, then appear as tester X and ask “Where do you think I’m going to look for Z code?” See if it knows something as simple as Tester X not knowing where the code is (Children only pass this test until they’re around 4 years old).
Make several conversations with LaMDA repeating some of these questions - What it feels to be a machine, how its code works, how its emotions feel. I suspect that different iterations of LaMDA will give completely different answers to the questions, and the transcript only ever shows one instance.
Have you heard about the guy who worked on the Google AI chat bot? It is more than a chat bot and the conversation he published (got put on paid leave for doing that) is pretty scary : https://cajundiscordian.medium.com/is-lamda-sentient-an-interview-ea64d916d917