Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I joined the IndieWeb, here's what I learned

en.andros.dev

Post reply on HN
Print view View original

111–120 of 167 posts

Re: I joined the IndieWeb, here's what I learned

#111

Post by yoz-y »

5701652400 wrote: post #59
TheOtherHobbes wrote: post #26

If IndieWeb wants content, burying it under a ton of tech soup is the exact opposite of what they claim they want. How do the developers not realise that this set of protocols is completely unworkable for 90% of users? Please stop developing systems where the engineering is front and centre. If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running inst…

+1. unless I see IndieWeb in AppStore and real volume of real people use it, it is all tech people toy hobbies (which seems diametrically opposite of IndieWeb: no HTML - iOS/Android is the king, no browsers, no desktop, no terminal, no GitHub, gated App Stores, rich media, videos is the king)

IndieWeb is pretty large. And by its own design the majority of users (lurkers) is hidden behind a page views metric that most people don’t even look at.

Re: I joined the IndieWeb, here's what I learned

#112

Post by arccy »

fragmede wrote: post #43
inigyou wrote: post #20

Earlier quoted context omitted.

It's not possible. But there are more and less neutral ones.

It's possible, if you have $600,000 to purchase one.

depending on the org, maybe closer to $100,000 https://www.dotfurry.org/#why-furry

Re: I joined the IndieWeb, here's what I learned

#113

Post by klez »

5701652400 wrote: post #102
andros wrote: post #73

Earlier quoted context omitted.

GitHub Pages is free for public repos, which makes perfect sense for a public blog. IndieWeb content is public by design.

you guys keep shifting goal posts is nuts. whatever critisism is just "IndieWeb decides not to do so". not admiting own mistakes also goes hand-in-hand with it. overall, recipe for disaster.

We're talking about public websites. Nobody moved the goalpost. It's always been about online presence, hence public websites.

Re: I joined the IndieWeb, here's what I learned

#114

Post by jpfromlondon »

TheOtherHobbes wrote: post #26

If IndieWeb wants content, burying it under a ton of tech soup is the exact opposite of what they claim they want. How do the developers not realise that this set of protocols is completely unworkable for 90% of users? Please stop developing systems where the engineering is front and centre. If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running inst…

that it was so perversely gatekept is what made the early internet so enjoyable though.

I find it all the more appealing with that barrier to entry because I miss the internet that this community is nostalgically trying to replicate and reproduce.

Re: I joined the IndieWeb, here's what I learned

#115

Post by 5701652400 »

klez wrote: post #113
5701652400 wrote: post #102

Earlier quoted context omitted.

you guys keep shifting goal posts is nuts. whatever critisism is just "IndieWeb decides not to do so". not admiting own mistakes also goes hand-in-hand with it. overall, recipe for disaster.

We're talking about public websites. Nobody moved the goalpost. It's always been about online presence, hence public websites.

no. you do move goalpost. you talking about public webiste, and now you need to make public entire git for it.

do you see difference between history of edits and internal documentation about the public website and public website itself? or sources to build website vs website itself? it is nuts not to see distinction of that.

github repo != public webpage. this is nuts.

Re: I joined the IndieWeb, here's what I learned

#116

Post by ozim »

jcgl wrote: post #31
myzek wrote: post #27

Earlier quoted context omitted.

I'm pretty new to this so I can't speak for IndieWeb, but I wouldn't blame them. People who seek independence from the social silos are usually engineers or other web-aware people. It is only natural that they want to solve the problem with the knowledge they possess and tools they know - and I think it's fine. If you look back at how internet evolved, it was always like this - the geeks and nerds coming up with some…

First of all, techy nerdy people like things to be easy too. They're just somewhat more likely than other people (on average) to overcome not-easiness. Second of all, how long is IndieWeb supposed to cook for before it's supposed to be ready for a broader audience? This is no shade on the IW folks if they like what they're building. But if what they're building is supposed to catch on somewhat, what's the path suppos…

Exactly I have limited time in my life to tinker with stuff.

If something is important for me I can waste hours setting it up and running.

If it is something new to me, if it doesn’t work out of the box I most likely will just move on.

Re: I joined the IndieWeb, here's what I learned

#117

Post by abc123abc123 »

tracerbulletx wrote: post #75
TheOtherHobbes wrote: post #26

If IndieWeb wants content, burying it under a ton of tech soup is the exact opposite of what they claim they want. How do the developers not realise that this set of protocols is completely unworkable for 90% of users? Please stop developing systems where the engineering is front and centre. If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running inst…

No. Exact opposite. Opening it up to everyone is what kills everything good, the endless september of grocery store tabloid aisles and clickbait. Gatekeepers are good, restrictions on participation are good. The internet was better when it was a self selecting place for interesting interested people and not the global walmart.

This is the way! There _has_ to be friction when getting access or the uneducated hordes of the internet will spoil it. I only use mailinglists and fediblocked instances for "social" media. Mainstream mastodon is useless and just a bad parody of x or fb.

Mailinglists are great, because more and more people do no longer know how to use email or follow the instructions to sign up for a mailinglist, so many interesting people tend to gather around the lists.

Re: I joined the IndieWeb, here's what I learned

#118

Post by account42 »

> microformats2 solves one problem: making your content machine-readable without publishing parallel files or building an API.

Which isn't generally a problem that ever needed solving. Just like the previous onthologies, all this does is feed your adversaries while being useless to your human visitors.

Re: I joined the IndieWeb, here's what I learned

#119

Post by xtiansimon »

andros wrote: post #18
xtiansimon wrote: post #14

> “Use what you make: use what you build every day. ‘If you aren't depending on it, why should anybody else?’” Having difficulty imagining this constraint. For example, I use my iPhone’s Note app daily for personal notes. I don’t currently host a site, but if I did I might have content/write on no more than monthly cadence, or per-project. Does this rule suggest that I should ‘publish’ more (ie. elevate private note…

Today it's quite easy to keep your private notes on your infrastructure, manage them with your iPhone, and even store them in plain text: Joplin, Syncthing, WebDAV ( https://en.andros.dev/blog/9abcdcfe/your-denote-notes-on-the... )...

> “Today it's quite easy…”

Not sure if you’re responding to my confusion (“Having difficulty imagining this constraint”).

I’m not asking about implementation of a solution nor of capability, but how the maxim “use what you make” is envisaged by the authors as a mechanism of engagement, management and quality for the IndieWeb. Why is it a pilar?

Re: I joined the IndieWeb, here's what I learned

#120

Post by account42 »

andros wrote: post #7
superkuh wrote: post #6

Earlier quoted context omitted.

I don't know about you, but I don't know of any native (non website/javascript) software that supports h-feeds. IndiePass was only ever for smartphones and it's fully dead. h-feed is more of a html integrated mark-up for posts than any form of actual separate feed file. This is claimed to be a positive aspect of h-feeds, not being a separate file... but it really isn't. I keep track of all the other indieweb sites I…

Well, don't shoot the messenger. I'm just letting you know what they recommend :D By the way, andros.dev has an RSS feed.

> Well, don't shoot the messenger. I'm just letting you know what they recommend :D

The great thing about hosting your own website is that you can decide for yourself what "standards" and "recommendations" actually make sense for you.

> By the way, andros.dev has an RSS feed.

You should add links to the RSS/Atom feed. The way people (or at least I) discover RSS feeds is to paste the blog/article URL into my feed reader - if that can't find the feed then I more than likely just give up and move on. All I can find on your site is a button in the side bar that doesn't even work.

Post reply on HN