Loomio bugs, issues and feedback

@Rob Guthrie no worries...u have a lot on and it is not that much of an issue.

i had a memory...one of these members always used to show as active and observing but upon talking real time with her, she said she was not. she said that her apple/ipad stuff did that on other platforms as well...hmmm

@david rayner sorry for the delay with this. Should get to it this week.

Actually, send me the user emails of those people who you removed, and a thread where they should not be a part of. I'll have a look.

The code says that when you remove a member, we remove their access to all threads in the group.

i removed those 2 people from that particular thread but they show up in others.

only 2 people in particular...but they may be only the 2 most recent removals.

will send screen shot.

Can I confirm?

You have a thread that was created a while ago. Since then some people have been removed from the group. When you click invite from that thread, the membership lists some of those removed people as being guests in the thread?

Maybe you can send me a screenshot? rob@loomio.org.

not sure if this is a bug...but i will ask.

today,when inviting people to a thread, i noticed removed members on the thread members list as (guest) They will have been thread members in past...but i do not remember seeing removed guest in past.

according to the manual, they have no further access but i was not sure what guest means.

(but of course they were not on list of group members on top invite line when opened...)

Wow Rob - that was quick! Thanks 🥰

Ok, fixed. Thanks again @Midi Berry.

I'll fix this now. Thanks for letting me know.

Hi. Is anyone else getting messages that they are not currently a member of groups to which they belong (and in my case, of which I am also an admin)?

As per the attached screenshot:

It does not appear to be actually affecting my access to the groups and threads therein.

@Aaron Wolf I've updated the threading code. Now when you reply, the OP is mentioned, so that should have a similar effect to you're request to say "in reply to". Additionally, threads default to 2 levels of nested reply - this change was made because you can now reply to votes in proposals.

I think you could write a PhD on this subject. For my loomio group of mostly old people with limited IT experience, I make the default thread type chronological, no nesting, newest first. Seems to have worked so far. I think a forum of IT programmers and superusers can deal with anything.

I don't prefer the flat Discourse style. I like nesting still, and nesting even when chronological isn't really a problem. Infinite nesting as an option might be good.

But yes, the "in reply to…" link in the title string on a comment would basically fix the core issue where some situations can confuse.

I hear what you're saying. It does seem confusing to switch between ordering by reply to ordering by time in some circumstances.

In this thread right now, (which is 'newest first') it's working well. An initial comment houses the following discussion, and there is no unnecessary drift right.

I did have a algo such that if replies were chronological they would not be nested, and we just nest replies where they interrupt chronology, I got a lot of confused feedback about that one too.

It's completely reasonable to enable infinite nesting as an option. It makes sense in some cases.

I can also easily add a "in reply to ..." as part of the title string on a comment, as you suggest.

Ironically, while I started from the Reddit opinion, I was thinking of Discourse when currently confused here at Loomio. Discourse has the capacity to more easily jump between a reply and what it was replying to so that I can at least make the connection even though it's not shown visually. In Loomio, I can find myself unable to figure out which post a reply was for in some cases. I suspect I'd feel okay with two levels of nesting plus some way to click and see what comment a reply is tied to among the lowest-level of the nesting.

Yea, we can support infinite nesting, but we're trying to avoid the conversation just drifting to the right by default. Limiting it has worked well most of the time. I'd like to know if 2 levels fixes it for you.

We're trying to strike a balance between the Discourse opinion that nesting is terrible for readability (I do not agree) and reddit approach that means many voices get buried.

It's actually a data structure rewrite when you change nesting settings. The ability to have very long threads, and send the browser only the part the user is interested in, and dynamically load the next or previous content, requires that we have all that information clearly written out so we can easily query for it as the page is used.

This means everyone sees the same thread structure. This has been good because most casual users would not change thread settings so letting an admin setup the best way improves the experience for most.

Thanks, I would suggest more than 2 levels even. It could also be nice to let users choose their view rather than the nesting setting be fixed for the whole group. I don't see any way for me as a member not admin to adjust the view I see.

You can enable 2 levels of reply.. either per thread or by default for all threads in the group.

Try clicking "Oldest first" on the thread context.

Here's a help page for the group default.

https://help.loomio.com/en/user_manual/groups/settings/index.html#thread-settings

I'm finding threading and replies really hard to follow. It looks like Loomio shows only one layer of replies. People can reply to a reply, but then it seems almost impossible to see the context.

So, in a current topic I'm following, I see replies that say effectively "I really agree with this point, let's focus on that", and it's not clear whether that is about a top-level comment or about someone else criticizing the top-level comment.

It would be so much easier to follow conversations if threading of multiple levels was shown.

Cool, thanks!

I saw it with Greenbeam, a add-on for Firefox allowing to see the third-party domains connected to a visited site through images, cookies etc. For instance, the image below, showing the link I saw to fonts.gstatic.com, will make a side triangle to zzz.zaclys.com:

