@fleeky @cmdrmoto @atax1a Yeah, I still love SSB. The approach to social graphs and moderation is still my fave of any social networks I've used. Also of course love the community and the pals I made there.
One thing I don't like is the data model. Needing to fully replicate logs and build up local indexes is bad UX and I think sparse pre-indexed sparsely replicated datasets would improve things massively. (also the use of json and weird node dependency management was pretty rough).
@em @forestjohnson Yeah webtransport is defs going to make it easier for browsers to connect to dhts and "native" networks. I worry that it still doesn't give us enough however.
It doesn't (yet?) give a way to host servers listening on incoming connections. It can't do UPNP and other negotiations with the router, and it can't do multicast UDP for local peer discovery.
Still a good step though!
@forestjohnson I've been making p2p apps for years and have done consulting for companies that made their own. :)
P2P in web browsers is defs a nono since the browsers security model and browser vendors won't allow it any time soon.
I defs don't mean to say that people shouldn't self host, it's just that that's not where we should stop.
More unmodified browsers these days are getting support for loading sites from IPFS for example.
For NAT stuff holepunch.to and socketsupply.co are good.
@yassernasc@mastodon.social Yeah there's stuff other than Beaker out there these days. Especially with the #IPFS ecosystem. There's IPFS support in Brave Browser and some flavor of Opera, and there's progress in making it available in chromium based browsers like Edge.
There's also my browser @agregore :P
@yassernasc@mastodon.social Yeah! That's pretty much where I'm planning to go this year. We've got ActivityPub integrated with p2p published static sites. Next we'll be making an AP client that integrates with the social inbox and make specs for identifying AP actors as being p2p-enabled so their stuff can be loaded directly.
@bx Yeah you can set up down left right to different keys. Also analog sticks give you 8 or more directions. Steam's UI for key bindings is really powerful too, you can have key combos and different effects for long presses and double presses and stuff.
Interesting idea for GBA. I've actually been cobsidering ditching my keyboard for a mini bluetooth cobtroller that would fit in ny hand. I currenrly just use it for tiktok scrolling but this 8vim thing might be usful for typing in general
@skryking Yeah big mood. At least these fays relay discovery is automatic and nodes automatically advertise as relays if they have a stable IP so it's a bit less centralized. IPv6 would be v convenient but it's still unavailable to so many regions 💀
@skryking Yeah NAT can be a pain. Have you been keeping up with some of the latest p2p networking stacka that are tackling it? Hyperswarm for example has great hole punching capabilities using DHT peers and IIRC they have a built in relaying thing for peers that can't ve hole punched. Works oretty quickly and reliably too. Only dowbside is it has a strong dependency on node.js so it's hard to embed in non-js apps.
I surprised someone again yesterday by saying that I legitimately don’t think technical issues are the hard part of shipping projects.
I find the constraints are almost always about how to navigate conflicting points of view, deadlines, organization, planning, and budgets. People, planning, and money are the hardest topics. The technical parts seem far less difficult -sometimes even trivial- in comparison.
@atax1a Yeah for sure, even just needing an always online http server in there is too much. Self hosting is a reaction to central hosting but we need to rearchitect stuff from the ground up to really be free. Gatways and bridges to http based fedi is a path to connect to existinf folks which is what I'm focusing on with the strategy in #DistributedPress
Instead of #selfhosted servers it'd be nice if software was #CloudFree and #P2P
Not only should we not ve reliant kn centralized corporate hosting, we should be able to just use whatever devices we have on hand without extra server maintenance.
@atax1a Honestly I hope we can get to a point where you don't need to think as much about infra to self host. Kinda the reason I've been looking at using #p2p publishing where you wouldn't need to set up dns or mess with ip addresses and be able to run everything you need right from the devices you use.
@fyrfli Ooo, a digital ocean one click deploy might be handy. I know it's still a bit "technical" but offloading the details of provisioning dns and managing a droplet to DO might make it easier to get *something* people can use and the lower power droplets are pretty cheap.
@fyrfli Interesting. I think I've seen some services for spinning up mastodon and pixelfed instances with fair fees. I forget the names though.
Is there something specific about gotosocial that you prefer?
I've been working on it from a different side with statically published blogs being available on the fedi via @sutty and distributed.press.
We still need an "app" for folks to easily load followed AP data into their device instead of large instance databases.
@ben What are y'all using for your backend? You might be into reusing some of the learnings and tools we've made in distributed.press: https://blog.mauve.moe/posts/distributed-press-social-inbox
@fyrfli If you don't mind me asking, how do you feel about there being more single user instances that sidestep the "need a techy admin to manage everyone" issue? My gut feeling is it could lead to more community blocklists and personal curation and skip needing to find "safe" instances, but I might be overly optimistic about it. I think it'd be neat if community was who you associated with rather than who owned your instance.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.