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?

GitHub - beckn/protocol-specifications: Core protocol specification for peer-to-peer consumer-provider interaction

Core protocol specification for peer-to-peer consumer-provider interaction - beckn/protocol-specifications

^GitHub

I had an issue like this recently on Debian testing and it turns out fluidsynth was hogging the sound device and so pipewire couldn't open it. IDK why it was doing that all of a sudden. The symptom was also just having the dummy device.

I think what I did to figure this out was look at the pipewire logs and it said something to the effect that it couldn't open the sound device because it was busy, and according to my bash history I did fuser -fv /dev/snd/* and figured out it was fluidsynth that was using it, which I then disabled or maybe uninstalled because wtf do I need midi for anyway.

Your problem may be different, but I can imagine, theoretically, that all the stuff you're doing makes it so pulseaudio gets first dibs on the (otherwise busy) sound device and so maybe you have misdiagnosed the problem.

I mean something must have changed three days ago, kernel update maybe? You could try running a different kernel and see if this fixes it automagically.

I recently also had an issue where I could only see a dummy device, and that got me wondering. It was caused by fluidsynth hogging the audio device. So maybe could you check something? Look at the log file for pipewire (journalctl --user -u pipewire here) and do fuser -fv /dev/snd/* when it's still in its broken state to see if (maybe) you're misdiagnosing the problem. Because I could possibly sort of imagine that doing the force-reload and start pulseaudio dance might actually have seemingly fixed my fluidsynth issue by inadvertently making it so that pulseaudio got a hold of the audio device.

I thought that it was a kernel update too but the last time it was updated was two weeks ago and nothing else relevant to audio was updated either.

I've restarted my computer and the fuser command does show mutiple instances of fluidsynth. I also ran the journalctl command and I'm getting a bunch of the same error messages over and over again. They are:

mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files

spa.alsa: 'front:0': playback open failed: Device or resource busy

mod.adapter: 0x5794b3a2b2a0: can't get format: Device or resource busy

Nope, that didn't work. In fact, it made the issue worse because now I can't get audio to work at all because my normal audio devices are missing again. I also tried running the commands again and the journalctl command is still giving me the same error messages and fuser states that the only thing running is pipewire.

Also, for some reason, my computer took a longer time to boot than normal and it made me input my password at startup, which I have Linux Mint configured to just automatically log me in without it. So if you have any further suggestions that require a restart, I don't feel comfortable restarting my computer again and I will try them tomorrow.

Oh, I'm sorry. Can you run systemd-analyze blame (and also systemd-analyze --user blame) and look for something, near the top, that took a long time? Also systemctl list-units --failed to see if something has failed to load properly.

I'm afraid to ask, and I should have thought of that, do you remember if uninstalling fluidsynth removed anything else?

Also maybe try uninstalling pulseaudio, it's possible it's fighting with pipewire over the device, but that's just a guess.

Oh good. Maybe you can try restarting pipewire w/o rebooting.

First, check if pulse is running (it might be even if uninstalled), with systemctl --user list-units (search for pulse by typing /pulse) or ps -A|grep pulse kill it with (probably) something like systemctl --user stop pulseaudio or maybe killall pulseaudio. Not sure what's better here, but it needs to be killed if it's running.

Then do systemctl --user restart pipewire pipewire-pulse wireplumber.

Yeah I wrote that stop command wrong, it's supposed to be systemctl --user stop pulseaudio. The relevant errors from journalctl were the "busy" errors. Are they still there? Maybe they're old messages? You can type G to go to the end of the log.

Also, and this is probably my last suggestion, try restarting the socket with systemctl --user restart pipewire-pulse.socket. And maybe restart all the other crap as well for good measure. My theory here is that pulseaudio overwrote that socket with it's own socket, and anything trying to play sound would be trying to connect to the nonexistent pulseaudio, and maybe restarting pipewire doesn't actually recreate the socket, because systemd does that, but I'm not sure that's actually how that works.

Theoretically logging out and in again should also restart all the things pipewire I think, but it's possible that whatever is slowing down your boot is actually slowing down the login, so do at your own risk.

If we assume, for a moment, that your issue was in fact related to fluidsynth, which I kinda still think it might be, because of what fuser and the logs showed, it would be a good idea to undo your module blacklist thingy and reboot.

If your slow boot issue persists, and you try to fix that tomorrow, then try looking at the bootup messages as described here:

askubuntu.com/questions/25022/…

If you reinstall pulseaudio to get back to where you were before, uninstall pipewire, those two shouldn't be running simultaneously.

Good luck and keep me updated if you manage to fix it somehow.

How to enable boot messages to be printed on screen during boot up?

How to enable boot messages, kernel messages and other logs of various services to be printed on screen during boot up?

^{Ask Ubuntu}

Clone it over, try it. If it works, great. Install Linux.

Search "clone windows install" and see what looks good

I run Linux mint with Nvidia card and no problems gaming, basically every game I tried worked (don’t forget to check protonDB and see how to get some games running, but most work right away).

As for dual booting, you need to worry about Microsoft doing evil and trashing the boot loader after an update. Windows is a mess, it spies on you, it boots your computer at 3 am to do updates, and it reboots when your doing work you haven’t saved. So happy I switched. (I do have an old MacBook that has macOS and windows for the few things that need windows or Mac such as modding tools (hardware flashing tools and such but I only use it a few times a year).

For ages I ran two SSDs.

One had Linux one had windows.

The reason is windows like to over write the bootloader when it updates (or did)

So for me... I had the Linux SSD as the primary boot device and I had to select the windows device in grub to boot windows.

It worked for ages and ages until I realized I wasn't using windows anymore.

Edit:
I ran a 1060 Nvidia on Ubuntu / Manjaro / arch / Debian

I never had an issue. Tho I use kde because waaaaay back in the day it was the only DE that wouldn't screen tear.

Lemmy dev here. Making the same post to multiple communities is not possible, so you need to post multiple times tagging a different community each time. Links are taken from Activitypub attachment, but Mastodon only seems to support image attachments. So it is not possible to add other types of links unless Mastodon adds an option for that. Markdown would also have to be supported by Mastodon.

There are various other microblogging platforms on the Fediverse which may support these features and may be better suited to your purpose. For example Hometown, Pleroma, Misskey or Mitra to name just a few.

LibreOffice is very good, and generally its Microsoft Office compatibility is decent. If you ever find it's causing problems, OnlyOffice is known to have better compatibility overall.

You can also try either of them on your Windows PC to see how she likes them, since they are available on all platforms.

Here is a feature comparison between the two.

tl;dr: It's a great piece of software that does everything the vast majority of people will ever want it for. For the other percent, it does some things MS Office can't do and vice versa.

I like Eddy. And at first I’ve liked this essay subject from other creators, but now I just find it shortsighted. The phone isn’t the problem, just like the television and radio weren’t the problem. It’s the content you put on it.

You can watch great TV shows—documentaries, masterpiece dramas, etc. Or you can watch slop.

You can do incredible stuff with your phone—get directions, listen to almost any song ever recorded, learn about the night sky, watch documentaries anywhere you are, write, create your own content, sky’s the limit. Or you can install slop and brain rot apps like Twitter.

You don’t have to pull a stunt like locking your phone away. Just delete the slop. Be more mindful of what an app and the company behind it are, and either limit your use of it or simply don’t install it at all.

I disagree. Yes there can be good intermediate steps, but deleting slop is not even half as healthy as locking a phone away.

1) Interruptions

Not just phone calls or texts, but things like typing an email on the phone and then seeing a text or having the GPS interrupt your train of thought by yelling "Continue straight for 5 miles". Brains hate interruptions. Those are still going to exist even when the slop is gone.

2) Resisting a temptation is exhausting. "not eating candy is healthy"... yes but having a candy bowl right next to your desk is exhausting. It takes 2sec to open a twitter link in the browser. Uninstalling an app is like moving the candy bowl to a nearby room, yeah its better, but it only takes 30 sec to reinstall.

Turning off the dopamine machine (not eating candy) is one thing. But Eddy was showing something a lot bigger than that; how it feels to delete his ability to access to the temptation. He didnt know the code to unlock the phone.