Live data from Hacker News

Show HN: Struct – A Feed-Centric Chat Platform

struct.ai

91–100 of 143 posts

Re: Show HN: Struct – A Feed-Centric Chat Platform

#91
post #89
post #86

Looks great, but hard to make the swap from slack without apps/bots/api. I'm sure you thought about it, but a slack-compatible bot api will probably really help with adoption.

You looking for this? https://struct.ai/struct-for-slack

Slack has a big app marketplace, which is helpful. Do you have plans to add something like that to Struct?

Re: Show HN: Struct – A Feed-Centric Chat Platform

#92
post #89

Earlier quoted context omitted.

You looking for this? https://struct.ai/struct-for-slack

Slack has a big app marketplace, which is helpful. Do you have plans to add something like that to Struct?

Yes. We'd be documenting Struct APIs. And also we want to identify the top 5-7 most popular Slack integrations, and build them ourselves for Struct.

Re: Show HN: Struct – A Feed-Centric Chat Platform

#93
post #88
post #45

Earlier quoted context omitted.

You could create a focused custom feed. For example, I have one for "tasks assigned to me". That's what I set to when I'm focused working. That's the beauty right -- you can control and filter what you see. As opposed to channel based interactions, where your boundaries are set in stone on channel creation.

But I don't currently use Slack as a task manager and don't want an unstructured task manager with no due dates or tags.

Yup. That's the point I'm making. Slack is used as ephemeral messaging system, a knowledge void. Struct aims to proves that more is possible.

Re: Show HN: Struct – A Feed-Centric Chat Platform

#94
post #85
post #60

Earlier quoted context omitted.

Good points. Let me try and address those. 1. Channels for Struct are just groups of people. You engage with a channel, just like you'd engage with a user. You start a thread, and then mention users or channels to define access for that thread. You don't go to a channel to chat. 2. A thread can only take so much space on the feed. The height per thread is fixed. So, both the threads you mentioned could be in the feed…

> You can also select a bunch of chats in a thread and fork them into a new thread. We'd maintain links between threads. Coming soon. Just want to chime in and say this is an essential feature IMO, I hope it’s prioritized.

Absolutely! We already have one chat message fork working. Backend supports multiple message forks as well. So, very close.

Re: Show HN: Struct – A Feed-Centric Chat Platform

#95
post #28
post #25

This is killer. Love the idea of focused threads while still having channels. Really like the design of everything, too. Only question: long-term plans? Before I commit a lot of data to something like this it'd be good to know it's not a VC flip and dump.

Manish, founder here. We intend to keep Struct running. Struct is built with a small of 3: Backend, Designer and Frontend. It's not that capital intensive. We have a roadmap of features that we're excited to get to, combining both teams and community usecases: - Enable audio / video calls, webinars. - Various spam control systems for community. - Improving the AI bot and recall, making it cheaper to run. - Index the…

3 people for this product is highly impressive.

Re: Show HN: Struct – A Feed-Centric Chat Platform

#97

runForThread.executeReq.Get.messages: executeReq.client.Do: Get " https://api.openai.com/v1/threads/thread_*******/messages?li... ": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Hope one day new products don't need to depend on OpenAI...

I'm honestly considering sometimes to ban .ai domains on my router until the whole thing has gone back to normal.

But seriously, this thing actually looked very interesting until the point where I read "... and AI" :-/ Guess I'm not the target audience.

Re: Show HN: Struct – A Feed-Centric Chat Platform

#98

runForThread.executeReq.Get.messages: executeReq.client.Do: Get " https://api.openai.com/v1/threads/thread_*******/messages?li... ": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Hope one day new products don't need to depend on OpenAI...

Arr.. we should clean up the error messaging a bit. Not to hide OpenAI, but just make it appear nicer.

I like OpenAI. GPT4 works really well. Some others we tried were cheaper, but the quality wasn't as good.

Re: Show HN: Struct – A Feed-Centric Chat Platform

#99
Congrats for your product !

BTW: I'm old enough to remember the "forums' days"... and actually, it really seemed to me that you just rediscovered forum (you know... threads that are bumped when there an update)

The only major differences I saw was:

- the UI is more "chat-like" / "facebook-like"

- forums where statically structured by an admin... but it looks like there no real way to structure your threads in folder or things like that (important on big orgs with lots of different subjects concurrently)

On the other side, mails may be (more or less) structured by "conversation" (sadly it's not a strong standard so not reliable) and conversation may be structured by personal folders

- there's "AI" and that's quite tiring these days. I see the point of having a dynamic summary of a thread... but

    * either your threads are 'chat-like' so with simple content... and no summary is needed

    * or your threads are 'mail/forum-like'... and I'm not sure how it will work (sincerly)

Sooooooo... I'm not sure to know what to think about it. Is it "just" a marketing 'chat-like' with 'AI buzzword' app ? Or did I miss something that make it really fundamentally different from forum threads or email conversation ?

Re: Show HN: Struct – A Feed-Centric Chat Platform

#100

Congrats for your product ! BTW: I'm old enough to remember the "forums' days"... and actually, it really seemed to me that you just rediscovered forum (you know... threads that are bumped when there an update) The only major differences I saw was: - the UI is more "chat-like" / "facebook-like" - forums where statically structured by an admin... but it looks like there no real way to structure your threads in folder…

> I see the point of having a dynamic summary of a thread...

That was a really cool feature in Discord, for a while: The AI always completely missed the point of the discussion and made hilariously awful summaries that provided entertainment for hours.

Post reply on HN