Some shells provide ways to prevent some commands to be added to the history
Some shells provide ways to prevent some commands to be added to the history
They are right 🤣
More than a decade ago I bought SUSE enterprise for a couple of years just to support the project. Never needed any assistance so I’m not sure about a different experience. BTW The box was nice 🤣
I’m not sure about the “audiobooks” part but you can use your browser from android to connect to calibre https://manual.calibre-ebook.com/faq.html#over-the-air
BTW I used for many years Moon+ Reader to read aloud my ebook on android. Not quite as a real audiobook but good enough https://play.google.com/store/apps/details?id=com.flyersoft.moonreader
If you are able to see every recipe I’d rule out data corruption. If the issue arise only when try to create a new recipe (or editing an old one) the usual thing to check are permissions. Don’t zip but use some tools to maintain permissions (tar, rsync, etc) and try again
I’m an avid Obsidian user but I didn’t know about Matcha. It’s really cool
I want to jockely answer: curl
but there are seriously good cli rss readers out there:
If you want a way to self host git (not github) repositories you can check this list https://www.slant.co/topics/1440/~best-self-hosted-web-based-git-repository-managers
It wasn’t meant to be a correction … I just learned about this project so I’d just want to know more
Are you sure about Paaster supporting Markdonw? I only see syntax highlighting https://paaster.io/GtlseaIIhqtfcsZV1C8sS#BgT9miwSaeKzMLQ-Ch6d3KZlgfCmIR32dpYr06HXYTw
I just copy&pasted their README in chatgpt asking for a comparison (so there may be allucinations)
Both PrivateBin and Paaster are “pastebin” tools that allow users to share snippets of text or code online. Both emphasize privacy and security, encrypting data at the local level in the user’s browser before sending it to the server. However, there are several key differences between the two services:
Design and User Interface: While PrivateBin self-identifies as a minimalist pastebin, Paaster seems to put an emphasis on user experience, offering features like file drag & drop and a paste history.
Features: Both offer basic features like password protection and the option to delete data after reading, but PrivateBin also offers features like the ability to have anonymous or nicknamed discussions, Markdown formatting support, code syntax highlighting, and the ability to upload files. On the other hand, Paaster offers a paste history feature, PWA support, and i18n.
Trust: PrivateBin warns users not to blindly trust the server administrator, whereas Paaster advises users to either host their service or use a trusted hosting service.
Implementation and Maintenance: Paaster seems more developer-oriented, with API documentation, a CLI tool, and support for Vercel and Docker. PrivateBin, however, also has a developer and installation guide.
Hosting Options: Paaster seems more geared towards self-hosting, with detailed instructions for use with Docker and options for use with external storage services like Amazon S3 and Google Cloud Storage. PrivateBin does not provide specific hosting details in the provided text.
Security: Both use end-to-end encryption, but they use different encryption algorithms. Paaster uses XChaCha20-Poly1305, while PrivateBin uses 256-bit AES in Galois Counter mode.
These are just some of the key differences between the two services. Both have their strengths and unique points, and the choice between the two will depend on the specific needs of the user or organization.
I’m incline to say that there’s no way. I order to have secure payments you have to secure each and every step of the process. Without a big corporation under those steps no one in his right mind will gamble with payments
I’d like to check grocy because it looks really promising even if a bit overkill if you want only a cookbook.
I do exactly the same. It’s not foolproof but it’s better than nothing. I remember, almost a decade ago, when I discovered that
rm
on mac didn’t accept flags as last arguments… I hope they changed that behavior