Hedja

It feels like this is already a work in progress using Beaker Browser and Dat.

- Beaker lets you browse entire websites (dat archives) and fork them.

- It lets you create and serve your own sites directly from the browser and seed it from a server (like a torrent).

- It lets other sites create templated sites under your name for user generated content.

- Visitors by default temporarily seed your website which may reduce single point of failures, hug of deaths and costs.

With this peer-to-peer torrent-like approach, the web can become distributed again and feel more like a "web". There's still a lot of work left and maybe Beaker itself isn't the best implementation for this idea, but it's a good start.

https://beakerbrowser.com/

https://datproject.org/

Always publish on your own platform then syndicate it across all the relevant social media providers to get exposure.

It's a huge pain, especially now that most platforms are closed and don't provide automation (APIs, RSS), but it's really the most flexible solution.

It also makes syndicating to new providers a lot less painful since you'll have some standard raw form (e.g. Markdown) which you can create a manual or automated pipeline for.

Considering Liberapay is using Mastodon, I expected them to already know what they're getting themselves into. Especially with Medium's thickening walls.

If the goal of this project is related to simplicity, the README makes it look like anything but that.

I've also written a blog post about some of the reasoning and thoughts behind it here: https://jahed.io/2018/01/29/introducing-night-patrol/

Understanding where to put a bunch of class names is a lot easier than understanding CSS. Bootstrap isn't really about working around CSS, often it's about avoiding it. CSS Grids will likely just make Bootstrap easier to use, maintain and extend.

I personally stopped using Bootstrap years ago when I gained a good understanding of CSS. The most common features that Bootstrap provides (components and layouts) are not hard to implement yourself. And you'll avoid littering your markup with brittle combinations of class names and nested <div>s.

You can do this with CSS Modules using BEM Classnames and a function to generate BEM classnames given a Component Name and State/Props.

The function can then pick the generated classes out of the CSS Module's JSON import. If the classname doesn't exist, it can warn to the console.

It's farely straight forward in React. You just need to make sure you always use the function to provide values to the className prop instead of manual strings.

Strange they've updated the main docs to 5.x yet their master branch is still on 4.x without a 5.x release.

https://github.com/FortAwesome/Font-Awesome

We use "Name & Name <team@company.com>" during pairs/mobs so we don't worry about who gets the credit and waste time rotating authors. It doesn't look great on GitHub but we usually use an IDE to go through commit history anyway.

It doesn't work great for our open source projects though where visibility on GitHub tends to be more important.

RSS/Atom is still used by most syndications. The average user may be unaware of its existence but that same audience is similarly unaware of most technologies that drive the web.

Other than the death of Google Reader, there hasn't been much of a change.

The only alternative to RSS right now (afaik) seems to be bespoke APIs and <meta> which is a pain for publishers to maintain and for software to syndicate.

Zelda Wiki is hosted on Gamepedia. It's like Wikia but specifically for Video Games and less obstrusive.

Just thought I'd share my experience with this, since I had a similar problem.

Spinners make it look like the app is taking ages to load data, even if it's not. If you delay showing the spinner until around a second of loading, it makes things feel a lot faster.

The user doesn't need to always know when the app is loading data until there's a significant pause and they need to know stuff is happening.

I'm building a game wiki/guide platform right now[1]. The idea mainly came from just wanting to re-create a game's interface on the web[2] and it gradually grew to a game guide and now a multi-game guide platform. I tried to learn new tech on the way to keep myself interested. The large parts being LeafletJS/PixiJS, moving onto React, then Firebase, and so on.

A lot of my web project ideas are related to the video game community because I often use and contribute to them and constantly find certain things lacking (wikis, forums, list trackers, news). So this project has nicely grew into something that I can both learn from and enjoy building for the long term. Of course there are the tedious parts (like upgrades and maintenance) but they're overcome gradually; it is just a side project right now.

[1] https://frontiernav.jahed.io/

[2] https://frontiernav.jahed.io/explore/game0/visualisations/ma...

I wouldn't say it's bad. It's confusing at first, like most interfaces with a ton of controls, but you gradually get used to it and know where things are.

The bad thing about the UI at the moment for me is the lack of HiDPI support (as far as I can tell). And back when I was using OSX, the interface seemed a bit janky since it used XQuartz and it generally wasn't very native both in terms of UI rendering and its default keyboard shortcuts.

You can disable issue trackers and PRs and let them know in the README.

Exactly the reason why I decided not to pay for Firebase and instead went with gradually rolling my own solutions.

Their Realtime Database is extremely convenient and pretty useful for web apps, but there's no way to limit the connections and track bandwidth usage in real time. It's basically an open door for anyone with only your Security Rules to block data access. There's no logs to even see if your rules are working as expected, nor where your connections are coming from. They didn't even have that simple blue line showing basic usage in OP's post until recently. The profiling tool mentioned in the OP is also recent and doesn't give a proper picture.

It's just really pathetic. They sell themselves as a service company for startups, but one of the biggest things startups need to do is manage their costs, which Firebase doesn't provide in any form. And now since Google bought them, their support will be near non-existent as with all Google products.

Having said all that, their Free tier is great for live prototypes and doesn't require adding payment information. Just make sure you're not tying yourself in if you want to progress. Make thin wrappers around their libraries and export your data regularly if it's not throwaway.

Probably because it doesn't feed into the narrative he's trying to make.

Nintendo have been pretty much been releasing highly memorable and praised games year-on-year. Most of which have a big designer behind it or at least providing advice, whether it's Miyamoto, Sakurai, Aonuma or whoever.

But of course, times are changing. These people have been in the industry for decades. A new generation will need to take its place so they'll gradually move into coaching roles to pass on their knowledge and experiences.

Also, most games developed by large companies are hardly ever attributed to a single person. It's a lot more collaborative now as studios get bigger and more people are involved compared to back then (where most well-known designers got their popularity from) when it was couple of developers writing assembly.