OldCoder

There's a lot to say. Code. Careers. Purpose. Pack behavior. What's real and what's pretend. There is too much pretend.

Last Notes

2026-04-24 05:30:05 UTC

- reply

I have a Motorola Edge Plus 2024 running Lineage OS 23, comparable to Android 16, omitting everything from Google except for Maps, and I continue to get 2 to 3 days despite the age of the phone.
Commercial Androids fall well below the lean Android forks on battery life. Third party bloatware and the Google components are battery vampires.
People will point out that if you replace the Android that comes with your phone, you might brick the phone and you'll void your warranty and lose support regardless.
The first point is true, but regarding the second, note that Motorola has had a very limited support period for the phone that I have and I've already taken the phone past the maximum Android level that it was expected to support. So, support isn't really an issue.
If a phone comes with Graphene OS pre-installed, of course, those last points aren't issues. It should be noted that Graphene OS is more secure then Lineage OS but at the same time is limited to Pixel hardware.

2026-03-17 04:00:10 UTC

- reply

: I had no difficulty in building #GIMP 3.2.0 for my Linux distro. Additionally, in theory, my distro can [and ultimately will] include both GIMP 2.10 and GIMP 3.2 or above.
@npub140g…24hf : You're free to say whee for G'MIC three seven three in GIMP three. The illustration, see: This is #GMIC 3.7.3 and #GIMP3 3.2.0 running in Laclin [the 17th wonder of the world into which all that is fast and light is unfurled.] I did need to patch G'MIC, in my distro, to fix a FTBFS related to "gimptool" release detection.
@npub1jxd…txs3 : However, one issue that upstream isn't responsible for is unavoidable: The fact that most SCM scripts aren't expected to work in GIMP 3 for some time.
FX-Foundry seems to be one example. In fact, FX-Foundry has been partly ported to GIMP 2.8 but I gather that it hasn't made it to 2.10 yet. I see that one reviewer is holding off on an update to GIMP 3 specifically for this reason.
If it will help, I can get FX-Foundry, or most of it, to GIMP 2.10. I should have a draft set ready this Spring. The draft set will support, I think, about 85% of the scripts.
If there is an automated tool under development that will take scripts from GIMP 2.10 to 3.2 or above, this would be one way to get FX-Foundry into the new series.
FWIW: My new script set, to be named OC-Foundry, will include updated copies of other sets such as the GimpHelp set [as the latter website seems to have shut down].
To reduce confusion due to overlap with work by other developers -- and to ensure that authors receive credit -- most menu lines in OC-Foundry will indicate the original associated websites and/or authors.
@npub1kdt…ce4r : BTW yes. G'MIC s'exécute dans GIMP, comme le montre la capture d'écran ci-jointe.
I'd like to close with a GIMP build tip:
I presently recommend that distro developers build "libmypaint" 1.6.1 exactly, then "mypaint-brushes" 1.3.0 exactly, and finally "my-paint-brushes" git-current. git commit 08da4a48a should work for the latter package. The three "*mypaint*" packages should be configured and installed using the same prefix.
The preceding steps should permit developers to build and run both GIMP 2.10.38 and 3.2.0 on the same box. Note: The two GIMP packages need to be configured and installed using *different* prefixes.
https://dansu.org/media/04f6305d-61aa-4ad0-847e-799a816fdfd5/260316-gimp-gmic.jpg

2025-08-22 11:47:37 UTC

- reply

#gmic 3.6.0 is out. I thought I'd mention that the G'MIC speech bubble feature, which is new in 3.6.0, is confirmed to work in both #GIMP 2.10 and 3.0. This opens up new options for #webcomics creators.
Illustration: Use of G'MIC 3.6.0 speech bubble in GIMP 2.10.
https://dansu.org/media/b1f20a6c-82a5-4a39-b534-d2a2cce0e8ca/250822-bubble.jpg

2025-06-21 02:24:42 UTC

- reply

has commented as follows:
"We've heard your feedback on the Terms of Service updates for mastodon.social and mastodon.online, and we're pausing the implementation date (previously announced to users via email as 1st July 2025) so we can take further advice and make improvements."

