im moving the cutoff as i age and im not going to stop :p
"Can someone try and poke holes in this idea?"
you are still proposing a federate ad network. payments are left to crypto (not fedi), credit cards (not fedi) or paypal (not fedi). the shipping is done by shops themselves (not fedi) (also amazon handles ~80% of their deliveries, check in this thread for sources). What's a "main shop"? doesn't sound very decentralized. you suggest leaving contestation again to the shops to handle (not fedi).
what exactly are you fediversing here? the proposition to users would basically be a single view with all shops, but then just delegating to them? there can be value in this, i see it mostly as an ad network leveraging AP and I'm really not a fan. it isn't really amazon
being angered by being shown issues in your idea doesn't help your idea. go visit your local hackerspace and start building if you think we're just naysayers
not really, for daily commutes any piece of junk that brakes and rolls will do. rode only ~50 bucks bikes for the last five-ish years, old city bikes are indestructible
you are not proposing a federated amazon, this is just federated ads and/or reviews.
how to process payments? how to ship goods? how to handle refunds? how to handle contestations?
please you can't just make anything federated. this protocol is built for social media and struggles to take over that sphere, we should focus on one thing rather than throwing random stuff at the wall hoping it sticks (cough federated tik tok cough)
this is an icky issue because lemmy sends votes with empty addressing, so remote instances should count them but not show them to anyone. however mastodon (and *key) sends likes with empty addressing too, but considers them public. lemmy is (surprisingly) right here and should request that the rest of fedi respects the protocol and hides stuff based on its addressing. maybe open issues on mastodon and friendica
also this issue probably exists when seeing lemmy posts on any microblogging instance
please have some introspection: you're being offended over some internet argument and complaining about a whole community. is your respect conditional on never wronging you?
your statement is so extreme it gets nonsensical too.
compilers will usually produce higher optimized asm than writing it yourself, but there is room to improve usually. it's not impossible that deepseek team obtained some performance gains hand-writing some hot sections directly in assembly. llvm must "play it safe" because doesn't know your use case, you do and can avoid all safety checks (stack canaries, overflow checks) or cleanups (eg, make memory arenas rather than realloc). you can tell LLVM to not do those, but it may happen in the whole binary and not be desirable
claiming c# gets faster than C because of jit is just ridicolous: you need yo compile just in time! the runtime cost of jitting + the resulting code would be faster than something plainly compiled? even if c# could obtain same optimization levels (and it can't: oop and .net runtime) you still pay the jit cost, which plainly compiled code doesn't pay. also what are you on with PGO, as if this buzzword suddenly makes everything as fast as C?? the example they give is "devirtualization" of interfaces. seems like C just doesn't have interfaces and can just do direct calls? how would optimizing up to C level make it faster than C?
you just come off as a bit entitled and captured in MS bullshit claims
I would be SoL if I didn't have one of my original sessions upon making the account years ago still
key backups are a thing: element tries to make you save the recovery phrase. if you lost your recovery phrase and all sessions, you can still rotate keys and recover the account, just no encrypted history. it seems you're not familiar with matrix, not that the system is flawed
99% of rooms aren't encrypted so are completely and totally insecure anyway
if this is true, you wouldn't even be SoL if you lost your session: just rotate keys. very big rooms are unencrypted: what value does e2ee provide when the other end is 10k+ people? any of these may ne untrustworthy, you're just paying extra infra cost. also, if 99% of your rooms are unencrypted, how do you keep seeing encryption issues?
these statements seem excessively dramatic and in opposition with each other
you mention neochat and fluffychat. i explicitly said element, and element x on mobile
im rather upset at the fact that we have basically no choice: dendrite is getting left behind, construct is abandoned, conduit is weird and conduwuit is not super reassuring. on the clientside, fluffy mostly works but uses old crypto, cinny is slow and lacks a ton of stuff, nheko is a mess, fractal is really underfeatured and i don't even know what neochat is. using matrix basically boils down to "synapse+element(x)" or "lmao have fun fixing stuff"
it seems from your replies you lack understanding of how things work and are nonetheless choosing community clients rather than the stuff element does. super valid, i encourage you to do so, just maybe cast your judgment on the actual stuff you're using and not the whole project itself
i'd like to close saying that your anectodal experience is not of much value here: you are having issues? i'm not, and neither is all those i'm communicating with. what gives? it's instead observable that newer developments address the issues you're mentioning: transparent encryption and simplified sliding sync
element is entitled, ignoring feedback and constantly playing the victim. its practices with the protocol are despicable.
the protocol, however, works
while "Could not decrypt message" is the n1 meme for matrix, i haven't seen it happen in a long while, maybe a year. synapse and element x are quite good at this point, you should try matrix again
im not an element fan, company is a bit spoiled and sassy, but they stopped adding features and went all in on polishing recently. fair, as they're trying to sell themselves for national deploys
honestly hashtags is 100% lemmy's fault: groups/communities are "audience" AP field, lemmy some time ago aiming to be "more compatible with mastodon" made it so that posts in communities get automatically added an hashtag, and hashtags get sent into communities. this is honestly stupid and should be undone, you'd better aim your anger at lemmy devs.
regarding mentions, Twitter-like software needs them for addressing: lemmy implies that replies are addressed to replied-to user, other software doesn't (you may want to contribute to a conversation without mentioning user directly above). if they don't mention, you don't see it, you'll have to just deal with this. you could cook yourself a client that finds mentions in object "tag" and removes them from the body itself if you care this much
you're right, my initial reply was harsh, i wish i had waited a bit longer before replying. i hope my points won't get lost in the rant because i stand by them. i really wish this enthusiasm was spent on other hurdles rather than chasing big monoliths. i don't want to curb enthusiasm, just move it elsewhere
So let me get this straight. Are you really saying "we the developers are going to build this however we see fit, and you the user can go fuck yourself, or else learn how to code and build it yourself"?
you're putting it in rather extreme terms, but yes. even if you were completely right in your opinions, the person investing their free time to do work and sharing freely the result is entitled to work as greatly or badly as they like
Don't like the feedback? Great, feel free to ignore it, or tell me why I'm wrong
honestly yes I'm doing exactly this: I'm ignoring your suggestion and telling you why i think you're wrong. i also shared some of my reasoning behind which i think is still valid, and i will reiterate it
This alternative has existed for a long time, but still has a fraction of the users as other alternatives out there. Aren't you at least curious as to why that is?
not at all because i know a good reason for it: fediverse doesn't scale well if expected to replicate fully and be a "central plaza". every server owning every post from billions of users is a very prohibitive design, especially if you expect self-hosters funded by their wallet or donations
i really think we should try to change how we do social media, not make the same thing again. if you just want that, atproto is likely more fitting, AP is decentralized, not distributed! things like nomadic identity would make the "server issue" obsolete. replies collections permit on-demand fetching of replies. activity signing and forwarding could provide real network-wide broadcasts
if we're cooking ramen, we appreciate knowing if it's too salty or bland. coming to complain about ramen not tasting like burgers, and proposing to add some ketchup, is useless at best, a bit disrespectful at worst
this feels useless at best and entitled at most: if you want these, get working. this is not reddit or Facebook: there is no profit or product, nobody is making money and no money is being spent on development or making sure your requests are met. all the time you spent writing this or replying could have been spent actually researching the app. not a dev? not entitled to complain
simplify user sign ups
you're basically proposing a centralized service over a decentralized network. who runs that service? how is it guaranteed fair? which servers should be in the pool? what if a server is worse than another spec-wise? what if the assigned server shuts down? the solution to the server issue is you picking a server for your non techie friends, not cooking more centralized complexity on top.
polish/add functionalities
if you really want features developed, make a bounty! pay developers! expecting others to work for your appeasement for free is distastefully entitled. or do it yourself. as you can probably assess, expertise and free time don't grow on trees.
how to attract more users
i think most of this disconnect stems from you wanting this to be just like big centralized services. it's honestly delusional. in another reply you state that "lemmy.world couldn't handle 10M users". maybe, but decentralization is only going to make it worse. every lemmy server needs to broadcast every action to every other server which has users in that community. every post and like needs to be stored in all relevant instance dbs. this generates an insane amount of traffic and data. if the lemmy network suddenly gained 1000 servers, each with 10k users, the new replication traffic may stomp smaller instances to the ground.
the idea of a "global square" is naive and we should move over. it just limits us all because a platform which caters to everyone must be built around the common ground, and the common ground for everyone isn't that much ground. a platform that caters to everyone caters to no-one: see mainstream social media and how it's going. fedi is great because it's a whole different model: small islands which can interconnect. this is why picking a server is so important and you should not hide it from the user: you're not signing up to mastodon, you're signing up to furry.engineer or fosstodon! you can interact with the other instance just fine, but it matters where you register!
this is the core of the disconnect: we should not bend the fediverse to what mainstream social media is, we should either teach others about this or be fine living as a niche. auto enshittifying ourselves hoping to be another facebook or another reddit feels really silly to me
there are plenty of articles about regrets and resources about detransition, those who get shouted down usually try to use ridiculously low regret rates as reasoning to limit access to healthcare. marriage has a 43% regret rate, why isn't your energy spent there instead?
then use "they", do you speak exclusively with yourself? your linguistic choices affect others, just like others' linguistic choices affect you (as you were noticing and complaining about)
you don't understand the language and thus everyone should comply with you? i'd rather read correct english than what you find more understandable
nice whataboutism, "they should do this instead". oh they do, but you don't care when they do.
the delivery didn't deface anything, if you want to focus on the delivery and once again ignore the message at least be honest. willing or not, messages like this do BP bidding
comparing with mullvad is ridiculous and just shows how much you drank the apple juice without questioning
- mullvad doesn't hold your contact info, like apple right?
- mullvad is open source so you can independently verified which data is being sent, just like apple right?
- mullvad claims to not log anything, like apple and their csam thing on icloud right?
"leave alone the multi billion dollar corporation" energy
if you're trying to build a chatroom then any chat software goes but if you're trying to build a community you should probably use something searchable and indexed, like real community software
also i find it laughable that users must already be on such platform, by your logic all communities should be mailing lists
i really disagree with most of your points. a "server" is some machine working for the client. your proposal isn't getting rid of servers, you're just making every user responsible to be their own server.
this mostly feels like "im annoyed my instance is filtering content and lacks replies". have you tried fedilab? it allows fetching directly from source, bypassing your instance and fetching all replies. i think thats kind of anti-privacy but you may like it
if you're interested here's a wall of text with more argumentations on my points (sorry wanted to be concise but really failed, i may make this into a reply blog post soon:tm:)
Federation is not the natural unit of social organization
you argue that onboarding is hard, as if picking a server is signing a contract. new users can go to mastosoc and then migrate from there. AP has a great migration system. also federation is somewhat the natural unit: you will never speak to all 8B people, but you will discuss with your local peers and your ideas may get diffused. somewhat fair points, but kind of overblown
Servers are expensive to operate
you really can't get around this, even if you make every user handle their own stuff, every user will have their database and message queue. every user will receive such post in their message queue, process it and cache in their db. that's such a wasteful design: you're replicating once for every member of the network
We should not need to emulate the fragmentation of closed social networks
absolutely true! this should get handled by software implementers, AP already allows intercompatibility, we don't need a different system, just better fedi software
The server is the wrong place for application logic
this is really wrong imo, and the crux of my critic. most of your complaints boil down to caching: you only see posts cached on a profile and in a conversation. this can't be different, how could we solve it?
- you mention a global search: how do we do that? a central silo which holds all posts ever made, indexed to search? who would run such a monster, and if it existed, why wouldn't everyone just connect there to have the best experience? that's centralization
- again global search: should all servers ask all other servers? who keeps a list of all servers? again centralized, and also such a waste of resources: every query you're invoking all fedi servers to answer?
- even worse you mention keeping everything on the client, but how do you do that? my fedi instance db is around 30G, and im a single user instance which only sees posts from my follows, definitely not a global db. is every user supposed to store hundreds of GBs to have their "local global db" to search on? why not keep our "local global dbs" shared in one location so that we deduplicate posts and can contribute to archiving? something like a common server for me and my friends?
also if the client is responsible of keeping all its data, how do you sync across devices? in some other reply you mention couchdb and pouchdb, but that sounds silly for fedi: if we are 10 users should we all host our pouchdb on a server, each with the same 10 posts? wouldn't it be better keeping the posts once and serving them on demand? you save storage on both the server and all clients and get the exact same result
having local dbs for each client also wouldn't solve broken threads or profiles: each client still needs to see each reply or old post. imagine if every fedi user fetched every old post every time they follow someone, that would be a constant DOS. by having one big server shared across multiple people you're increasing your chance of finding replies already cached, rather than having to go fetch them
last security: you are assuming a well intentioned fedi but there are bad actors. i don't want my end device to connect to every instance under the sun. i made a server, which only holds fedi stuff, which at worst will crash or leak private posts. my phone/pc holds my mails and payment methods, am i supposed to just go fetching far and wide from my personal device as soon as someone delivers me an activity? no fucking way! the server is a layer of defense
networks are smarter at the edges
the C2S AP api is really just a way to post, not much different than using madtodon api. as said before content discovery on every client is madness, but timeline/filter managenent is absolutely possible. is it really desirable? megalodon app allows to manage local filters for your timeline, but that's kind of annoying because you end up with out of sync filters between multiple devices. same for timelines: i like my lists synched honestly, but to each their own, filters/timelines on the client should already be possible.
you mention cheaper servers but only because you're delegating costs to each client, and the "no storage" idea is in conflict with the couchdb thing you mentioned somewhere else. servers should cache, caching is more efficient on a server than on every client.
a social web browser, built into the browser
im not sure what you're pitching here. how are AP documents served to other instances from your browser? does your browser need to deliver activities to other instances? is your whole post history just stored in localstorage, deleted if you clear site data? are you supposed to still buy a domain (AP wants domains as identities) and where are you going to point it?