Having a density of competent people helps a lot and avoids things like this.
Show HN: Struct – A Feed-Centric Chat Platform
61–70 of 143 posts
Re: Show HN: Struct – A Feed-Centric Chat Platform
#62Earlier quoted context omitted.
Looks cool, but unfortunately another company that treats single sign-on as a luxury feature, not a core security requirement by jacking the price way up to get SAML support. Companies really need to stop doing this.
Single-sign-on is a large and painful feature to develop, that most people don't need, and that the companies that need it are willing to pay for. It's the perfect candidate for a higher-tier pricing structure. This makes much more sense than tiering on a feature that everyone needs.
SSO in 2017? Sure. In 2024? No way.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#63BTW I think this is brilliant because summarization is one of those things where AI works really well. Out of curiosity, I wonder if you could share some of the tech you used? Any dgraph or badger under the hood by any chance? :-) How about hosting? Big three or something else? K8s or no? Elastic Search? etc. Edit: Also curious if struct is supposed to online scrape slack/discord or become and standalone chat app now…
The Stack is this:
- Go - Postgres - OpenAI (biggest bill producer is this) - React / Next.JS - Loops.so for Emails - Imgproxy for handling images - Microsoft E5 for embeddings (not OpenAI) - Typesense for Search (also a user of Struct) - Figma (design) - Framer (website) - Server on Hetzner
Badger wouldn't have made sense to use instead of Postgres. I'm thinking of using Badger for other purposes. I do use ristretto and roaring bitmaps a lot internally.
Struct has a very nice integration with Slack. So, you can actually use Struct as a Slack interface. Essentially, your peers can be using Slack, while you could responding to them via Struct - think Superhuman for Gmail.
We have a good integration with Discord too. Both are being used by OSS companies to generate public knowledge bases from their Slack/Discord conversations.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#64Earlier quoted context omitted.
Yeah, good point. We have data from orgs who're using Struct. Short story: It's significantly cheaper compared to Slack. Struct charges 9.97 per month. And we only charge for AI usage, not number of users or threads or chats. Base price comes with 200K tokens free, which is enough for most small orgs, if they're only using it to generate thread titles and summaries. In fact, that's the average token usage by Typesens…
Awesome. Thanks. Great work. I signed up to try it out and use it personally before deciding for the other team/company. I would really wish to retain org name to 5-characters. ;-) Update: I can actually change the URL from inside Struct. It would still be nice to be able to choose that during the sign-up steps.
You might have found a loophole, ser. Enjoy the exploit!
Re: Show HN: Struct – A Feed-Centric Chat Platform
#65Any plans on a web client?
app.struct.ai works very well as website. I use both the website and the desktop app simultaneously often.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#66Countless tools have promised to highlight "what's worth my attention". None of them have worked for me or my team. What's different on Struct? A few questions I jotted down while watching the video on Struct's landing page: 1. the concept of channels seems to be important on Struct as channels are the starting point of threads/feeds. Could you clarify the concept of channels on Struct? Is it just a concept to group…
In the time you wrote this interview you could also just have tried the app yourself
Re: Show HN: Struct – A Feed-Centric Chat Platform
#67Countless tools have promised to highlight "what's worth my attention". None of them have worked for me or my team. What's different on Struct? A few questions I jotted down while watching the video on Struct's landing page: 1. the concept of channels seems to be important on Struct as channels are the starting point of threads/feeds. Could you clarify the concept of channels on Struct? Is it just a concept to group…
In the time you wrote this interview you could also just have tried the app yourself
I think that rather avoids one of the best parts of hacker news - getting the vision/justifications from the creator directly.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#68> We’re forced into clicking through multiple channels just to catch up on our team’s latest updates. Combine this with the always-growing list of new channels, and information starts to get really scattered.
This is one of those problem statements that just doesn't resonate for me at all. I really like things separated into the different buckets so I have a good idea how to find it again later.
The idea of combining stuff into one feed is kind of a nightmare for me.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#69> We’re forced into clicking through multiple channels just to catch up on our team’s latest updates. Combine this with the always-growing list of new channels, and information starts to get really scattered. This is one of those problem statements that just doesn't resonate for me at all. I really like things separated into the different buckets so I have a good idea how to find it again later. The idea of combining…
It's really about choice.
In Struct, you can create custom feeds, which can filter threads by channels / users/ tags, etc. You have that choice. In Slack, every one of these entities (and permutations for DMs) stands alone. It's set in stone, unchangeable.
That itself is a big win.
In fact, feeds are everywhere. That's how we consume almost all internet. RSS, News, Facebook, Twitter/X, Instagram. Feeds scale, they are powerful, they work. Instead, Slack has us jumping around channels and DMs for drips of messages, playing Whac-A-Mole.
Re: Show HN: Struct – A Feed-Centric Chat Platform
#70This is one of the first Slack competitors that has caught my attention. I really think you're on to something here. I have one thought after watching the video (other than a generally positive feeling about it): It feels, somehow, less personal. Where Slack rooms felt like digital _rooms_, this gave me the feeling of an office bulletin board. I'm imagining being a new employee at a company that is fully bought in on…
Founder here. Jason (OP) and I think about this a lot. The balance of cluttering everyone's names on the left panel, v/s making it feel like you're in the same room as these people. If you look at feed based platforms, they tend to get very asynchronous (almost forum like). And so our design for the real-timeness of the feed was to emphasize the fact that you're in this room with these people, and they're talking rig…
yeah, you've hit it on the head – I think what I felt was missing in the demo was a feeling of presence. a hard thing to capture. anyways, awesome job and good luck!