2025-06-19 05:25:17 UTC

- reply

Mr. Doctorow:
I see in the Github issue that, moving forward, the new language will be the default based on its inclusion in the Mastodon #ToS templates. This isn't ideal.
If #Pleroma is better in this regard, one option would be to encourage the adoption of Pleroma and its forks. Pleroma is much lighter anyway. FWIW: I've run my own Pleroma instance for 4 years and this is being posted from it.
However, realistically, Mastodon is likely to remain a dominant force in the Fediverse. The ToS issue is therefore significant.
I have nothing against the Mastodon core group's likely desire to be bought out for $1B due in part to its creation of "birdsites" that own piles of content. But the Fediverse might well be one of the few things that is still standing between the boot and the human face in "1984".
You're a "name" that's associated with rights. If you do the following, it might gain some traction. Work with your circle to set up a light automated fork of Mastodon. The fork could also be thought of as a spoon.
The fork or spoon would be identical to upstream except for changes made by automation scripts. Such as replacement of the ToS templates with versions that your group would select. It would be a simple matter.
Forks usually die quickly. However, there's little to prevent semi-automated spoons from lasting indefinitely. Sometimes, too, forks end up with both superior features and momentum. See: angie, a full fork of nginx.
Mastodon gGmbH has trademarked the term "Mastodon" as a software mark. However, a spoon could certainly refer to itself as Mastodon (tm) compatible. If "Xnet" isn't trademarked, that term could be trademarked and used as the repo name. Or perhaps "Little Brother" would work.
One nice thing about the spoon approach, aside from the fact that it might be relatively low effort, is that other people would have different concerns about Mastodon that could be addressed at the same time as the stated issue.
Creative Commons people would, for example, like to see increased promotion of Creative Commons in the default Mastodon setup.
So, you might be able to assemble a group of 5 to 10 people. That would be more than enough. Or the prospect of a spoon might offer some leverage in discussions with @Gargron.
Illustration: A #Mastodon is facing a fork by somebody who has a better known name than he does. The Mastodon reconsiders his position on intellectual property issues.
The illustration is partly LLM, though I have concerns related to LLM, and partly GIMP.
https://dansu.org/media/284f99c9-7ed9-4025-9580-3c38c1b099c1/mastofork.jpg

2025-04-05 01:39:57 UTC

- reply

In theory, yes. GIMP-3 builds with the 'C' version of librsvg. In practice, I observe an "unknown error" [ or similar wording ] when I use the resulting copy of GIMP-3 to open SVG files. If I'm able to learn something more specific, I'll report it.

2025-04-04 10:14:43 UTC

- reply

I've built GIMP-3 from source. It's nice. My #Linux distro will keep GIMP-2 and feature GIMP-3 as well. I'll comment that, for me, two features are missing from GIMP-3:
SVG support requires Rust now. Rust is a huge dependency to need to add just to get SVG. Additionally, Rust isn't available for some distros and/or architectures. So, for me, GIMP-3 will need to omit SVG. I think that some other distros will make the same decision.
The Create Logo command is gone as well.
Comment to @npub1jxd…txs3 : It shouldn't be difficult for "file-svg.c" to support the 'C' version of librsvg. In fact, the code is already there in an "#else" block. It looks like relatively minor changes are needed. However, I haven't been able to make it work yet.
On the other hand, Resynthesizer and #GMIC both build and work. The base GIMP-3 filters plus those two add-ons are most of what I need.
Note to distro admins: To build Resynthesizer for GIMP-3 from source, you presently need to use the "resynthesizer3" git branch.
@npub140g…24hf may be pleased to hear that GIMP 3.0.2 and GMIC 3.5.3 are confirmed to be simpatico. See the attached screenshot.
Note: The distro and desktop used here are my own 30-year-old project, Laclin. I'm as fond of it as the GIMP and GMIC teams are of their projects.
#FOSS #graphics
https://dansu.org/media/8e4fdc9d-ea1b-4d8f-8490-ad8c9fcb2796/gimp30-250404.jpg