Sometimes building and maintaining open source is really not motivating.
We understand that we can't make everybody happy, but one person in this thread really doesn't know etiquette.
https://t.co/ZOBB1GQqY7
@SkiyeBlueFox@SerahTheLioness The symptom that is described by acropalypse, is that cropped information is still available. This means if you cut away sensitive information from a photo or screenshot, with a trick people can still look at it.
Greenshot does not have this issue.
I just found another Microsoft Store app entry for Greenshot where "Brian Studio" is selling apps which seem from others. He/they get the money, but over our backs as it generates work on our side, we get nothing. Please do not support this person/app: https://t.co/NJAnuNe35K
Unfortunately the part in the policy about open source, which should be rewritten so it would help us, was completely removed: https://t.co/LlJ9aV59dR
That is making things really hard, the Greenshot App in the store which is NOT from us, is still making money over our backs. ๐ข
We hope the newly added store policies will help: https://t.co/J7zvF3giip
"Not attempt to profit from open-source". I hope this doesn't prevent us from selling Greenshot as App in the future, as we place a lot of time in it which is only possible if we get something in return.
@lakritzator@SlackHQ It now has been more than 5 months where @SlackHQ is causing inconveniances to our Windows users and they still didn't report back when they are finally going to fix it.
https://t.co/icTMOC3Lk1
@NilsAndreasT You are probably a paid @SlackHQ user and use their "Window sharing" feature. There is a bug in Slack which, for whatever reason, resizes (!!) the Greenshot capture window. More information here: https://t.co/Au2gHwjOVC
As mentioned there, if possible report the issue with them.
@Candace__Hughes We are always interested in user stories, helping us to help you. Would it be possible to describe what you are doing, and how you work & what want to archive, but please without going into solutions how it should work (that is our job)
You can do it here https://t.co/KA5ugHI389
@Candace__Hughes@Techn392 We are looking at the possibilities to make reversing an obfuscation impossible, but for now it's certainly important that people need to be aware of (independent of Greenshot) that obfuscation can be reversed.
If things are sensitive a black box is always the best option. ๐
Things like this make us sad! We understand that not everybody likes our software or that it sometimes has issues. We spent a lot of free time on our product, which is in fact free, so why do this without explaining what bothers you? ๐ข
#FOSS
@ericwilborn Hello Eric, I do not know what you mean with pbrush and we didn't remove anything.
Please report your issue here, so we can track it. https://t.co/QEjben88Tf
@Patrick87724454 In theory it would reach out for an update check every x (look in settings) days. It will only download an XML with the latest version. There is a known bug, fixed with version 1.3, in certain setups the check is very often. If it happens a lot, set update check to 0.
@devuxer Please tell your IT that is not how code signing works! Our certificate from 2017 expired, so we can not sign a NEW exe. It's not like a SSL cert (way more expensive), otherwise no one could release 1 week before expiring.
Windows shows signature is OK if you close that window.
@arudlang The biggest issue with free & open source, we didn't have funding for that kind of hardware. This makes it hard to support that kind of setup.
Prices haves dropped, and make it more reasonable to be able to support this hardware.
Check out 1.3, but Windows & DPI is not easy.