djtech

joined 1 year ago
[–] [email protected] 3 points 9 months ago

The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

[–] [email protected] 6 points 9 months ago (1 children)

Thanks for your reply; i won't work with firmware-level aspects of the stack, as my plan is to write the userspace daemon, while keeping the kernel-levels modules identical and to communicate to them via HCI sockets, as they are implemented by Linux and with them I can talk directly to the bluetooth controllers.

I'll check out Android's project and double-check for security vulnerabilities in older version of the protocols tho, so thank you again for replying.

80
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

Hi everybody,

i'm a long time Debian user and, while i've always loved the Linux experience, the bluetooth side of things was always a little bit... painful.

Lately, i've been digging on how bluetooth on Linux works (i knew about BlueZ, but i didn't know about HCI sockets, standard protocols for bluetooth controllers, ...). Seeing how Android manages to work fine with bluetooth (yes, i know, money and company support, blah blah blah), i was thinking about re-writing the bluetooth daemon, in order to be modern, modular, safe (written in Rust), stable and retro-compatible (exposes the same D-Bus APIs as BlueZ) I already found some documents about HCI socket in Linux, HCI communication with bluetooth controllers, HID standards for Bluetooth, etc...

My questions are:

  • is this a good idea?
  • does somebody want to collaborate?

Thanks for reading.

EDIT: The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

[–] [email protected] 13 points 10 months ago (1 children)

Fork the feature one, get the diff of the commit that patches the bug and apply the diff to your fork.

Now compile and test.

[–] [email protected] 1 points 10 months ago
[–] [email protected] 2 points 10 months ago

A quick research tells me that there aren't patches for other emulators, but the protocol seems well described, so making those patches is possible. I could also take a look at Alacritty source code and deicide if I could make this project work.

[–] [email protected] 9 points 10 months ago (6 children)

For rendering high quality images in the terminal, check out the Kitty graphical protocol. I don't know if they are any python libraries to use, but I think that they are. P.S. This seems to work well https://stackoverflow.com/questions/58138638/how-to-display-graphical-images-in-kitty-terminal-using-python

[–] [email protected] 6 points 10 months ago

So... emacs?

[–] [email protected] 46 points 10 months ago* (last edited 10 months ago)

mhhhhhhhhhh

The project is trolling fs

 
 
[–] [email protected] 0 points 10 months ago* (last edited 10 months ago)

What do you mean by AppImage permissions? A sandboxing feature like "access only those directories, those /dev devices, ..."

EDIT: obviously this isn't just for AppImage, but I tested it with AppImage and it work well. Another tip: if you want a package manager for managing AppImage installations try zap (https://github.com/srevinsaju/zap)

In that case, take a look at bubblejail. (https://github.com/igo95862/bubblejail)

[–] [email protected] 3 points 10 months ago

Before the "systemctl" command: try removing the GPU and booting it up without the GPU If it works, you can skip the "systemctl" commands

[–] [email protected] 3 points 10 months ago (10 children)

Run "journalctl --lines 200" and send photos of output.

NOTE: This is all of the logging of the computer, and it's long (that command select the last 200 entries), so you might have to scroll down using the PageDown key (or arrow down) in order make the photos of everything

[–] [email protected] 3 points 10 months ago (13 children)

The Shell where you typed "systemctl reboot" and "exit".

If you are running KDE neon, try "apt update" and "apt upgrade". If It doesn't work do "sudo apt update" and "sudo apt upgrade"

 

crosspostato da: https://lemmy.world/post/7542906

So, Lemmy is sometime missing content. I don't regret switching from Reddit to Lemmy but, expecially for niche communities, the content isn't always here.

My idea is to fix this is a Fediverse-based content relay named Relly.

Relly allows you to select RSS feeds, Mastodon users, Mastodon hashtag and Mastodon instances (so, the top posts on that instance) as sources for content, and post them to your favourite Lemmy community.

There are several features which make Relly better and anti-spam:

  • Limits for a source (example: only up to 5 posts a day from this RSS feed)
  • Limits for a community (example: only up to 5 posts a day to !archlinux)
  • Global limits (example: only up to 10 posts made each day)
  • Opt-out for servers & communities (instance and community moderators will be able to ask to be put in the UNLIST, which blocks by default Relly on your instace/community; this isn't an anti-spam, as it is more a tool for avoiding common users to use Relly in a malicous and spammy way)
  • Order posts (so, if i have 10 RSS posts and 10 Mastodon posts and a global limit of 15 posts, you can either have the 10 RSS posts and the 5 most upvoted Mastodon posts, or some RSS posts and some Mastodon posts [always the most upvoted])
  • Multiple communities (post the same content to different communieties, or set up a fraction [ex. 50%], so that each post has a certain percentage to be posted on a certain community)
  • Dynamic limits: You can set an objective of active users/post made in the last 24 hours, so that the limits (either for a specific source, a specific community or globally) will be reduced. Example: if you set a objective of 50 posts, and 25 are made, the limits of Relly will be 50% of what they were originaly set to be; this allows Relly to completly stop posting on a community if the objective was already reached.
  • Do not repeat: before posting a link, checks if it was already posted in the community in a specific time period (by default, 48 hours)
  • Modularity: new post sources and post outputs can be implemented; an example could be an e-mail output, so that you can run Relly in local and recieve an e-mail everyday with your favourite news)

Relly is designed to be used by moderators of communities, but users can also use it. A user should always ask the moderator if it is OK to use it. A moderator should always ask the admins if it is OK to use it. Moderators, if they are the one using it, should also make public the list of sources, and allow the community to discuss possible edits to the list. The admins should put in the sidebar notes if Relly is OK to use for moderators of communities.

At the moment, Relly is just the idea that I presented here; I want to hear the community's feedback, and if the community is OK with this project being made, I will start working on it (I will make it in Rust and release under the MIT License).

 

Just wanted to ask: what do you not like in Lemmy (Lemmy as communities, server and clients)?

This is just a way for me to get some feedback from the community.

 

Hello everybody,

I'm trying to read a (probably damaged) microSD card from my computer (tried with two different computers, both Arch Linux, which can read other card without any problems). There isn't any singal of life (no /dev/sdX, nothing with GParted, testdisk, ...); the only thing that I found was in dmesg. Here's the output of sudo dmesg | rg "mmc0":

Any idea on how to resolve?

view more: next ›