Copilot und Automatisierung: So wird KI im Dokumentenmanagement produktiv
#DMS
@geobomatic
I use both on different machines.
On #mangowc I use #dms because it has a widget to set the layout and you can place widgets on top above all windows.
About a month ago I switched away from using my own dotfiles for #niri in lieu of #dankmaterialshell. It might stem from me wanting to just use my machine instead of having to maintain my machine, but it’s been a very nice experience. The devs are working hard adding a ton of features to make a nice desktop environment, and there’s already a pretty in depth plugin ecosystem for adding more specific features. I’ve been enjoying it!
O danklinux.com agora tem plugin pro #homeassistant #smarthome
Warum Unternehmen beim Dokumentenmanagement Geld verlieren, ohne es zu merken
And here my desktop in "all its glory".
I left #dms pretty vanilla because it just looks great out of the box. That I could move the bar very, very easily to the left to fit better into my #niri workflow is superb as well.
As I said: very happy with the outcome.
So awesome. #dms launcher now supports git search plugin in latest dev builds. Also there's a kde connect plugin. #niri/#dms combo does it all for me now. <3
DMS 1.2 "Spicy Miso" Released
https://danklinux.com/blog/v1-2-release
What's New:
- Desktop Widgets & Plugins
- Theme Registry
- Native Clipboard and History
- Monitor Configurator
- Notification Improvements
- Cursor & Layout Configuration
- DMS Doctor
- Keyboard Shortcuts Editor for niri, Hyprland & MangoWC
- Settings Search
- i18n: RTL Support
- Launcher Improvements
DankMaterialShell (dms ) 1.2.0 + niri Running in Void
@berdandy
2/2
You should consider a 'document management system' (#dms) for much more than 2k titles. Just know that these are almost universally server type systems with web GUIs. You'll have to learn a bit of #selfhosting but that's no bad thing.
Some good options here:
https://awesome-selfhosted.net/tags/document-management.html
I use Mayan EDMS to manage a growing ~80k assorted document titles, including rpg.
Paperless-ngx should meet your, presumably, more modest needs and is easier to set up.
@unattributed 𓂃✍︎ @Ben Pate 🤘🏻 @Social Web Foundation @Sovereign Tech Agency @Bonfire Ideally, one day, the highly advanced permissions system available on Hubzilla (based on Zot, ActivityPub optional), (streams) (based on Nomad, ActivityPub optional) and Forte (based on ActivityPub) would be cast into one or multiple FEPs.
This would solve this issue by not only controlling who receives a DM, but also who is permitted to see the DM. In combination with FEP-171b Conversation Containers (which was invented on (streams), inherited by Forte and backported to Hubzilla), the permissions of the DM would be inherited by all comments and replies to the DM with no way of ever changing these permissions anywhere in the conversation.
See, if I send a DM to Alice and Bob, then only Alice, Bob and I are permitted to see the DM. Also, only Alice, Bob and I are permitted to participate in the conversation, and Alice, Bob and I can see each comment and reply, but only the three of us are permitted to see them. The entire conversation has the exact same permissions all over, inherited from the initial DM.
Anyone of us can mention Carol all we want. But that does not give her permission to see anything in the conversation, not even the comment/reply that mentions her. Once the initial DM is out, its permissions are set in stone, and it's also set in stone that any and all follow-ups in the same conversation have the same permissions as the initial DM.
This does not even require encryption. That said, at least Hubzilla does offer encryption on top of the permissions system; however, it's only compatible within Hubzilla AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #FEP_171b #ConversationContainers #Permission #Permissions #DM #DMs #DirectMessage #DirectMessages #PrivateMessage #PrivateMessages
This would solve this issue by not only controlling who receives a DM, but also who is permitted to see the DM. In combination with FEP-171b Conversation Containers (which was invented on (streams), inherited by Forte and backported to Hubzilla), the permissions of the DM would be inherited by all comments and replies to the DM with no way of ever changing these permissions anywhere in the conversation.
See, if I send a DM to Alice and Bob, then only Alice, Bob and I are permitted to see the DM. Also, only Alice, Bob and I are permitted to participate in the conversation, and Alice, Bob and I can see each comment and reply, but only the three of us are permitted to see them. The entire conversation has the exact same permissions all over, inherited from the initial DM.
Anyone of us can mention Carol all we want. But that does not give her permission to see anything in the conversation, not even the comment/reply that mentions her. Once the initial DM is out, its permissions are set in stone, and it's also set in stone that any and all follow-ups in the same conversation have the same permissions as the initial DM.
This does not even require encryption. That said, at least Hubzilla does offer encryption on top of the permissions system; however, it's only compatible within Hubzilla AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #FEP_171b #ConversationContainers #Permission #Permissions #DM #DMs #DirectMessage #DirectMessages #PrivateMessage #PrivateMessages
As seem in the #niri Discord. #DMS by https://github.com/bbedward
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst