11–20 of 101 posts
I see we still haven't learned to put a summary of what your product is/does near the start of any big announcement.
Appears to be a fediverse social network like Mastodon, there's a demo on their homepage: https://bonfirenetworks.org/
- The homepage has a bunch of "Bonfire is...", but they don't tell me much about how Bonfire achieves any of those goals like to be a "commons".
- There's a codebase and documentation, but it comes in six different "flavours", although I can only really differentiate between two.
- Most of the FAQs just say "wip".
- It proudly states that there are no ads, no tracking, etc, but doesn't tell me what there are no ads on, or what isn't tracking me.
- It proudly states that it's federated, but as far as what it federates with, that's "wip".
I'm all for more federation, more data control, and experiments in social networking, but I'm a technical user and I have no idea what this is or does. It feels like in service of wanting to be as abstract and flexible, it maybe just doesn't solve any actual concrete problems.
If it's a toolkit with which to build social networks, that's great, but much of the documentation suggests that it's also a network itself, suggesting perhaps limited use as a toolkit. If it supports ActivityPub or AtProto, it really needs to come out and say that up front. "Bonfire is a framework for building custom AtProto based social networking applications" would be a great summary, or "Bonfire is a Mastodon alternative exploring the frontier of ActivityPub federated applications" would be great too.
there is a fine balance between new features and performance (e.g. android/ios apis, .net apis in unity game engine etc.) but I think there's a consensus around certain software not keeping its responsiveness acceleration on par with hardware capability acceleration, some of it driven by ideas like "everyone phone now has 8gb of ram, c'mon", but most of it by profit incentives on the other side, e.g. cloud providers.…
In my opinion, it’s good to make these mistakes earlier rather than later on. You got the scars early enough to think there must be a better way, as opposed to starting with the “old school way” and then thinking that AWS/GCP would make it easier.
it definitely helps to have scars, though. just pray something/someone takes you out of the pain soon enough (it took me ~4y to finally realize there has to be a better way at least for small/medium projects)
> Profit over people: at what cost? Profit hasn't been the goal of Silicon Valley for a very long time. Revenue and growth have been the goals, and chasing those two has been much more damaging than chasing profits.
> Profit over people: at what cost? Profit hasn't been the goal of Silicon Valley for a very long time. Revenue and growth have been the goals, and chasing those two has been much more damaging than chasing profits.
Aren't they chasing those to ultimately generate profits?
To the point that Uber said they may never generate profit in their IPO filing
Slightly unrelated maybe, but I'm really hoping that the https://once.com model would take off. That would be the change I would want to see in the software world. It's more simpler to understand than governance, public interest, etc. Just pay once and own the software. I really don't think software is that deep or has many philosophical implications.
I think before we talk about being only paid once for software (which isn't a finished product like a brick anyway) we need to figure that out.