A Personal API
blog.webb.page
blog.webb.page
https://en.wikipedia.org/wiki/Solid_(web_decentralization_pr...
The predecessor to unwalled.garden (fritter.hashbase.io) also bears some resemblance to the author's Socii. It would be neat to see Socii "rebased" onto Dat and Fritter, but also made to work for legacy plebs still on the legacy web, and then trying to organically grow "A personal API" out of that, instead of the sort of top-down, second-system thing that happened with unwalled.garden.
As far as I can tell right now the author is mostly working on UI/UX improvements right now, what gives you the impression that he's yak shaving?
Whenever I feel like it I can very easily extend this platform by just writing a new javascript file. Currently there are thinks like
* An endpoint to show my currently playing track on spotify
* An endpoint that renders one of my todoist lists as html (my whislist)
* A reporting module that receives webhooks from different backup scripts and sends me a report by mail every day
* Move new songs from a spotify playlist to an archive playlist after a few weeks to keep the playlist "fresh"
I always wanted to create a bigger project based on my learnings but I'm not yet completely happy with the technical implementationWe have a lot of new tooling coming soon, so if this is of interest to you please reach out! You can e-mail me directly: keith at (our domain).
The case of updating your website again is pretty specific and niche... the majority of people’s personal sites these days are their FB/IG pages. And this does nothing to create APIs for locked down 3rd parties like WhatsApp or Messages.
Rather than being a simple wrapper / bridge, is there the possibility of doing something more new that isn’t possible with a variety of SDKs? Like a personal API into my health or routines, that either creates inferences or is able to intelligently control a variety of devices/services?
Until then, this personal API concept is the best thing I could think of.
Yes, we could have a VPS per person being our fixed point on the Internet (and a fixed address...) but wouldn't it be better to return to the original idea of the Internet with devices always connected and routable? It might take an overlay network such as a DHT-like thing, it might be something IPFS or Torrents eventually lead to, but the end game is "everyone always on-line."
The chrome codebase mostly help me for the multi-process IPC communication and reusing the UI compositor for UI and Web.
I wont say much more, because i want to keep some idea of novelty for when i launch this here on HN.
For me is what a mix of what a Browser + App platform should be, with the idea of people owning their data, devs distributing without centralized control, and without forcing you to use some hardware or specific OS.
Yes. However, I'd still like to do something in the meantime. There's no telling how long an overlay network would take to implement and release.
Even moving to the cloud cannot seem to shake its networking presence.
:(
The biggest problem as I see it is cost. While I might want to have this for $60/year (or own my own hardware for a little more), the vast majority of people (whose adoption you need), don't want to pay for this.
There are countless other UX and technical challenges, all interesting and largely tractable.
But I'm not sure how to deal with the cost problem. It underlies the failure of essentially all anti-centralization efforts.
Everyone wants free but "free" costs more than money. It's quite the pickle.
If you have a few friends who will seed your page for you out of the goodness of their hearts, I imagine your site will have pretty good uptime without anyone having to buy a VPS.
In addition to providing you a profile/bio, it can pull in your content from various social media sites into a single central API for you to use.
Here are some examples https://beepb00p.xyz/mypkg.html#examples . (the post is in draft stage and a bit rough, I will share it once it's done)
And link to the package: https://github.com/karlicoss/my
Think of an inbox for all your starred/saved convos on discord, slack, etc... and all starred emails on gmail... and saved reddit comments or threads.
Then being able to schedule maybe once a month posts to slack / reddit job boards that you're 'forhire'... And being to see all messages/replies from reddit and search across all types of messages.
Do you have qualms with that line? IMHO we provide content for a number of social networks with questionable returns. Yes we have community and can connect on shared beliefs and learn something new but lately it seems that we'd be better off tending to our own spaces and sharing with the larger networks should we choose to do so.
I intend to write more and post here so at least for future posts the convo can be on the content.
There's no world in which you can: make your website scroll horizontally, disable horizontal scroll, make vertical scrolling actually scroll horizontally and have users be okay with it.
https://www.pressreader.com/canada/toronto-star/20191202/pag...
What's your preferred method of input and platform?
If you disable Javascript, it's a lot more consistent because the Javascript is only there to swap vertical scrolling for horizontal. Without JS it's still horizontal scrolling, but you scroll left/right the same way you would expect to, and for the most part the page just handles it -- it'll even resize correctly as you change the browser height.
The quick, dismissive comment I could give is that I don't think I like this as a user, so the author should just give the entire thing up. But it's kind of interesting, and I can see why someone might want to pursue a strange effect like this, and there might be ways to make it more tolerable. I think overriding vertical scroll controls was a mistake; maybe it's better to lean into the fact that it's horizontal, use pure CSS for the core, and only use Javascript to make horizontal scroll speed a bit faster or add shortcuts or something. Let the browser handle scrolling horizontally.
Cool or not, the effect seems to distract from the content though. Since the CSS is fairly nice and clean, something simple like a button that toggled between horizontal/vertical modes would not require overriding many rules, and would head off a lot of these kinds of comments.
It's using a few overlooked properties like CSS columns that get around needing to use JS to dynamically calculate height, and it's using Flexbox to get rid of any weird padding issues. I haven't tested, but I assume this will work in pretty much any modern browser (and even a few older ones like IE11) and degrades wonderfully when Javascript is disabled. It's screenreader accessible, it doesn't require messing with the HTML layout. It's some really pretty CSS.
Makes reading such pages much more comfortable on a wide screen like my 17" HP Omen.
Or an extension, thereof.
So it isn't a "server" that is running that a webapp talks to, instead, it is that the webapp talks to your "localhost" or similar (browser extensions are easier).
Then the apps are decentralized from the start.
We're already doing something similar (alpha) with http://party.lol and in the http://gun.eco (our decentralized Open Source Firebase alternative) community.
<comment type="annoying">Works for me.</comment>
Roll the mouse and I get a vertical scroll.
Linux whatever, firefox=latest pushed update from whenever
I should add a button and/or keyboard shortcut to disable the horizontal scrolling.
Thanks for adding other options for scrolling!
Seriously, do so few people ever say, "hey, honey, come here for a minute and try something for me..."?
(On the off chance that the page author comes to their senses, or a different URL is offered, the current link goes to a page with horizontal scrolling that will wear out your scroll wheel if you try and use it to navigate. One tick of the wheel = one pixel of movement.)
I'm gonna be adding a toggle for visitors who wish to do away with the polarizing scrolling.