5 Followers
173 Following
167 Posts
Svg, No
@mykolak @kde have you tried Zim Desktop Wiki? Its an excellent note-taking app , with very easy crosslinking to other pages , attached documents or external files. Unfortunately Zim doesn't really have any mobile support
@revk @jwildeboer As I age my memory ain't what it used to be, but on the plus side I can now count grey hairs to verify I am indeed above 18 🥲
@Chaos_99 multiple simpler sketches tends to work better than a few complicated sketches. Makes it easier to find those frustrating invisible non-closed sections.
It's a good idea to have a main sketch with only key-dimensions but no extruded geometry, and use for defining other sketches.
@rasos @eurostack They both do link to eachother though, so it seems above-board

You prob know this already, but if you duck-search, you can go to a slightly different entry point at https://noai.duckduckgo.com to do web searches without AI slop dumping on you.

I see they've dressed up the landing page there! Now more obviously non-AI. I mean, it's a selling feature, so yeah, go to town guys.

(if you still google things, consider the duck search! it's worked well for me for years, and the non-ai version is a nice step forward).

#InternetSearch #degoogle #websearch

Update: Within hours after a #Reuters journalist got in touch with Apple, the Apple team got back to us.

Good news: You will soon be able to select #Tuta Mail as your default email app on #iOS.

Bad news: #Apple will get away with ignoring our request for weeks without any consequence.

https://mastodon.social/@Tutanota/114273074547354681

@MostlyHarmless @caseynewton easier said than done unfortunately.

AI scrapers have been found to both lie about their user agent and scrape from distributed IPs to avoid throttling. Also they ignore robots.txt. Solutions like Anubis would work, but that also blocks "legitimate" scrapers like search engine crawlers.

Niccolo from KDE wrote a great article about their efforts to combat rising costs from AI scrapers: https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/

FOSS infrastructure is under attack by AI companies

LLM scrapers are taking down FOSS projects' infrastructure, and it's getting worse.

LibreNews
North Sea tanker: Crew member missing and vessels still on fire after collision in North Sea

Thirty-six people have been brought ashore after a cargo vessel hit an oil tanker off the East Yorkshire coast.

BBC News
GitHub - Akylas/OSS-DocumentScanner: Document scanning app

Document scanning app . Contribute to Akylas/OSS-DocumentScanner development by creating an account on GitHub.

GitHub

I have some advice on doing this. This is coming from my experience with creating an ansible role to fully setup a plasma desktop with all of my preferred configurations on a fresh computer from scratch: You can find the repo here for reference: github.com/alyxxy-net/ansible-role-alyxxy-kde

For context, this is coming out of a process of trying to minimize the amount of files to keep track of and creating a minimal base config that is easy to apply on any device, so it might not cover all of your needs if you have a more complex setup. It has also just been updated and tested for plasma 6 on Debian testing:

Enough context, here are the files that I have found important to backup and what they do:

~/.config/dolphinrc Contains the settings for the dolphin file manager

~/.config/kdeglobals Contains settings for color scheme, icon theme, and widget style, maybe other appearance settings as well if you aren’t using a default theme

~/.config/kglobalshortcutsrc Contains all of the keyboard shortcut/hotkey settings

~/.config/khotkeysrc This file is a bit harder to parse, but it looks like it covers custom user created shortcuts and well as a bunch of other stuff including gestures. I definitely plan to dig into this more, but I will admit that I don’t have the best understanding of this config file XD

~/.config/klaunchrc Covers application launch feedback, this is where I have the bouncing icons turned off

~/.config/kscreenlockerrc Contains settings for screen timeout and locking

~/.config/ksmserverrc Contains session settings, this is where I have the setting to login with a fresh setting instead of trying to restore an old one

~/.config/kwinrc Contains the virtual desktop settings (how many are defined and what layout they are in) as well as plugins/effects that enabled or disabled, the window focus policy, the global animation speed and hot corners settings. This is one of the more important configs that defines a lot of behavior, it probably also covers more things that I am not using. It is also very easily readable :)

~/.config/plasma-org.kde.plasma.desktop-appletsrc This is another really important config. It contains all of the panel and widget settings, including system tray settings. It can be a bit hard to parse and read, but it follows this basic format: [Containments][numeric id] This defines a panel

[Containments][numeric id][applets][numeric id] This defines a widget or other object that is part of the panel.

In general, there will be entries to define all of the panels and their components, and further entries (matching the [numeric id] of the definition entry) that define their configuration and placement within the panels.

~/.config/plasmashellrc Contains more panel definition settings for panel behavior and dimensions, much more brief and less comprehensive than the previous config, not sure why they are even separate in the first place shrug. The panels are identified with the same [numeric id]

~/.config/plasmarc Contains theme settings

~/.config/gtk-3.0 and ~/.config/gtk-4.0 directories Contains appearance settings for gtk apps to match the plasma theme and color settings

~/.config/xsettingsd directory Contains more settings for gtk apps appearance and behavior (icons, toolbar style, fonts, cursor settings, etc)

That’s all of the files I am keeping track of and porting over from ~/.config/ Next up is the stuff in ~/.local/share

~/.local/share/konsole Here be the terminal profile settings

~/.local/share/plasma/plasmoids This is where any extra plasmoids/widgets that you have downloaded and added are kept. These are pretty easy to copy around directly without having to track them down and download again, but they also might break between major plasma versions

Whew, ok, we are almost done! The following parts are how I handle wallpaper and themes/colors.

For wallpaper, I actually have a pretty janky method of nuking the contents directory of the default plasma theme at /usr/share/wallpapers and tossing my own images in there matching the file naming because I am a monster who was tired of analyzing config files when I decided on this approach XD

I used to use a custom theme (more details on porting that below) but when moving from plasma 5 to 6 and porting it over for testing… It broke so hard that I swore off custom themes completely (I couldn’t even open the settings menu, it would technically “open” but the window would never display)

My new approach is to use the plasma dark theme that is included by default, modify the colors settings and save them as a new profile. This actually got me everything I wanted from a theme anyway and only creates one file to keep track of!

~/.local/share/color-schemes/<name>.colors

Any custom themes you have downloaded will be in the following directories (including the one above)

~/.local/share/aurorae/themes/

~/.local/share/plasma/desktoptheme and ~/.local/share/plasma/look-and-feel