Glimpse
litestream
Glimpse | litestream | |
---|---|---|
20 | 165 | |
1,151 | 9,997 | |
- | - | |
7.5 | 7.5 | |
almost 3 years ago | 12 days ago | |
C | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Glimpse
- GIMP's 2022 Annual Report
-
BREAKING NEWS!
glimpse fork have already died :`( https://github.com/glimpse-editor/Glimpse/wiki/Development-Priorities
-
LibSQL is an open source, open contribution fork of SQLite
Remember the fork of GIMP because people were offended by the name?
https://github.com/glimpse-editor/Glimpse
https://glimpse-editor.org/posts/a-project-on-hiatus/
-
Gimp development release 2.99.12 includes initial CMYK support
> What if the name of the software was CripplePhoto
Argumentum ad absurdum.
> I mean, no professional uses Gimp for photo editing
Perhaps because the lack of CMYK, the limited architecture for plugin, or the outdated UI have more to do than the name?
If the name was the real bottleneck for adoption, you can be sure that you'd see someone creating a fork with different branding and being widely successful. Oh, wait. It has been tried already! [0]
[0] https://github.com/glimpse-editor/Glimpse
- OBS and Streamlabs Commit to Long-Term Collaboration
-
when your mum calls you by your full name
There is a bunch of folks who forked Gimp because they find the name offensive. Since they still have to refer to it they use euphemisms (such a "upstream") or call it "GNU Imp".
-
I REALLY want to create TakaMori fanart and post it here.
Glimps is a good one. It has pressure sensitivity support for drawing tablets. If you want something closer to Illustrator, Inkscape is your best shot.
-
Windows, A Consumer Product.
They're named by committee. No committee would have come up with "GIMP" (also forked as "Glimpse").
-
Founder of Adobe and developer of PDFs dies at age 81
I've been enjoying the Glimpse fork a lot more these days.
-
The amazing Grant Sanderson (3Blue1Brown) demonstrates seam carving in Julia.
(cc u/krapht) check out glimpse! it’s a fork of GIMP that’s a bit more modern. also an nx version coming soon which will be geared toward beginners
litestream
-
Ask HN: SQLite in Production?
I have not, but I keep meaning to collate everything I've learned into a set of useful defaults just to remind myself what settings I should be enabling and why.
Regarding Litestream, I learned pretty much all I know from their documentation: https://litestream.io/
-
How (and why) to run SQLite in production
This presentation is focused on the use-case of vertically scaling a single server and driving everything through that app server, which is running SQLite embedded within your application process.
This is the sweet-spot for SQLite applications, but there have been explorations and advances to running SQLite across a network of app servers. LiteFS (https://fly.io/docs/litefs/), the sibling to Litestream for backups (https://litestream.io), is aimed at precisely this use-case. Similarly, Turso (https://turso.tech) is a new-ish managed database company for running SQLite in a more traditional client-server distribution.
-
SQLite3 Replication: A Wizard's Guide🧙🏽
This post intends to help you setup replication for SQLite using Litestream.
-
Ask HN: Time travel" into a SQLite database using the WAL files?
I've been messing around with litestream. It is so cool. And, I either found a bug in the -timestamp switch or don't understand it correctly.
What I want to do is time travel into my sqlite database. I'm trying to do some forensics on why my web service returned the wrong data during a production event. Unfortunately, after the event, someone deleted records from the database and I'm unsure what the data looked like and am having trouble recreating the production issue.
Litestream has this great switch: -timestamp. If you use it (AFAICT) you can time travel into your database and go back to the database state at that moment. However, it does not seem to work as I expect it to:
https://github.com/benbjohnson/litestream/issues/564
I have the entirety of the sqlite database from the production event as well. Is there a way I could cycle through the WAL files and restore the database to the point in time before the records I need were deleted?
Will someone take sqlite and compile it into the browser using WASM so I can drag a sqlite database and WAL files into it and then using a timeline slider see all the states of the database over time? :)
-
Ask HN: Are you using SQLite and Litestream in production?
We're using SQLite in production very heavily with millions of databases and fairly high operations throughput.
But we did run into some scariness around trying to use Litestream that put me off it for the time being. Litestream is really cool but it is also very much a cool hack and the risk of database corruption issues feels very real.
The scariness I ran into was related to this issue https://github.com/benbjohnson/litestream/issues/510
-
Pocketbase: Open-source back end in 1 file
Litestream is a library that allows you to easily create backups. You can probably just do analytic queries on the backup data and reduce load on your server.
https://litestream.io/
- Litestream – Disaster recovery and continuous replication for SQLite
- Litestream: Replicated SQLite with no main and little cost
-
Why you should probably be using SQLite
One possible strategy is to have one directory/file per customer which is one SQLite file. But then as the user logs in, you have to look up first what database they should be connected to.
OR somehow derive it from the user ID/username. Keeping all the customer databases in a single directory/disk and then constantly "lite streaming" to S3.
Because each user is isolated, they'll be writing to their own database. But migrations would be a pain. They will have to be rolled out to each database separately.
One upside is, you can give users the ability to take their data with them, any time. It is just a single file.
[0]. https://litestream.io/
-
Monitor your Websites and Apps using Uptime Kuma
Upstream Kuma uses a local SQLite database to store account data, configuration for services to monitor, notification settings, and more. To make sure that our data is available across redeploys, we will bundle Uptime Kuma with Litestream, a project that implements streaming replication for SQLite databases to a remote object storage provider. Effectively, this allows us to treat the local SQLite database as if it were securely stored in a remote database.
What are some alternatives?
PhotoGIMP - A Patch for GIMP 2.10+ for Photoshop Users
rqlite - The lightweight, distributed relational database built on SQLite.
photoshopCClinux - Photoshop CC v19 installer for Gnu/Linux
pocketbase - Open Source realtime backend in 1 file
caire - Content aware image resize library
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
gimp-python-development - Some ideas and tools to develop Python 3.8 plugins for GIMP 2.99.4
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
winapps - Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration.
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
photopea - Photopea is online image editor
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines