Activity for Gary Kramlich
-
Gary Kramlich modified a comment on discussion Users Helping Users
Please note, these forums are not actively looked at by the development team at all. Please use https://discourse.imfreedom.org/c/support/6 instead which is actively viewed by the development team. I have also (attempted) to make this forum read only as well to help people migrate to discourse.
-
Please note, these forums are not actively looked at by the development team at all. Please use https://discourse.imfreedom.org/c/support/6 instead which is actively viewed by the development team.
-
Note we don't really use these forums anymore, our main support forums are over here https://discourse.imfreedom.org/c/support/6 As far as "full functionality" goes, the answer is probably no. At a minimum, basic message functionality exists with some level of support for additional features. But all of the protocols you mentioned as handled by third parties and links to those projects can be found here https://pidgin.im/plugins/?publisher=all&query=&type=Protocol
-
This sounds like it's related to this issue that we've been tracking over in our issue tracker https://issues.imfreedom.org/issue/PIDGIN-17564
-
VOTE: pidgin
-
Gary Kramlich committed [75658f]
initial commit, bunch of work, nothing to write home about yet
-
closing merged branch
-
Add the license and a copyright file
-
Merged in styling (pull request #1)
-
remove some debug output
-
Overhaul the way the hgkeeper repo is created
-
Well everything kind of works, but hg init is throwing failures eventhough it's creating repos
-
Merged in termdumb (pull request #2)
-
Move the serve command to it's own package
-
rename setup.SetupCommand to setup.Command
-
Fix up the few unit tests
-
Move the command running to a helper function
-
overhaul how commands are found/run
-
Add an admin repos command line argument
-
Add a Dockerfile and convey.yml
-
closing merged branch
-
Merged in access-control (pull request #4)
-
Merging in Wagner Riffel's access stuff
-
Make the logs more readable
-
Lots of work on access need to clean up commands before preceeding
-
run go mod tidy
-
Merge addToKey and loadKeys
-
Wire up permissions still need to handle readonly
-
closing merged branch
-
Fix some issues I missed when merging
-
It's much more likely to get noticed than here, but the current plan is to move discussion over there. It's still pretty bare right now, but that's we're getting there :)
-
It's much more likely to get noticed than here, but the current plan is to move discussion over there. It's still pretty bare right now, but that's we're getting there :)
-
Yep, normally I don't see these, but i happened to notice the email. Also if you're interested we're been toying around with using https://reddit.com/r/pidgin as well
-
Sorry about that. I renewed the cert but forgot to bundle them for lighttpd. It's all fixed now (still running through the other sites, but pidgin.im is fixed now)
-
2.13.0 for Windows is finally available!!!
-
Unfortunately not yet. The org cert is taking WAAAAAY longer than expected. I've been hesitant to apply for a personal cert, but I might just go that route, but that's still going to be a fair amount of time to get. But at this rate, might be sooner. On Tue, Jun 26, 2018 at 10:24 PM, Alex alexoren@users.sourceforge.net wrote: Is there any progress? Version 2.13.x Windows Binaries ? https://sourceforge.net/p/pidgin/discussion/665/thread/3b859409/?limit=250#d242 Sent from sourceforge.net because you...
-
The problem is with the code signing certificate. That is, we don't have a project wide one (I'm working on that) and that the personal certainly that we've used in the past have expired and people are working on getting theirs renewed as well. There's been some talk of releasing it unsigned to get it out there but no decision has been made yet. Releasing it unsigned means you'll get prompted during the install that it comes from an unknown publisher, and maybe something else? I don't run Windows...
-
Wow I didn't realize people still used this... Long story short, we'll have a new...
1