Live data from Hacker News

Show HN: Sora, Personal Publishing Platform

sora.city

51–60 of 62 posts

Re: Show HN: Sora, Personal Publishing Platform

#51
post #43

Nice one! However I'm not trying/paying for a service that its own terms and conditions look like unfinished business. Sora is "a company"... Hmm. No basic details who's behind it. Then there's this "Our servers are located in." In where exactly? Lots of questions probably.

> "Our servers are located in." In where exactly? This is actually hilarious though. Terrible for a ToS, but hilarious.

Posted our app here for technical feedback mainly, but appreciate you looked through our ToS. Will go over this part with our lawyer.

Re: Show HN: Sora, Personal Publishing Platform

#52
post #50

Earlier quoted context omitted.

What’s the point of this post? The GP asked if they plan to sell user data, they respond no. Did you want them to just not respond? What?

I would hope they would respond with how they can -prove- data can never be sold, by having accountable cryptography, etc.

At this point, there is not much to e2e encrypt--as most of the time you're posting for the internet to see. With more personal collections coming, we'll introduce encrypted content as well.

Although this has nothing to do with selling users data—will work on our tos to communicate our expressed intents more clearly.

Re: Show HN: Sora, Personal Publishing Platform

#53
post #44

> Restricted. > Sora isn't available in Belarus, Hungary and Russia. Why these countries in particular? I guess it's about having oppressive/authoritarian regimes and being in Europe, but why to restrict it that way? Edit: or perhaps it's because of the war, but Hungary doesn't seem to be involved as much. Though maybe I missed something there.

List is longer, copy was outdated.

It's more like a principle question than anything else—we know it won't make a dent in the world, but we aren't comfortable providing service for countries that openly pro-war.

Re: Show HN: Sora, Personal Publishing Platform

#54

Earlier quoted context omitted.

Also curious about your tech choices. Why did you opt for Supabase instead of headless CMS like Netlify? Why did you opt for Atomic CSS instead of Tailwind?

> Why did you opt for Atomic CSS instead of Tailwind? I've been using Tailwind since 2019, and I would recommend Tailwind to anyone, but I still don't understand why people always try to get others to use it over something else. Is something wrong with Atomic CSS?

Maybe the "atomic CSS" part wasn't very clear—we just meant the concept of atomic CSS.

We love tailwind as everyone else in their right mind, but we're using our own flavor of the concept I started years ago: https://fractures.dev

On the why: We plan on having a lot of novel, one off interfaces, which TW isn't just right for. CSS is. We also don't have an frontend scaling problem, as I'm the sole developer here.

Re: Show HN: Sora, Personal Publishing Platform

#56

Is there any reason this is dynamic and not static? It looks like this could be: Creators use a dynamic system for creating/publishing Readers consume a static website that’s is generated incrementally upon create, edit, etc of a writer.

Reading is cached 95% of time for now, which is as fast as static. ISR for n users is more complicated (at this point at least) than just letting edge cache.

Re: Show HN: Sora, Personal Publishing Platform

#57
Great job building this! I can tell it took a lot of time and work. How long, from idea conception to this Show HN, did it take you?

And how did you determine whether there would be a market for this? Was it more something you built for yourself, or did you have some feeling there would be an audience for this on HN (or elsewhere)?

Re: Show HN: Sora, Personal Publishing Platform

#58

Great job building this! I can tell it took a lot of time and work. How long, from idea conception to this Show HN, did it take you? And how did you determine whether there would be a market for this? Was it more something you built for yourself, or did you have some feeling there would be an audience for this on HN (or elsewhere)?

Thanks! I had a working version a few years ago, but started a complete rewrite 6-ish months ago, mostly working on weekends.

> Was it more something you built for yourself, or did you have some feeling there would be an audience for this on HN (or elsewhere)?

It was 100% for ourselves at the start, but figured others would love it too, so second time I built it to scale. HN is not especially our target audience, but wanted to show it off, stress-test and get at least some outside feedback. :)

Re: Show HN: Sora, Personal Publishing Platform

#59

Earlier quoted context omitted.

My personal blog costs me about $1.30 a month, including my image cdn. Why is your software worth $100+ a year to me? I can go with Ghost and save $1 a month over your price.

I’m curious, how many megabytes of image are you hosting ? Looking to run my blog with static hosting similar to this.

I use digital ocean. The minimum buy in is $60/year, and it gives you 250gb of storage and 1tb of bandwidth, across as many spaces (ie buckets) as you want.

I also use this as my "share" site, and for a bunch of other uses, so my ~2gb of image hosting is just a fraction of that yearly $60.

The major catch is they don't offer dynamic image resizing. I only resize my images to a few standard sizes and just use a small script to resize + upload in one shot.

Re: Show HN: Sora, Personal Publishing Platform

#60

Earlier quoted context omitted.

> Why did you opt for Atomic CSS instead of Tailwind? I've been using Tailwind since 2019, and I would recommend Tailwind to anyone, but I still don't understand why people always try to get others to use it over something else. Is something wrong with Atomic CSS?

Maybe the "atomic CSS" part wasn't very clear—we just meant the concept of atomic CSS. We love tailwind as everyone else in their right mind, but we're using our own flavor of the concept I started years ago: https://fractures.dev On the why: We plan on having a lot of novel, one off interfaces, which TW isn't just right for. CSS is. We also don't have an frontend scaling problem, as I'm the sole developer here.

> We plan on having a lot of novel, one off interfaces, which TW isn't just right for.

I think you misunderstand Tailwind, but there's nothing wrong with your technology choice. :)

Post reply on HN