iBelieve

Max accounts get 15 daily runs included, any runs above that will get billed as extra usage.

Looks like I'm limited to only 3 cloud scheduled tasks. And I'm on the Max 20x plan, too :(

"Your plan gets 3 daily cloud scheduled sessions. Disable or delete an existing schedule to continue."

But otherwise, this looks really cool. I've tried using local scheduled tasks in both Claude Code Desktop and the Codex desktop app, and very quickly got annoyed with permissions prompts, so it'll be nice to be able to run scheduled tasks in the cloud sandbox.

Here are the three tasks I'll be trying:

Every Monday morning: Run `pnpm audit` and research any security issues to see if they might affect our project. Run `pnpm outdated` and research into any packages with minor or major upgrades available. Also research if packages have been abandoned or haven't been updated in a long time, and see if there are new alternatives that are recommended instead. Put together a brief report highlighting your findings and recommendations.

Every weekday morning: Take at Sentry errors, logs, and metrics for the past few days. See if there's any new issues that have popped up, and investigate them. Take a look at logs and metrics, and see if anything seems out of the ordinary, and investigate as appropriate. Put together a report summarizing any findings.

Every weekday morning: Please look at the commits on the `develop` branch from the previous day, look carefully at each commit, and see if there are any newly introduced bugs, sloppy code, missed functionality, poor security, missing documentation, etc. If a commit references GitHub issues, look up the issue, and review the issue to see if the commit correctly implements the ticket (fully or partially). Also do a sweep through the codebase, looking for low-hanging fruit that might be good tasks to recommend delegating to an AI agent: obvious bugs, poor or incorrect documentation, TODO comments, messy code, small improvements, etc.

I ran all of these as one-off tasks just now, and they put together useful reports; it'll be nice getting these on a daily/weekly basis. Claude Code has a Sentry connector that works in their cloud/web environment. That's cool; it accurately identified an issue I've been working on this week.

I might eventually try having these tasks open issues or even automatically address issues and open PRs, but we'll start with just reports for now.

I've been working on a toy Lispy language and self-hosting compiler that targets JS. My goal is to explore building a full-stack web framework with a template compiler similar to Svelte that runs minimal JS on the frontend.

https://github.com/iBelieve/knight

The Bible.

Mysterious Island (1874), Around the World in Eighty Days (1873), and other books by Jules Verne.

Books by James Fenimore Cooper.

The Sea-Wolf (1904) by Jack London.

The Count of Monte Cristo (1844) by Alexandre Dumas.

Oliver Twist (1839) by Charles Dickens.

Yes, unfortunately reqwest pulls in lots of dependencies, but I think you should be able to get a binary under 10MB if you compile in release mode using the --release flag.

Same here, Firefox 66 on Arch Linux.

What couchand said still applies to 1.0. So this should work:

    use actix_web::{web, App, HttpServer, HttpRequest, Responder};

   fn index(req: HttpRequest, info: web::Path<(u32, String)>) -> impl Responder {
       format!("[{}] Hello {}! id:{}", req.method(), info.1, info.0)
   }

Great to see actix-web reach 1.0. I've played with Rocket in the past and liked it, but ended up choosing actix-web recently for a production project because I don't want to rely on a nightly compiler for a production project. I'm only using actix-web in a small portion of a larger Rust project, but so far my experience with it has been quite pleasant.

For anyone looking for a hosted solution, https://surge.sh/ is super nice and simple without any of the complexity of managing the stack yourself. Deploying uses one simple command, and you get hosting and custom domains for free, though I believe SSL is paid for custom domains. (I'm not affiliated with Surge at all, just a happy user.)

Looks like the last item in the all-files array is an empty string - maybe that's why? Either that, or the current directory (".") might be included as the first element.

It appears to be running under the Android emulation layer:

Because Chrome OS runs Android apps, targeting Android is the way to build Chrome OS apps.

This looks great! I've been using Yoga in my Rust UI framework via the yoga-rs bindings, and this looks like a nice pure-rust alternative to try using instead.

This is great to see. I started my own org-mode library for Rust at the end of last year (https://github.com/iBelieve/orgmode-rs), with the goal of building a desktop or web app for org-mode, but haven't had much time to work on it.

With microservices, if you make a mistake and take part of your application down, aren't you worse off because only part of your application is running and is now in an undefined state?

My preferred format for getting newsletters, blog posts, and other news is RSS. I use Feedly along with Reeder on macOS.

I used to run Linux quite well on a 2013 MacBook Pro, then I got a new 2016 MacBook Pro through work, and ran into tons of issues and finally gave up running Linux on it and just use Linux on my home-built desktop. Issues included the keyboard not working out of the box, suspend not working quite right, issues with the dedicated+integrated GPUs, etc. I don't know the current state of Linux on recent MacBooks, but here are the two GitHub repos I had used: https://github.com/Dunedan/mbp-2016-linux and https://gist.github.com/roadrunner2/1289542a748d9a104e7baec6...

Yes - QtQuick Controls 2. It is discussed in the book at https://qmlbook.github.io/ch06-controls/controls.html and has official documentation at https://doc.qt.io/qt-5/qtquickcontrols-index.html

I came across this project on the Rust subreddit: https://www.reddit.com/r/rust/comments/7iu7q8/plato_a_docume....

It's neat the Kobos have a removable microSD card and run Linux and can be easily hacked/customized.

You might be thinking of https://gettogether.community/ (https://github.com/GetTogetherComm/GetTogether)

I can understand the 15% complaining that you haven't released the source yet - your website very clearly calls this an "open source mobile phone". Something can't be open source if the code hasn't been released yet under an open source license. It might be open source in the future, but it isn't yet, in direct contrast to multiple claims on your website.

In the FAQ, under the Technical section it says:

Q: Where can I download the code?

Probably Github. After we ship the rewards.

So, unfortunately, it looks like it'll only be open-sourced after it ships.

If you're a theist who believes in a "god", sure, you can believe whatever you want, including that god won't punish anyone.

But for Christians, we are convinced that the Bible is true based on evidence and reason, and therefore can only believe what it teaches. For Christians, the answer is simple: everyone has sinned, God is just, and must punish sin. Lack of knowledge of God is no excuse, for everyone knows that God exists and everyone has rejected Him. No one deserves to go heaven; no one can get to heaven by anything they do. The only way to heaven is through Jesus, by trusting in Him as our only hope of forgiveness and salvation.

That is why we must go to the ends of the earth, from the largest cities to the most remote islands, to share Christianity with everyone we meet, often giving our lives to spread that message.

If you were convinced that something is true and that it has eternal consequences for those who reject or don't hear that message, how could you _not_ want to tell everyone about it, going to the ends of the earth and risking life itself so others could hear that message?

I've seen it happen at least once in the few years that I've been on Hacker News, see https://news.ycombinator.com/item?id=17228704

The way I do this in Rust is `Some(...).filter(...)`. I personally like this over having generic extensions, as it makes it very clear that its doing filtering that produces an optional, rather than filtering through a list or other iterable.

I hate trying to guess whether a newline is enter, shift+enter, option+enter, ctrl+enter, or cmd+enter.

I'm curious, are you (or anyone else using Org Mode) using a single org file for your entire personal wiki, or one file per major topic? In the past, I've used Markdown files with one file per language/topic for my personal developer wiki, but am looking at moving it to Org Mode now. One file for everything (developer knowledge + other subjects) seems nice, but it seems like trying to manage and navigate around a single large file would get messy.

I'm currently using Yocto for an embedded Linux project, and agree that it just feels so overly complicated for what we're using it for. I've written packages for Arch Linux in the past, and that's a breeze compared to writing bitbake recipes.

The ability to modify existing recipes through append files is nice, but that seems like it could be handled in a normal distro just by forking a package and making changes.

The outer border and shadow appears to be from the default window decorations, which I expect they'll remove in some non-app-specific method. The top bar is the standard window headerbar, which they'll probably remove as well, at least for the dialer screen. The gradients are part of the default GTK theme. Not sure about the button labels, as it's been a while since I touched GTK development - there may not be an easy way to add labels under an image in a button.

EDIT: designs almost always look nicer than the first pass at implementing them, as designers can put pixels wherever they want to make things look pretty, while developers are constrained by the technical restrictions of the frameworks being used.

One reason would be to use non-Mac hardware and Windows or Linux as your primary OS, but still have access to macOS for the times that you need it, for example to do iOS development. I do some iOS development and primarily use a Dell XPS 13 with Linux on it, and have to switch computers any time I need to work on an iOS project.

And specifically about the Mac hardware - I agree MacBooks are the best available, especially the touchpads. But Linux doesn't really support my 2016 MacBook Pro, so I have to use the XPS to run Linux.