41–50 of 57 posts
They insist on microformats which are no use for any content other than html, in my case atom: https://demo.mro.name/shaarligo
Plz prove me wrong.
Becoming a "citizen of the IndieWeb"† seems to require you to be a web developer. Level 1 requires knowledge of HTML, or a CMS that exposes the rel attribute on links (is that common?). Level 2 requires specific CSS classes and... more than I can summarize succinctly here. And there's still Level 3 to go. It's hard to see this growing beyond web developers unless it's baked into other software as an incidental. † htt…
What would you think of an onboarding experience like at https://demo.mro.name/shaarligo/o/p/ac2gthz
This is cool! I'll be looking into adding webmentions to Kalaksi.com my rss-based social network. It makes perfect sense and is very much aligned with the "open web" I'm trying to help survive.
Since you want to use the open web standards, you probably have heard of the indieweb movement. They have been working in this field, have standardized a bunch of protocols, among which webmention is only one (see https://indieweb.org/graphics#Illustrations_and_Sketch_Notes) and are all about doing first. I think there's a lot more you can reuse from their work! Kalaksi could be a nice demonstration of what the openness could bring. In particular it seems Kalaksi could become a social reader (https://indieweb.org/social_reader). This is exactly what we need to remove the importance that siloed private social networks.
Small comment: it seems the planets don't have the in the header that allows the browser to detect the rss feed, so one can't use the page directly but has to copy-paste the link to be able to subscribe outside of Kalaksi
Earlier quoted context omitted.
it isn't opensourced... at least not yet. Hubzilla is different. Kalaksi is still centralized, but the content is fully open and readable from anywhere (via RSS). So you can publish/curate, and your readers dont necessarily need to use kalaksi to access it.
Oh, that's really sad. If i may, why would you consider developing software that's not free software? Also, why would you develop software to provide services for other users, that they can't selfhost if/when you're not longer hosting the service? That sounds like serious footguns/antipatterns to me, so i'm curious what's your rationale :)
Becoming a "citizen of the IndieWeb"† seems to require you to be a web developer. Level 1 requires knowledge of HTML, or a CMS that exposes the rel attribute on links (is that common?). Level 2 requires specific CSS classes and... more than I can summarize succinctly here. And there's still Level 3 to go. It's hard to see this growing beyond web developers unless it's baked into other software as an incidental. † htt…
I guess you're right for now. What would you think of an onboarding experience like at https://demo.mro.name/shaarligo/o/p/ac2gthz
Earlier quoted context omitted.
Oh, that's really sad. If i may, why would you consider developing software that's not free software? Also, why would you develop software to provide services for other users, that they can't selfhost if/when you're not longer hosting the service? That sounds like serious footguns/antipatterns to me, so i'm curious what's your rationale :)
Basically I'm not clear where to go with it (if I go anywhere :p), and perhaps offer paid accounts with more features (like hosting images, videos, etc). And yes, I know this is not mutually exclusive but I dont see the point of everyone installing their own kalaksi. Its not made as something you self host for your own content but as a central platform. If I ever abandon the project, for sure the code will go open, i…
Well that's part of the magic of free software. You may meet people with who to figure it out on the way ;)
> I dont see the point of everyone installing their own kalaksi
Have you ever lost an account/service due to a service provider shutting down? If so, you probably see the point.
> Its not made as something you self host for your own content but as a central platform.
Too bad, the world truly needs better planet/aggregator tooling. The existing tools have mostly not evolved over the past decade.
> for sure the code will go open, if not before :)
i'll keep an eye open! :)
I like the idea of aggregating mentions from around the web on my personal static site. Ideally I would want to always have the most recent data, and not expose my site in a way that could be hacked. These are the implementations that come to mind: - re-render entire site on receipt of new mention (live data, but dangerous) - re-render site on a schedule (less dangerous, nearly live data) - fetch mentions client-side…
> not expose my site in a way that could be hacked What do you mean? XSS? SQL injection? What are you afraid would get hacked? > use cloud edge worker So you let a 3rd party private company interfere in serving your website? Of course we rely on third parties for some things, but that's a pretty dramatic course of action to let one of those edit your webpages on the fly.
Perhaps hacked isn’t the right way to describe it. The issue is that if you setup a re-build if your static site on receipt of a mention, that means anyone on the internet can rebuild your site whenever just by creating a mention. That has the potential to take your site down because for example you might run out of build monthly minutes. There are probably other ways such a setup could be used to cause issues.
> that's a pretty dramatic course of action to let one of those edit your webpages on the fly
The way I have been thinking of cloud edge workers is just another place you can run some compute when you get a request. I think I can see why you might be hesitant, so you might have a valid point, I haven’t spent a huge amount of time analysing the threat vectors that are inherent with edge workers.
In your opinion, why are edge workers more dangerous than the usual hosting provider that ‘interferes’ with the request by rendering and returning the page?
Earlier quoted context omitted.
I guess you're right for now. What would you think of an onboarding experience like at https://demo.mro.name/shaarligo/o/p/ac2gthz
It's probably as simple as it gets given the set of constraints (I assume) you've set on yourself. To open it up to a wider audience you'd either have to have write some sort of provisioning tool (possibly a local app) or lean on someone else's (Linode marketplace, etc). DNS shouldn't be overlooked either as something troublesome for users.
Hm. I consider that crucial for a user's control (agency) over it's digital property. To not depend on my tool for the existencial moments of creation and deletion of what is in between populated by my (other) tool.
This is cool! I'll be looking into adding webmentions to Kalaksi.com my rss-based social network. It makes perfect sense and is very much aligned with the "open web" I'm trying to help survive.
Kalaksi is really cool, too bad it didn't catch up! I applaud your goal to make the open web thrive by using RSS. I see that you're even incorporating RSS-bridge, that's very cool ! Since you want to use the open web standards, you probably have heard of the indieweb movement. They have been working in this field, have standardized a bunch of protocols, among which webmention is only one (see https://indieweb.org/gra…