bugsPumpahttp://pumpa.branchable.com/bugs/Pumpaikiwiki2017-02-10T18:14:36ZHTML entities in title fieldshttp://pumpa.branchable.com/bugs/HTML_entities_in_title_fields/2017-02-10T18:14:36Z2017-02-10T18:14:36Z
<p>Reported by JanKusanagi on IRC:</p>
<pre><code>00:23 <JanKusanagi > Sazius: apparently Pumpa is ensuring the Title field in posts
doesn't have reserved HTML chars, replacing them with HTML
entities, but by looking at the Meanwhile feed interactions for
this post, the Title field could (probably should) have those
characters:
https://datamost.com/zykotick9/note/4lXVG1otQHqR0R4Izi9NVQ
00:23 < pumabot> why the pumpiverse is so quiet... &lt; UPDATED for date & newest
version!&gt; - datamost.com
</code></pre>
qjson not found on OS X/Homebrew systemshttp://pumpa.branchable.com/bugs/qjson_not_found_on_OS_X__47__Homebrew_systems/2017-02-01T17:28:25Z2017-02-01T17:28:25Z
<p>On my OS X system, building Pumpa via <code>qmake && make</code> fails with an error about qjson not being found. This is because Homebrew installs qjson as libqjson-qt5, not libqjson. So e.g. the include path is <code>/usr/local/include/qjson-qt5</code> but the build system is expecting <code>/usr/local/include/qjson</code>.</p>
<p>Pumpa version:</p>
<pre><code>% git rev-parse HEAD
3cf89c487ecd9d7d5056eebb26ee466bc46074b3
</code></pre>
<p>QMake version:</p>
<pre><code>% qmake --version
QMake version 2.01a
Using Qt version 4.8.7 in /usr/local/Cellar/qt/4.8.7_2/lib
</code></pre>
Posting new notes crashes Pumpa, 16.10http://pumpa.branchable.com/bugs/_Posting_new_notes_crashes_Pumpa__44___16.10/2017-01-23T22:14:54Z2017-01-23T22:14:54Z
<p>This is a forward of a bug posted by Nathan Willis to Launchpad at <a href="https://bugs.launchpad.net/ubuntu/+source/pumpa/+bug/1658795">https://bugs.launchpad.net/ubuntu/+source/pumpa/+bug/1658795</a>:</p>
<p>Using Pumpa on a machine I just upgraded from 16.04 to 16.10. After the upgrade, reading timelines works, but every attempt to post a new note (including File->New Note, C<sup>N</sup>, and clicking on the Comment button on any existing post in the timeline) immediately crashes the Pumpa application.</p>
<p>This makes Pumpa essentially a read-only utility which, while interesting, is certainly insufficient.</p>
<p>I have not encountered any other broken functionality after the upgrade. FTR, I am using Pumpa with an identi.ca account.</p>
<p>As noted by Nathan at <a href="https://identi.ca/n8/note/Ty7EH1_TQtqJEq7ogk8VkQ">https://identi.ca/n8/note/Ty7EH1_TQtqJEq7ogk8VkQ</a> he's using the stock version. According to <a href="http://packages.ubuntu.com/yakkety/pumpa">http://packages.ubuntu.com/yakkety/pumpa</a> this is 0.9.2.</p>
<p>An attempt will be made to backport 0.9.3 to ppa:skellat/tests to see if it can be made available.</p>
Auto-filling @targets fails very oftenhttp://pumpa.branchable.com/bugs/Auto-filling___64__targets_fails_very_often/2016-09-17T08:29:15Z2016-09-17T08:29:15Z
<p>Probably it's failing to fill the list of people being followed. Should be investigated...</p>
no edit buttonhttp://pumpa.branchable.com/bugs/no_edit_button/2015-05-28T02:34:33Z2015-05-28T02:34:33Z
<p>No longer have an edit button on posts I've just made.</p>
<p>0.9.1 from debian</p>
Ability to disable loading of avatarshttp://pumpa.branchable.com/bugs/Ability_to_disable_loading_of_avatars/2014-12-26T19:54:05Z2014-12-26T19:53:49Z
<p>Request: <a href="https://pumpdog.me/rsd/note/u5IZU3uTQ3uOvZ1Gzqwv8Q">https://pumpdog.me/rsd/note/u5IZU3uTQ3uOvZ1Gzqwv8Q</a></p>
broken display of mouseover urlshttp://pumpa.branchable.com/bugs/broken_display_of_mouseover_urls/2014-11-28T19:14:26Z2014-11-28T19:14:26Z
<p>Expected behavior: I move the mouse over an link in pumpa,
and the full url is displayed at the bottom of the window.</p>
<p>Actual behavior: Works sometimes but other times the displayed url is
not the one the mouse is over.</p>
<p>Analysis: There are two kinds of links; links inside posts and links that
pumpa makes to eg, people's names. If I first mouse over someone's name,
and then move the mouse to be over a link inside a post, this is when
pumpa keeps displaying the old url, rather than showing the new url I
moved the mouse over.</p>
<p>Certain mouse movements clear the previously displayed url, and then
the problem doesn't happen.</p>
<p>Originally reported as <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769456">bug #769456 in Debian</a>.</p>
Ability to enlarge font/text sizehttp://pumpa.branchable.com/bugs/Ability_to_enlarge_font__47__text_size/2014-11-17T18:36:22Z2014-11-17T18:36:22Z
<p>I cannot find how to make text bigger.</p>
Ver 0.9 doesn't respect KDE4 colour scheme.http://pumpa.branchable.com/bugs/Ver_0.9_doesn__39__t_respect_KDE4_colour_scheme./2014-10-15T13:27:46Z2014-10-15T13:27:46Z
<p>I just ugraded from version 0.5 to 0.9, and now Pumpa doesn't respect KDE4 colourscheme. That is, I am using a dark colours scheme, but Pumpa has the usual greyish background that is default for QT apps.</p>
<p>I am using ArchLinux, and installed the package using AUR.</p>
Image item appears without contenthttp://pumpa.branchable.com/bugs/Image_item_appears_without_content/2014-09-04T19:41:57Z2014-09-04T19:41:57Z
<p>For some reason <a href="https://pump.libernil.net/api/image/NzNkfOU6RQ-peBhzYvPhAQ">this post</a> appears in pumpa without the text content. <a href="https://pump.saz.im/api/proxy/fBY3_vnYTjWXfnB2cWt7vg">Proxy URL.</a></p>
<p>Dumping json shows it's missing:</p>
<pre><code>{
fullImage: {
height: 960
pump_io: {
proxyURL: https://pump.saz.im/api/proxy/OQaOJfmlTzahT1OPeCiepg
} // end of pump_io
url: https://pump.libernil.net/uploads/cmhobbs/2014/9/4/zyOrzg.jpg
width: 1280
} // end of fullImage
id: https://pump.libernil.net/api/image/NzNkfOU6RQ-peBhzYvPhAQ
image: {
height: 240
pump_io: {
proxyURL: https://pump.saz.im/api/proxy/abq1J90hQ9mTaZsnf5n4pg
} // end of pump_io
url: https://pump.libernil.net/uploads/cmhobbs/2014/9/4/zyOrzg_th ...
width: 320
} // end of image
liked: false
likes: {
pump_io: {
proxyURL: https://pump.saz.im/api/proxy/ZReWoOIDThGUCSgQ4Dullg
} // end of pump_io
totalItems: 0
url: https://pump.libernil.net/api/image/NzNkfOU6RQ-peBhzYvPhAQ/likes
} // end of likes
links: {
self: {
href: https://pump.libernil.net/api/image/NzNkfOU6RQ-peBhzYvPhAQ
} // end of self
} // end of links
objectType: image
published: 2014-09-04T18:21:36Z
pump_io: {
proxyURL: https://pump.saz.im/api/proxy/fBY3_vnYTjWXfnB2cWt7vg
shared: false
} // end of pump_io
replies: {
pump_io: {
proxyURL: https://pump.saz.im/api/proxy/mwsRFCeHTKyI3Us_j2AABg
} // end of pump_io
totalItems: 0
url: https://pump.libernil.net/api/image/NzNkfOU6RQ-peBhzYvPhAQ/r ...
} // end of replies
shares: {
pump_io: {
proxyURL: https://pump.saz.im/api/proxy/JKgd8S03QXSVaTjioqr31Q
} // end of pump_io
totalItems: 0
url: https://pump.libernil.net/api/image/NzNkfOU6RQ-peBhzYvPhAQ/shares
} // end of shares
updated: 2014-09-04T18:21:36Z
url: https://pump.libernil.net/cmhobbs/image/NzNkfOU6RQ-peBhzYvPhAQ
} // end of JSON
</code></pre>
Some pics brokenhttp://pumpa.branchable.com/bugs/Some_pics_broken/2014-09-02T17:24:53Z2014-09-02T17:24:53Z
<p>The big picture on this post appears as a file icon on Pumpa, also the avatar is broken for Tsyesika:</p>
<p><a href="https://io.theperplexingpariah.co.uk/Tsyesika/note/HfaTTAx3QS-WJ5KKtVsMZA">https://io.theperplexingpariah.co.uk/Tsyesika/note/HfaTTAx3QS-WJ5KKtVsMZA</a></p>
comments displayed out of orderhttp://pumpa.branchable.com/bugs/comments_displayed_out_of_order/2014-08-05T17:04:58Z2014-08-05T17:04:58Z
<p>i've noticed this problem on the web interface as well. i've noticed it after clicking the "load more comments" button.</p>
<p>someday it might be good for pumpa to sort comments by time, unless they are intentionally being sorted some other way. <img src="http://pumpa.branchable.com/smileys/smile.png" alt=":-)" /></p>
<p>...</p>
<p>i looked at an old thread in pumpa and saw that two comments in an older thread were swapped. it ought to be in your meanwhile feed in pumpa.</p>
<p>i restarted pumpa to see if that would resolve the issue, but now pumpa doesn’t display the first message, and doesn’t show a button to load more comments. the original 2nd and 3rd posts are still swapped.</p>
<p>Sazius: Yeah, unfortunately Pumpa is unable to fetch the rest of the conversation if only a reply is in the meanwhile feed. There’s a bug report about this: <a href="https://github.com/e14n/pump.io/issues/873">https://github.com/e14n/pump.io/issues/873</a>. Pumpa does its best to collect what it sees in the feeds to the conversation. In my case I see only the original post (because it was included as inReplyTo object to cwebber’s comment (which was in my feed). Then I see your “It’s a joke” reply, since cwebber favourited it causing it to show up in the feed.</p>
<p>With regard to the ordering, I’m wondering if people liking the posts later might be confuse it? Not sure…</p>
changing tabs can be slowhttp://pumpa.branchable.com/bugs/changing_tabs_can_be_slow/2014-08-05T17:02:45Z2014-08-05T17:02:45Z
<p>sometimes changing tabs in pumpa can be slow. it seems to be more noticeable if it's been running for a while.</p>
Allow public sharinghttp://pumpa.branchable.com/bugs/Allow_public_sharing/2014-08-05T16:48:59Z2014-08-05T16:48:59Z
<p>Bernhard E. Reiter: When "sharing" a message, it only goes to followers by default.
It would be nice to have an option or button to share for Public
or other recipients as well.</p>
<p>Sazius:
I should look into that. I remember seeing a discussion somewhere on pump about if sharing publicly was a good idea, but I can't remember the outcome of that discussion <img src="http://pumpa.branchable.com/smileys/smile.png" alt=":-)" /></p>
<p>Bernhard: I believe there are two distinct questions:
a) should the interface be made more complex by adding an option to share
publically or even more to select all target lists.
b) What should the default be. Or how the user interface should look like.</p>
<p>I believe that a more non-public default is good,
but for a) the answer is clearly yes, we need at least the followers+public extra functionality.
I'd say that even a full blown to: and cc: dialog would be warranted with an option
that public is filled in as default together with Followers.</p>
Proxy Settingshttp://pumpa.branchable.com/bugs/Proxy_Settings/2014-08-05T16:48:42Z2014-08-05T16:48:42Z
<p>jpope: It'd be handy for the tin-foil-hatters if you could either manually set proxy settings (say for use with tor+privoxy) within the settings or if Pumpa could look at system-wide set proxy settings. The latter is likely not feasible as it'd be WM/DE dependent I imagine.</p>
<p>Otherwise, running Pumpa via torify works just as well.</p>
Clean cache dir occasionallyhttp://pumpa.branchable.com/bugs/Clean_cache_dir_occasionally/2014-08-05T16:47:42Z2014-08-05T16:47:42Z
<p>~/.cache/Pumpa/pumpa/</p>
<p>can get pretty big after a while</p>
Ability to use external editor http://pumpa.branchable.com/bugs/Ability_to_use_external_editor_/2014-08-05T16:47:13Z2014-08-05T16:47:13Z
<p><a href="https://microca.st/johns/note/SnDkDvWQRdyyhaoT5dY2Vw">https://microca.st/johns/note/SnDkDvWQRdyyhaoT5dY2Vw</a></p>
Preview Embedded images http://pumpa.branchable.com/bugs/Preview_Embedded_images_/2014-08-05T16:46:24Z2014-08-05T16:46:24Z
<p>jpope: It would be nice if when embedding images in a post, the embedded image could be seen in the preview.</p>
<p>Sazius: The problem is I'm using Qt's QLabel for the preview (and for showing posts as well) to keep Pumpa relatively light weight. It can show images, but note load them remotely. Embedded images in posts work because Pumpa actually downloads them to a local cache (~/.cache/Pumpa/pumpa/) and then updates the link to a local one.</p>
Memory leak problemhttp://pumpa.branchable.com/bugs/Memory_leak_problem/2014-08-05T16:45:10Z2014-08-05T16:45:10Z
<p>See <a href="https://microca.st/dper/note/irBD0VcITBigVUdVjJQl7g">https://microca.st/dper/note/irBD0VcITBigVUdVjJQl7g</a>
and <a href="https://identi.ca/jankusanagi/comment/pyCtOoHVT0G364xu6bTvlw">https://identi.ca/jankusanagi/comment/pyCtOoHVT0G364xu6bTvlw</a></p>
<p>bernhard: Does it make sense to run pumpa in some profiling tool like valgrind or compiled with -g1 -g3, it may provide some insights
if memory or cyclers are lost. I’ve noticed some issues when running pumpa for several hours and loaded a lot of of lot messages.
(I usually do not run pumpa longer than 8 hours and then shut down my workspace machine.)</p>
<p>Running it even longer with profiling or memory checking could give some ideas where to debug further.</p>
<p>sazius: I ran with valgrind and found the FileDownloader to be a big problem. I think the situation is now improved after a rewrite to FileDownloader, however it is still not good.</p>
Add extra buttons for "follow" activitieshttp://pumpa.branchable.com/bugs/Add_extra_buttons_for___34__follow__34___activities/2014-08-05T16:43:44Z2014-08-05T16:43:44Z
<p>usr_share: Right now, if someone follows you, the only way to follow the person back is to use the browser.</p>
<p>I think that "follow" (or "unfollow") activities should have the following buttons available:</p>
<p>[see profile] -- quickly see the person's profile, similar to the [+] button to the right of all posts. (</p>
<p>[follow / unfollow] -- to, obviously enough, follow the person back, or to unfollow if already following.</p>
<p>[see activities] -- if possible, to see the activities of that specific user like one's own in the "Activities" tab.</p>
<p>Sazius:
Actually there's a work around for the first problem: open your "followers" tab, the recent follower will be at the top. Press "follow" <img src="http://pumpa.branchable.com/smileys/smile.png" alt=":-)" /></p>
<p>But yeah, ideally you should be able to do that directly from the "X has followed you" item.</p>
<p>Right now it shows your own profile, which is "technically" correct, because that is the object in the pump feed. But not very useful in this case <img src="http://pumpa.branchable.com/smileys/smile.png" alt=":)" /></p>
Ability to change aspell language on the flyhttp://pumpa.branchable.com/bugs/Ability_to_change_aspell_language_on_the_fly/2014-08-05T16:42:44Z2014-08-05T16:42:44Z
<p>E.g. for people that regularly write different languages.
This would also be an option in the config file.</p>
ability to search usershttp://pumpa.branchable.com/bugs/ability_to_search_users/2014-08-05T16:41:45Z2014-08-05T16:41:45Z
<p>tioeze: The thing is when you want to unfollow a user or only to search him is very problematic when you have more than 250..
I don't think about a tab or so, only a shorcut like FF with ctrl+f or something like that.</p>
additional highlighting for stringshttp://pumpa.branchable.com/bugs/additional_highlighting_for_strings/2014-08-05T16:41:06Z2014-08-05T16:41:06Z
<p>jrobb: Would it be possible to highlight certain strings in posts?
for instance, I could add "jrobb" to my highlight list, and this would be highlighted in posts where mentioned (like IRC).</p>
<p>Also, maybe if this happens in the "meanwhile" tab the header could get a "*" or different highlight color instead of red.</p>
User tabhttp://pumpa.branchable.com/bugs/User_tab/2014-08-04T19:52:24Z2014-08-04T19:52:14Z
<p>David Marsden: Tab for user timeline, i.e., when you click on a user's name it shows their timeline in a new tab (a bit like Heybuddy does). Useful for deciding wheter to follow someone. I think current behaviour opens up a web page instead.</p>
<p>Sazius:
This is definitely on my todo list, but I need to first make tabs that can be closed. The Qt toolkit that I'm using makes that a bit difficult, I need to investigate this.</p>
CLI Optionshttp://pumpa.branchable.com/bugs/CLI_Options/2014-08-04T19:22:48Z2014-08-04T19:22:48Z
<p>jpope: I'd <strong>love</strong> to be able to trigger a new post (specifically with an image) via the command line.</p>
<p>The goal of this would be to add a custom action in Thunar or a service .desktop file (for Dolphin, maybe others) to trigger a right click action in the file manager. Right click an image->'Post with Pumpa'.</p>
<p>Sazius:
I'm a bit conflicted about giving a GUI program a lot of CLI functionality. OTOH, Pumpa already has you account set up so it would be a waste not to use that <img src="http://pumpa.branchable.com/smileys/smile.png" alt=":-)" /></p>
<p>One idea I had was to create another binary, e.g. "pumpa_cli" or whatever and just link the pump.io-API bits in there. It would use the same conf file as Pumpa but wouldn't open up a GUI window at all. Of course you'd need to setup the conf file first with Pumpa's OAauth Wizard thingie...</p>