rglullis

We tried at communick.news a while ago, it didn't work so well. Perhaps the situation has improved, so it's worth to take a look.

For instance you can't fetch Mastodon posts from Lemmy.

Having a standard URL scheme would precisely help us develop ActivityPub clients and get rid of application-specific servers.

I still don't understand why you'd prefer to stick with a community on LW when there is a whole instance at https://nba.space/ waiting for more participation.

https://lemmy.dbzer0.com/modlog?page=1&actionType=ModBanFromCommunity&userId=7652836

For the same reason that they have a website: to control their media presence and their means of content distribution.

if merging in the creative bits from each were merged into the more popular ones more often.

Yeah, the pity is that most of the times this simply doesn't happen, and everyone wants to reinvent their own special flavor of wheel.

You are right. I am still looking at anything related to the Fediverse as work and not as a hobby, and I shouldn't be expecting other people to share the exact same vision and ambitions.

I kinda want to write my own client

Fair enough, every developer goes through that.

At the same time... If this is your primary motivation I would feel like there is no point in you asking for "feedback" because you are essentially looking for validation.

I don't mean to pick on you, I just wish we collectively learned to stop this. So much effort is wasted by individuals who want to prove something to themselves and want to go out on their own, it feels like FOSS alternatives would be 20 years in the future if put worked together on 2-3 alternatives instead of 20-30 disparate projects.

If you are okay with reconsidering your position... go to Voyager's discussion pages on GitHub, there a few issues I opened there and would like to tackle:

• make it offline-first (probably using something RxJS to store and sync application data and state through different apps)
• add support to browse subreddits (won't require the API, and to ease the issue of network effects)
• make it less dependent on the Lemmy API and substitute for straight ActivityPub whenever possible
• use content-addressable storage for media (IPFS likely, but maybe also webtorrent)

If any of these things interest you, I'd love to have a longer chat and see if we can work together.

Why not take an existing client like Voyager, and add the features that you are missing?

This is exactly what I am doing for "easier onboarding". I am working on a fork of Voyager, learning my way through React Native and ionic, and adding support for Fediverser to it.

Imagine if OSes in the 90s crashed as rarely as desktop OSes today. Imagine if desktop OSes today crashed as rarely as mobile OSes today. Imagine if mobile OSes crashed rarely enough that the average consumer never experienced it. Wouldn’t that be a better state of things overall?

Depends. What is the cost to get there? Will that sacrifice openness? Will that sacrifice portability? Will that require ossified structures that will make development of new applications more difficult?

Look, the article is talking from the perspective of someone who is developing web apps in Ruby. Performance is not a huge concern. Processes being crash-proof are not a concern. You know what is the concern? To be able to validate ideas and have something that bring customers willing to pay real money to solve their real problems.

For his scenario, forcing to define everything up front is a hindrance, not a benefit. And having GP screaming at it like this for having this opinion is beyond ridiculous.

I don't really want to be talking past each other. The point I am refuting is that even if type-safety can help reduce the amount of bugs shipped, this is not the only metric that matters to measure the value of the software being developed.

bugs are really annoying

And being late or never delivering out of fear of shipping buggy code is even worse.

Some years ago, I worked on a crypto project that was financed via an ICO. This meant that whatever money the company was going to get was already in their hands, and their only job was to make sure they could prove they've done a best effort to deliver what was promised to investors.

Because of these incentives, the engineers were more concerned about covering their asses regarding bugs than to actually get the software out in the hands of users. The implementation was in python, and to the team it was easier to justify spending time on getting 100% mypy coverage than to get things in hands of users to see the value of what we promised to deliver.

In the end, by the time the team managed to deliver, the code was super well-tested, there were 0 mypy warnings and absolutely zero interest from other people in adopting our tool because other competitors have launched a whole year before them.