HN user

boraturan

53 karma

Founder,Copo

https://copo.st https://x.com/_boraturan

Posts7
Comments44
View on HN

Solo/indie dev here.

Created ‘Shopify for Social Media’.

Create your own Tiktok/Instagram app, white-label, embedable. Your app, your brand, your domain, your icon, your rules…

For creators, communities and businesses.

https://app.copo.st Https://virksocial.com

It is basically white-label Tiktok/Instagram native apps, but written all in web- including camera, native-like mobile feature/gestures/animations…

PWAs enable the same native full screen experience while bypassing appstore tax/rules.

For native apps, I have a React Native shell app that embeds a webview so I can create native Appstore/Googleplay binaries ready for publishing. With the new Expo CNG architecture, I can automatically create native apps binaries from console. https://apps.apple.com/us/app/copo-st/id6737266643?platform=...

You can embed apps/feeds/posts/profiles in web pages and native mobile apps(webview). So this creates a distributed social network on open web with various distribution/monetization/aggregation/commerce models.

Exploring to make this user-owned platform/apps.

great article, couple of questions

-storing timestamp for each field (user:name) by default seems costly, timestamp can be stored on main key(e.g. user), curious on the thinking.. -is timestamp 64bit? do we need miliseconds? -what is your sharding architecture, in terms of rage queries -are your global search indexes on this architecture

Web3 Social Media - Alvin5.com | Web | Remote | https://alvin5.com

Developing “Web3 Social Media”

Open and community-owned (on-chain DAO) social media platform initially focusing on short-form video and web3 community. Also available as a white-label, embeddable solution for businesses/startups. Think open Tiktok/Instagram, for people and businesses.

DAO with governance/ownership/incentive token.

I would love to meet with people interested in building this.

- Web/WebApp (Think developing Tiktop/IG as a webapp) LatestWebArchitecture/Browser/React/PWA/SW/Video/Canvas/WebRTC

-Backend - DevOps, Scalability, Distribution, AWS, Node, .NET core…

-Protocol/Tokenomics/Solidity/Web3/DAO/Eth/OpenZepplin/Compound Dao Stack

Web3 whitepaper coming soon.

I am the founding engineer, bora.t@alvin5.com Subject:Guild

FFmpeg to WebRTC 5 years ago

I am also exploring the webrtc(ingest)-to-llhls. FFMPEG doesn't seem to support llhls now, as it requires web server intelligence. For the webrtc, mediasoup is nice being node based.

Google has a "Web Stories" initiative. YouTube shorts might eventually get connected to that, videos appearing on Google Search creating a decentralized stories distribution/search/ad network. (Disclamier: founder@ alvin5.com where I am working on the same concept). I agree that shorts in the youtube app context is awkward, if they get traction, might spin out.

I am really interested in how these analogies would appear in different word embedding methods (Bert..), or different implementations of word2vec.

As to different implementations of word2vec, I am still not satisfied why the original code uses two separate embeddings for target and context words. It could use shared embedding layer.

Also for the layer above the sigmoid layer (Dot product), why is cosine similarity not considered for calculating the vector similarity.

I have searched these issues and not found detailed comments. I have created word2vec embeddings with shared embedding layer and cosine similarity. The vectors seems similar to the original code but deciding on which one is better, needs more work.

Google announced their version of Material React (Alpha) at IO. "Material Components for React (MDC React)" Curious to see how it plays out with Material-UI. They should support Material-UI.

We are all built on .net core (alvin5.com)

We have had issues with Visual Studio and Tooling between betas, but now the platform has matured considerably and with the expected release of .net standard 2.0, I would say you can go for it for prod. C#/Editor/Tooling/Access-to-low-level is better than any platform I habe used. The new MS with the open/Azure/AI investments also seems ok. We feel like we are fit for the next 10 years with .net core.

Docker Swarm is a great idea. But I think that with Swarm, I don't have to deal(and see) with nodes (server instances). I would be able to just run and scale services(containers). Scaling with nodes should be supported and done with AWS and Azure behind the scenes.

EC2 is not a Docker solution. EC2 Task&Service definitions are not Docker Task&Service definitions. So this basically ties to with the AWS platform. You can not move your Docker infra between AWS and Azure. Docker for AWS is the way to go, but I believe it could be enhanced greatly. I also think that AWS does not seem to support Docker Swarm very eagerly, because I think AWS still did not figure out to charge Containers, they are still charging Nodes.