weex

I think most people understand that some things need to be secret aka private, like their passwords. I wonder if there are any old folktales about gossip in towns and villages that would be fun to rewrite for now. I named the open source community !magicstone based on one of those old stories and I think it helps get the idea across of building something great through community.

This project is a real MVP. Can't thank them enough.

NB: Lambert's proof is a metaproof composed of 14 other proofs, 5 of which no longer get security updates.

When I heard web3 on a podcast last week I actually hoped they were talking about the fedi. Nope, just same stuff plus AI. These labels just help some get funding and others to sell products.

It's similar to the supply chain issues. Centralization and concentration are good for efficiency but they can lead to very fragile systems. When those fragile and now big systems break, they make for high profile events that serve as a warning and counterforce to efficiency.

It doesn't matter if you shave 0.1% off your bandwidth costs if you lose 5% of your customers every year due to outages.

So I think it will work itself out as long as people cancel and look for alternatives these things when they're not getting a good experience. Normalizing consumer rights is the best way to help this and plenty of other issues.

Just found https://github.com/inventaire/inventaire which is about lending physical items and seems to be implementing ActivityPub.

Hey viktorstrate, My current operating principle is that a community is foundational to the success of a software project. Building community is therefore the first thing to focus on when starting something like this. To that end, I'm looking in your post for points around which a community could rally.

1/Easy-to use-is good, yes but it's kind of a given for all software. Some prioritize more than others but nobody wants their stuff to be hard to use.

2/Organize, share discussions are similarly common however an event focus is more unique. Mobilizon is working on this as well but I haven't seen that yet as a strong core problem around which the rest can be built. I think it's better added as a feature or plugin to an existing and strong software project.

3/Lists exist in Mastodon but not nested lists. I suppose once you have more than a handful of lists, you'll want more structure and so I think that might be a good feature, but again better added to Mastodon or a fork than something to build from scratch.

In terms of greenfield projects, I would think a TikTok-clone would be interesting. That's heavily dependent on a mobile app with strong camera, creative and video editing editing features but it would be nice to have somewhere in the fediverse to point that fastest growing segment of social.

Getting back to community, how do you feel about the strength of the photoview community and how do you think you might improve on what was done there in this new effort?

I feel like I'm seeing that effect here? I never noticed that lemmy broke out downvotes but here we are.

In regards to algorithms, I always assumed there was no budget to do the extra processing and that's probably true for the massive machine learning R&D projects that the likes of Twitter can fund, but if people really want open source algorithmic feeds then I'm sure they can be done under some computational cost.

I created Ecko, a fork of Mastodon, for the purpose of testing more adventurous ideas like this so created an issue based on this. Will be interesting to see if any code appears :)

This is the first I've heard of an alternate feed algorithm and it would be interesting to test. Has one been implemented anywhere yet?

My understanding is that code was limited to anti-spam. There's going to be some level of trust involved with using a centralized service so I don't see that it's such a huge issue, even as someone who prefers to use decentralized and FLOSS for as much as possible.