Create, enable and scale economic and digital exchange across and between diverse sectors.
Seems cryptocurrency related. Lot of marketing fluff.
Beckn Protocol is perhaps the least well-known project outside of tech circles, but is likely the most impactful of all work Nilekani has championed since Aadhaar
Who and what are those?
The github repo is slightly better, but not by much:
Beckn is an open protocol that allows local businesses across any industry to be discovered and engaged by any beckn-enabled application. Beckn protocol helps businesses co-create solutions for the masses seamlessly, by combining services of any form or provider.
Beckn protocol is a collection of open specifications consisting of protocol APIs, message formats, network design and reference architectures to allow any two entities to execute commercial transactions without being on the same platform.
This server-to-server communication protocol allows any consumer facing online platform to discover and transact with any business with minimal implementation overhead. The server-to-server nature of the protocol allows rich user experiences to be built by bundling services from multiple independent platforms.
Beckn protocol decouples the demand side digital infrastructure in the form of apps and other channels from the supply side service provisioning infrastructure. It does this by making integratedservices available not just on a single platform but potentially on any online consumer interface, (online maps, messaging, wallets, voice assistant apps and devices) that have mainstream adoption in a city.
Beckn is a protocol, not a platform. It adopts a decentralized architecture that obviates the need for creating a centralised platform in order to integrate services from multiple providers simultaneously ensuring privacy and security by design by enabling secure, encrypted iteractions.
The project could really use a "What problem is this trying to solve?" section. Is it aiming to replace something existing like HTTPS/Visa/etc?
Not really a question, but something to think about is being more strict about backwards compatibility so that people don't get burnt out on having stuff break. Coming from this post by the Tesseract dev, who did not like the breaking changes to the v3 API in 1.0: https://dubvee.org/post/2904152
To formulate that into an actual question, do you think the changes are still worth it and you'd make the same decision to break backwards compatibility?
I have multiple accounts, but only really for moderation purposes. Cross-instance moderation is semi-broken, so it's easier to do it that way. Other than that, having an alt is useful in case your main instance goes down.
I wouldn't generally worry about impersonation, if someone tries it you could contact the admin of that instance and they're generally pretty responsive.
Pixelfed/Mastodon/etc sort of work with Lemmy, in that they can see Lemmy posts. Lemmy can see posts from them if you tag them appropriately, which rarely happens. They only sort of federate properly. And yeah, Loops is like TikTok for the Fediverse.
I'm not saying PieFed is better than Lemmy, just saying that apart from Lemmy, your best option is probably PieFed atm.
I was using Loops pretty heavily for a while, but the most recent update made it not work right on my phone (and there's no web version), so maybe I'll try again when it's out of beta. It's also not truly federated atm, so only sort of counts.
I've tried out a bit of PieFed and it looks really nice. Probably the best Lemmy threadiverse alternative atm. The dev does some interesting experiments like Private Voting
Sorry, worded that somewhat confusingly. FairEmail and Thunderbird are both open source apps that I use as clients for my Fastmail account, which probably isn't open source (I haven't checked)
I use Fastmail with a custom domain for hosting, and FairEmail as my Android app and Thunderbird as my desktop client. Pretty happy with that setup, the apps don't do any data mining and are fully open source
The linked site has a bit more about it, but usually you see toggle switches like that with relatively "balanced" options. "On" / "Off" are about the same width when rendered as text. It's easy then to just make the switch big enough for the bigger option and everything's good. What happens if you have "On" and "Some really long text option that should probably be shorter"? The image shows what it looks like toggled to "On", and then goes over two solutions, neither of which are great options:
Use the smallest size and cut off the larger text. Not really a viable option
Use the longest size, but when the shorter option is toggled to, you're left with a bunch of blank space
Related, pagination can still get broken if you try hard enough. Some sites have pagination, but bump up the id of old posts every time there's a new post, so it's still useless because the links will change content
It's a little bit harder than you think, because people will definitely do things like this, and they have to account for that sort of behavior:
It is nice to see that they're working on it, where "they" means part of the W3C (so not just random nobodies):
The purpose of the Open UI, a W3C Community Group, is to allow web developers to style and extend built-in web UI components and controls, such as
<select>
dropdowns, checkboxes, radio buttons, and date/color pickers.
To do that, we’ll need to fully specify the component parts, states, and behaviors of the built-in controls, as well as necessary accessibility requirements, and provide test suites to ensure compatibility. We’ll also implement polyfills for our extensible web UI controls.
Today, component frameworks and design systems reinvent common web UI controls to give designers full control over their appearance and behavior. We hope to make it unnecessary to reinvent built-in UI controls, but for those who choose to do so, we expect that these design systems will benefit from Open UI’s specifications and test suites.
Long term, we hope that Open UI will establish a standard process for developing high-quality UI controls suitable for addition to the web platform.
It's federated, just not to the ActivityPub universe, right? People have been able to join rooms on discuss.online using their matrix.org accounts, which to me counts as federated.
Only one program can listen on a port at a given time usually. Something's listening on port 443 (the standard HTTPS port), and when nginx starts up it tries to listen on that port and can't. You can figure out what's already listening on that port with commands like lsof or netstat, see here for examples:
I don't know exactly what you're avoiding wireless for, but it has no ability to transmit, only receive FM if that matters. You could fairly easily disconnect/break the antenna and permanently disable even that.
The closest you're going to find is probably the SanDisk Sansa Clip+. It can receive FM, but IIRC no wireless other than that. I don't think it's made new any more but you should be able to find it for less than £100 online.
I don't think mutual aid can work well like that on the internet. Works great in person, works OK for GoFundMe-type stuff like "I had something happen to me that will take a lot of money to fix". Too easy to scam and grift for small stuff like this though, where for all you know they're just a very clever dog on the internet.
Seems cryptocurrency related. Lot of marketing fluff.
Who and what are those?
The github repo is slightly better, but not by much:
The project could really use a "What problem is this trying to solve?" section. Is it aiming to replace something existing like HTTPS/Visa/etc?