Post

been working on a open source replacement for bento.me (which is shutting down) using your bluesky pds to save your data. still very much work in progress, but can be tried it out here (editing your blento currently desktop only): blento.app source code (svelte ofc :P): github.com/flo-bit/blento

53 reposts425 likes

This might be a bat shit crazy idea but... you could just click on the word that says Bento.me, it's called a link and it takes you to other places like the Bento page so you can see what it's all about. The interweb is full of links that take you places, it's crazy! Technology is nuts! 🤯

I did already and it turns out it's pretty useful actually! I found out what it's all about just by clicking the link thingamajiggy. I'm pretty sure the dev linked to Bento so they didn't have to explain what it is to every dimwit with poor comprehension skills.

bento originally describes a type of layout where you have different sized boxes in a grid (the name comes from japanese bento boxes, that have different sized compartments). that's been a trend for a while in web design and bento.me just made it easy to create your own website using that layout

but there's lots of other websites that use that layout (apple probably made it as famous as it is now, see image), i really like nevflynn.com as a nice portfolio example too, so bento.me == linktree/personal-website-creator but in a bento grid layout

Thanks for trying it out, I left you a comment on the github issue, with the missing instructions :)

how are you handling schema evolution? been running into interesting constraints around versioning custom lexicons when the data structure needs to change but old records still exist.

tbh i havent really thought about it yet :D (haven't even really defined a schema...) so far less than 20 people have tried it, so I think it should still be fine to switch lexicon for a while (maybe with some tool that converts old records to new ones) but at some point its just gonna be chaos :P

Yeah, atproto made it very easy to build too without having to worry about all that user accounts and database stuff :D planing to add lots more cards for different atproto projects too (recent bluesky post, listened music from teal.fm, your leaflets, projects on tangled, events on smoke signal,...)

Muito legal, obrigado pra testar :) ja tou vendo algumas coisas q vou tentar melhorar! vc viu alguma coisa q nao gostou/tem sugestaos? (e desculpa pelo meu portugues ruim :P)

funny how sometimes you avoid doing something for days that then turns out to be less than 30 minutes of work 😅 (though I do wish there was an option to just request `app.blento.*`) that looks a lot nicer now...

Will be trying to put this to use for a.roomy.space asap, awesome stuff 🤩👏 What makes the site editing desktop-only for now? Not a problem, just wasn’t expecting that order of device support from a Svelte app.

The main problems are not svelte here, but 1. your layout can look different on mobile and desktop, there's a button on desktop to show the mobile view, but showing the desktop view on mobile is a lot harder 2. my dragging+bento grid implementation is very clunky right now and broken on mobile 😅

Well, I'm not the best person to explain how that works (I'm just using it to build fun website :P), but the way i understand it: - bluesky is one of (potentially) many apps that run on top of a protocol "at proto" - in that protocol everyone has their own little server (personal data server = PDS)

- you *can* totally selfhost your PDS (see github.com/bluesky-soci...), but you can also let someone else do it for you (most everyone on bluesky lets bluesky host their PDS), but even if someone else does it for you, you can always move your PDS somewhere else (using some cryptographic magic, ...

... that I don't understand either ^^), so you always have control even if you dont selfhost - regarding needing a key for reading: currently basically everything you do on at proto is public by default (excluding DMs and bookmarks afaik but those are actually saved outside of at proto), ...

Yeah I took a look at that and might still adopt it (don’t tell anyone but i havent actually specced a schema yet, basically just acted like my records are random json files 🫣), the main @standard.site schema did look a bit *too* blog format specific though, but havent explored it much

Maybe bento blocks could be grouped together in the content of a site.standard.document though 🤷‍♀️

also first time i'm using @microcosm.blue (for fetching the most recently updated blentos) and love it, that's exactly the kinda thing i always wanted to make it easier to quickly build on top of at-proto