Show HN: I made a solar-powered, ePaper photo frame https://ift.tt/3r7vXIw

Show HN: I made a solar-powered, ePaper photo frame Looks like this year ePaper projects have been popping around[1], so this is mine. I made a photo frame with the intention of having a record of my family's history that can potentially outlive me. Knowing the challenges of long-lived digital projects, I consider this a moving target that will go through several iterations, but the first version showed encouraging results. I wonder if anyone else is interested in having something like that in their living rooms. More details: https://ift.tt/2Wr1O96 [1] https://ift.tt/33w5ngR https://ift.tt/3a0eS9D and more recently https://ift.tt/2W8BSyJ December 18, 2020 at 04:56AM

Show HN: Runneth is a bookmark manager that forces you to prioritize https://ift.tt/2J2GMdK

Show HN: Runneth is a bookmark manager that forces you to prioritize https://ift.tt/3r4NKjr December 18, 2020 at 03:54AM

Show HN: Christmasvillage.io https://ift.tt/34pOK8i

Show HN: Christmasvillage.io https://ift.tt/2KErPPC December 17, 2020 at 10:03PM

Show HN: Turn your un-used domains into Reddit-like clones https://ift.tt/2WwCApv

Show HN: Turn your un-used domains into Reddit-like clones Hey there, HN people! I would like to share with you a little tool I've been working on this year. It's called Newsy https://www.newsy.co Problem I have more than 30 domains that I've bought over the years. I plan to (eventually) do something with them, but meanwhile, they are un-used and just sitting there. I want to use them somehow. I know there are a few impulsive domain buyers out there! :) My Solution I wanted to turn my un-used domains into something useful without me having to do too much work. So I created Newsy https://www.newsy.co It turns your un-used domains into a Reddit-like content aggregator. It automatically crawls the web based on the keywords I provide (or RSS feeds) and creates a Reddit-like content-based website. Over the past few months, we've added following features - memberships, voting, comments, themes, automated newsletters, integration with other tools & monetization by bringing your own ads. Examples Check out some of mine and some of other users who have their domains on Newsy https://ift.tt/34pQe2d https://ift.tt/3mtuhpf https://ift.tt/2Ke3yjn It's still early days for us, but I'm glad that I am now using most of my 30 un-used domains for somewhat interesting things and everything is pretty much automated so I don't really have to do much work on them. Would love for you guys to check it out! Thanks! December 18, 2020 at 03:13AM

Show HN: Cimbar – File transfer via color barcodes and the Android camera https://ift.tt/3gYAS9W

Show HN: Cimbar – File transfer via color barcodes and the Android camera https://ift.tt/3r9vWDK December 18, 2020 at 01:14AM

Show HN: UseAuth – add auth to React apps in 5min https://ift.tt/34EcBBl

Show HN: UseAuth – add auth to React apps in 5min https://useauth.dev/ December 17, 2020 at 10:09PM

Launch HN: ShareWith (YC W21) – Easily share internal websites securely https://ift.tt/3mn7bAA

Launch HN: ShareWith (YC W21) – Easily share internal websites securely Hi HN! We are Jake [jakemoshenko], Joey [jschorr], and Jimmy [jzelinskie] of Petricorp ( https://petricorp.io ). We’re building authorization services that reduce the overhead of adding a complex authorization policy to your apps and internal resources. We’ve been building developer services and tools for over 15 years, and throughout that time we’ve repeatedly run into the problem where whatever authorization solution we pick for a new service at first, turns into a major limitation later down the road. Relational database backed libraries like the ones found in popular web frameworks have proven inflexible and a scaling bottleneck, and distributed policy engines such as Open Policy Agent [1] turn the evaluation scalability problem into one of distribution and consistency. In the past, we’ve even had to shelve product features because the effort required to safely alter the policy and migrate the data was higher than the value of the feature! To solve these problems we’re building a multi-tenant SaaS platform based on Google’s Zanzibar paper [2], which allows for flexible tenant-defined policy, at planet scale. This new platform offers the consistent experience of a centralized auth solution, with the scalable nature of a distributed system. By taking on the operational overhead of running the platform ourselves and providing users with client libraries that reduce complexity, we're shouldering the burden to enable authorization decisions that are fast, accurate, and accessible across applications. Today we’re launching our first product integrated with that platform: ShareWith ( https://sharewith.io ). ShareWith brings Google-docs style sharing to anything that you can run behind a reverse proxy or authenticate with OpenID Connect (OIDC) [3]. We think ShareWith is a great alternative to VPNs, which are hard to set up and configure, hard to federate access to, and don’t allow for fine-grained permissions or sharing with people outside of your organization. We’ve already found a few interesting uses of the service: We secure traffic to our own internal dashboards by running them behind OAuth2 Proxy [4] instances configured with ShareWith. Other companies are using it to avoid building the boilerplate for adding sharing and permissions into their products entirely! Because organizations in ShareWith are billed per unique participants that have had resources shared with them, the pricing model shouldn't inhibit protecting new things. Adding another service or adding an existing user to a new service doesn’t impose any additional cost. ShareWith website protection is implemented using an extended OIDC provider. Normally, an OIDC provider is responsible only for returning an identity. Our provider will also match up a given access request with a pre-designated authorization requirement, and then check that the requestor has had that access shared with them. If not, we will pause the authentication flow and give them an option to request access, which notifies the owner: a familiar pattern to anyone who has ever had to request access to a document. Underneath the hood, we are making dozens of requests to our platform, from writing and updating policy, to the individual access control checks. To answer an authorization check request, we first build a graph containing edges and nodes from both the policy and the individual relationships between users, groups, and resources. We then take that graph and attempt to find a path from the resource to the user. Once a path is found, or no such path can be found, the service informs the caller of the decision. Thanks to the distributed nature of the service, these answers are quickly computed by building and evaluating subgraphs in parallel, and each piece of data is replicated to ensure reliability. Try out what we’ve built so far by following our guide ( https://ift.tt/2KAvfCV ) to protect an example service. If you want updates from the team, be sure to sign up for our mailing list ( https://ift.tt/2WqBP1i ) or follow us at https://twitter.com/petricorpio . If you're interested in integrating with our underlying authorization platform, you can reach out to us directly at hn@petricorp.io. We've learned a lot building ShareWith, but now we want to hear what you think about what we’ve built so far, and the direction in which we’re heading! We’ll be hanging around in the comments today if you have any questions or feedback. [1] https://ift.tt/2IKgY09 [2] https://ift.tt/2VtBY3n [3] https://ift.tt/2a1AmEk [4] https://ift.tt/2QYtPm1 December 17, 2020 at 10:01PM