KeepingYouAwake VS maestral

KeepingYouAwake. Prevents your Mac from going to sleep.

Hi, I have been using slack on my company provided mac and I have installed https://keepingyouawake.app/ to keep my macbook awake indefinitely. When I keep the slack application open for so many hours, I can still see the green dot on slack and it has never marked me as 'away'. So, I'm wondering if others can see me as 'online' if the green bubble is showing up on my slack application for so many hours?

I use this app, KeepingYouAwake works perfect for when I am trying to seed my torrents with a locked screen

FWIW, you might want to give the excellent and open-source alternative https://keepingyouawake.app/ a try.

I like https://github.com/newmarcel/KeepingYouAwake for prevent sleeping mac

As for the M1 "server" always going to sleep, I installed: https://github.com/newmarcel/KeepingYouAwake

Do people really not know about caffeine indicator, KeepingYouAwake or caffeine for windows ?

maestral is an open source Mac/Linux client. Just one example, I’m sure there are others.

Worth mention the open source project Maestral: https://github.com/SamSchott/maestral

(an unofficial Dropbox client)

Sometime late last fall, my NAS rebooted and my ZFS pools didn't come back online automatically, but Docker did automatically restart the Maestral client. In so doing, it detected an empty folder...and...promptly deleted EVERYTHING in my Dropbox, assuming I'd just deleted everything locally. It's an issue that has had at least a few bug reports and which as of yet still hasn't been addressed - basically, the client needs but does not have a way to say "a bunch of stuff is changing, are you sure?" before doing it - especially on a restart of the client.

>- Debug apps which don't opt into debugging, using gdb/lldb, without disabling SIP. It's my computer, I should be root, I should be able to introspect how processes execute on it. Not being able to do so prevented me from debugging https://github.com/samschott/maestral/issues/597, since I had to disable SIP, which required rebooting, which stopped the bug from happening.

Another option is to re-sign the application with the entitlements necessary for debugging.

e.g:

https://gist.github.com/talaviram/1f21e141a137744c89e81b58f7...

there is a native build as beta, but I found Maestral much better :) https://github.com/samschott/maestral

3) No support for extended file attributes (so you cannot sync .app bundles)

[1] https://github.com/SamSchott/maestral/issues/443

If you still haven't found a use for them: they make for good low-power, always-on, headless networked servers for processing-light tasks.

Other commentators mentioned pihole/DNS, WireGuard, and music streaming, but you can also use them for a (slow) NFS server, persistent Syncthing node, Maestral host[1] (third-party Dropbox client written in Python (that can actually run on the Raspberry Pi, unlike the official Dropbox client)), or device that maintains a connection to a distributed network (e.g. Hyporborea/cjdns).

[1] https://github.com/SamSchott/maestral

I'd been reading up on Linux for the last little bit, learning about different distros and what things to look out for - so when this thing arrived I jumped onto the latest Fedora release & am really enjoying it. I've tweaked some Gnome extensions, gotten my favorite writing app downloaded, set up the awesome Maestral open-source Dropbox client, and set up a decent little undervolt using intel-undervolt, mprime, cinebench, and glmark2 :)

Open-source Dropbox client, with multi-account, no-device-limit and M1 support\ (147 comments)