Of course, every object from outside loomio.org will make such a “third-party site” triangle and a discussion can so become “dirty” even if the base code of Loomio is clean. But I didn't think fonts can be fetched this way. (Is it?)

Anyway, this is good news and also a good opportunity to ask the people at Framasoft to install a recent version.

For your information, they configure their 2.1.9 version of Loomio in order to avoid the link to the fonts of Google, but they have to repeat the operation after each restart.

Thanks a lot!

How did you decide it was also the case at loomio.org?

Thanks for getting in touch, but this change has already been made. Loomio serves it's own fonts.

If Framavox update to the latest version, the problem will be resolved.

Hi there!

Somebody recently let me see (with Greenbeam ) that Framavox (French instance of Loomio — v2.1.9) had links with fonts⋅gstatic⋅com and fonts⋅googleapis⋅com.

After that, I realized that it was also (even more) the case at loomio.org.

This could become a serious issue. Certainly for the people concerned with the protection of their privacy, but also for legal reasons.

An example: “Website fined by German court for leaking visitor's IP address via Google Fonts”.

I find the functionalities of Loomio really useful (with your decision-making tools, that have no known equivalent), but I (and the group I belong to) frankly prefer a less performant tool than a better one, that allows a web giant to get information about me.

⇒ So, here comes at last my questions:
- Is there a easy way to get rid of these (quite possibly tracking) “services” on a particular instance?
- Have you got plans to replace these tools by your own code/fonts?

Thanks in advance for any information

cheers loomio. must not

trigger

timeline by writing entire post in h2.

personally...i really like using loomio. especially when u can see what people altered and when...

aha...i remembered the save post hack...write what u want to write first then paste and post.

done.

oh...and i miss the searchable emoji...

that persistent box is still irritating...even when i go back a page (alt Left arrow) it persists/

this is the only site i have ever encountered this within.

everything else is quite alright. keep up the good work.

that did not end up being the last post...but that is the only one thing that i was giving a heads up about that i truly wish was different.

thanks for the replies.

Tasks is a good idea. i watched the whirly pool quite a few times, wondering what would happen...waiting for a chance to use it. next meeting...

hrrmm...

and last but first in my list...the popup box that comes up for 'seen by xx' which is such a useful function (esp. for finding lurkers...) does not evaporate with Esc key or random click outside or in box, only a precise click on the quite small x in a circle. minor but irritating....

@Rob Guthrie i need to get out more...

the search has such idiosyncracies...how is the rewrite going?

oh I have a search rewrite in the works... found a great article on how to support that kind of thing.

when one uses search box, it is working great....but adding just one space at end returns zero results.

does it need a reminder (but that may be messy...) written next to search,or in box, not to include spaces?

is the Loomio search boolean? (wow...that sounds like i really know what i am talking about.)

@Robert Guthrie 'save draft' is the feature that would solve most of the complaints we get at our end - autosave would be even better! People complain that they have lost a lot of work when they have accidentally navigated away from the page and the work is gone when they click 'back' in their browser. I have done this myself when using CTRL-K to insert a hyperlink into highlighted text (I do this on autopilot - I use the google suite and Word a lot, and that's the shortcut there) - in Loomio, CTRL-K takes you to the navigation bar, and when you quickly paste the link there and press enter, away you go...

Oh wow. That's more the mobile OS fault that loomio, however save draft is in the near roadmap, a customer is sponsoring the work.

a colleague who uses L on her mobile (not sure what sort...sorry) noticed that it was timing her out when a call (might have been no matter how long...) arrived so she would lose what she was working on. is there a way round this?

any progress on a save post progress sort of notepad or something?

hard question of the day....if i ran linux, would that problem go away? 🙊

no reply needed...bigflop are watching thru the nsa backdoors...

dark mode is autodetected on boot, unless you change the setting manually, after that it's always manually set.

noticed for a while...dark mode does not turn back on after logging back in until a refresh...

may just be my 8.1 pc...ff 97... as i delete them occasionally, is it a cookie thing?

Ok, wow, nice spotting. It will be fixed in the next release, which you can subscribe to via github.

Hrrmm, that's odd. I'll look into it.

I'd say it's half solved :)

In the poll details page you can see all the voters but on the voting table, the voters who voted 'no' everywhere are still not visible. (tested with v2.11.6)

Did that fix the issue?

Update done. Thanks !

Please update your Loomio version, this should be fixed now.

Hello community. We have a "bug" on the display of the voters in the results of date poll. When a member votes 'no' everywhere it does not appear in the results so impossible to know who really voted. Here is a capture with 8 voters but only 7 appear on the detail. @Rob Guthrie

Thanks so much, Rob. Good to see the reason; hope the long URL problem will be OK.

I used Loomio years ago in another role, another organisation. Great to see the improvements over time.

Sorry about that. I used too much CSS trying to fix a problem where long URLS would blow the width of the page out.

Deploying a fix now, thanks for bringing this up.