1. OpenAI and the whole baggage of training on company data should be optional. Titles and summaries might not be that important and could be provided by the user. 2. Never ever will I buy anything from a company that looks like it's hiding where it's from and who's behind it. No, your profile pictures and a bunch of names do not count. This whole website could be scam for all I know. This might be my European (Germa…
Show HN: Struct – A Feed-Centric Chat Platform
121–130 of 143 posts
Re: Show HN: Struct – A Feed-Centric Chat Platform
#122Couldn't it be a Matrix client ? Else, a new silo is born.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#123For example, I don't want to optimize my meetings' notes so that I can have tens of meetings and keep track of it. I want to have less, but more effective, meetings.
Just a thought that I have.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#124Re: Show HN: Struct – A Feed-Centric Chat Platform
#125Slack's chat interface feels fine to me. What would prevent me from switching off Slack is losing my Slack integrations/the Slack developer APIs. How does Struct address this?
Re: Show HN: Struct – A Feed-Centric Chat Platform
#126Sometimes I wonder if we are trying to optimize productivity in the wrong way. Maybe the bigger gains are not from having tools that help us manage the clutter in communication, but instead it might be on having less communication altogether and still be effective at getting the right things done. For example, I don't want to optimize my meetings' notes so that I can have tens of meetings and keep track of it. I want…
AI can obviously generate automatic summaries from meeting transcripts, so why can't it follow up on the next steps/action items? If a next step is for Janine to set up a meeting with Carlos, why can't it just reach out to Carlos for her to set it up?
We're thinking way too small.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#127Sometimes I wonder if we are trying to optimize productivity in the wrong way. Maybe the bigger gains are not from having tools that help us manage the clutter in communication, but instead it might be on having less communication altogether and still be effective at getting the right things done. For example, I don't want to optimize my meetings' notes so that I can have tens of meetings and keep track of it. I want…
Though, you do have to abide by Metcalfe's law. Most modern work happens in teams and therefore, you have to pay the price of O(N^2) communication, where N = size of the team.
I don't see communication decreasing overall. We just have to use the right tools to be more effective at it.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#128Earlier quoted context omitted.
I don’t see this going after discord but Slack or teams perhaps?
Founder here. Struct is designed for both teams and communities. Because the problems affecting Slack and Discord are the same. We already have a bunch of community features, like publicly indexable knowledge base from threads, public-to-internet channels -- which are being used by many OSS companies (list on home page). Teams is a different product. Companies who use Teams are there because they have tight integrati…
We also don't use Threads in Teams. Things got lost trying to jump back and forth between the "Chat" tab and the "Teams" tab. So now, we just create a new chat conversation for each project we're working on and add the relevant participates and rename the chat to the Jira Ticket #. That provides enough context/summary for what the chat is about.
All that said, Struct looks really nice and I could see it benefitting our team. Especially the AI portion. We have chats going back years for long-lived projects that get shelved and then picked back up later. Being able to interact with a ChatBot to help find answers within these chats would be killer. I assume there are no plans for a Struct for Teams though.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#129Earlier quoted context omitted.
Founder here. Struct is designed for both teams and communities. Because the problems affecting Slack and Discord are the same. We already have a bunch of community features, like publicly indexable knowledge base from threads, public-to-internet channels -- which are being used by many OSS companies (list on home page). Teams is a different product. Companies who use Teams are there because they have tight integrati…
We switched from Slack to Teams because we were going all in on Office 365 and Teams is included.... so why pay for Slack? But, honestly, we don't use a lot of the integrations, except for maybe the Sharepoint access when adding attachments which is, admittedly, pretty nice. We also don't use Threads in Teams. Things got lost trying to jump back and forth between the "Chat" tab and the "Teams" tab. So now, we just cr…
We'd surely look into Teams integration at some point. Though, I'm not sure how many takers would be there for Teams/Struct integration. My perception is that Teams users tend to be medium-to-large businesses who are tied to Microsoft Office, and would be very hard to sell to. I might be wrong.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#130Earlier quoted context omitted.
Founder of Struct here. I looked at Zulip before starting Struct. And I'm sorry -- I don't think it's the same. Threads in Zulip are really sub-channels, and the idea of a unified feed like "All Threads" doesn't exist -- at least, that was my perception of Zulip. And just looking at the site right now, it feels the same as before. I could be wrong. Struct is different. It's a reimagination of what a chat platform wou…
> the idea of a unified feed like "All Threads" doesn't exist I believe it does. You get a feed of all messages; and still organized by a topic, quite conveniently. I don’t use it, though, since from anywhere in GUI I can immediately jump to the next unread message, irregardless of topic or stream, simply by pressing “n” on keyboard (preceded by Esc if I happened to be typing; my draft is saved reliably).
- https://zulip.com/help/inbox