how to create new groups?

[a3rosol]

Hi! I don't know how to create a new group for the feeds. Is there some UI element I'm not seeing?

[passiomatic]

There's no UI for creating new groups.

The workaround is to create a OPML feed with a group and one or more feeds into in and import it with:

sweat import filename.xml.

[a3rosol]

Allrighty, then I'll do just that. This should be a feature though in a future version

[passiomatic]

I am genuinely interested in hear why do you people use groups. I'm subscribed to something like 70 feeds - most of them are personal blogs so they are rarely updated and I don't need to categorise feeds at all. So that's why groups in Coldsweat are so underpowered.

Since you are not the first user asking for better group handling I'm wondering why people ask or it. Why do you find groups useful?

[a3rosol]

I'm subscribed to a LOT of feeds from traditional websites as I don't like Twitter and the like to stay up to date. Also, RSS is my primary means of consuming online news. I'm subbed to 5 different major news sites and my mindset is rather "let's see what's happening atm" rather than "let's see which updates were published on site xyz". So I can click on my news group and see all the newsworthy items 😊 same with tech news, security stuff and so on. The specific site/blog/news paper loses its relevance. If I'm really interested in a particular site, I can still single it out. Hope this helps and gives you an insight in my work flow Andrea Peltrin <notifications@github.com> schrieb am So. 20. Mai 2018 um 21:26:

…

I am genuinely interested in hear why do you people use groups. I'm subscribed to something like 70 feeds - most of them are personal blogs so they are rarely updated and I don't need to categorise feeds at all. So that's why groups in Coldsweat are so underpowered. Since you are not the first user asking for better group handling I'm wondering why people ask or it. Why do you find groups useful? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#115 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEUOPlPJWpFC0cDWMjbnBQ5sOHo2_NuGks5t0cNggaJpZM4Trzz-> .

[nitinthewiz]

I use groups (on my Fever install) to separate longreads, pure tech blogs, webcomics and personal blogs and even have a section for "Blogs by Women" (though I'm deprecating that to bring those blogs to their respective topics). I think it's a good idea...

[passiomatic]

Thank you @nitinthewiz and @a3rosol for your input.

In the @a3rosol case I guess that, when you are subscribed to a bunch of major news sites, the "unread" view is quite useless - there's too much going on to start marking as "unread" dozen and dozen of entries every day. Anyway, the "let's see what's happening atm" scenario makes sense.

Last week I was thinking on how I could redesign the Unread view, or better, i've came to the conclusion that the unread/saved/all is quite artificial. It's there because Fever API needs two database tables read and saved, so this surfaces on the UI. This is a typical issue with UI design: the underneath system architectures is reflected into the user facing interface. It takes some time to take a step back and rethink the whole thing.

To be clear, it makes perfect sense to have a Saved view. One saves a feed item which is interested in, want read later, want to review periodically, etc. However, Unread and All, uhm. I think I'll unify those in a single view. Also, after a configurable period of time feed items will be deleted, unless starred (saved).

I understand that the above changes doesn't "fix" groups, but I think that, since groups are already here they will remain in Coldsweat. I need to do two things, though:

• Allow to create a new empty group
• Allow to move a feed to one group to another

I can do this incrementally, but I think that this is the bare minimum. There are more, of course: delete a group, allow multiple feeds to be move from one group to another at the same time, allow to creare a new group when adding a new feed, etc. We'll see.

[a3rosol]

Well, I'm using Reeder exclusively, so coldsweat is more backend than front end for me. Marking entries as read is still crucial for me, because I get anxious if the unread count is too high 😅 with Reeder it's easier. But in my (maybe special) use case, a feature that groups similar entries would be amazing and would make me use the web ui exclusively. On a busy news day, there are simply too many thematically similar news stories out there Andrea Peltrin <notifications@github.com> schrieb am Mi. 23. Mai 2018 um 21:00:

…

Thank you @nitinthewiz <https://github.com/nitinthewiz> and @a3rosol <https://github.com/a3rosol> for your input. In the @a3rosol <https://github.com/a3rosol> case I guess that, when you are subscribed to a bunch of major news sites, the "unread" view is quite useless - there's too much going on to start marking as "unread" dozen and dozen of entries every day. The "let's see what's happening atm" scenario makes sense. Last week I was thinking on how I could redesign the "unread" view, or better, i've came to the conclusion that the unread/saved/all is quite artificial. It's there because Fever API has internally two tables read and saved, so this surfaces on the UI. This is a typical issue with UI design. The underneath system architectures is reflected into the user facing interface. No good. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#115 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEUOPkaqBB3YLb5WwCL4Gk_mR6GenGzBks5t1bHZgaJpZM4Trzz-> .