@Dendrobatus_Azureus yeah I know, thats why I said it. I just think local send is over-hyped. It is meant for LAN files sharing, and this problem humanity solved in like 90s. Diffrent solutions get their own place in my heart. Syncthing for easy NAT traversal. KDE Connect for Apple like experience on any phone. Nextcloud for its web interface. In single houshold setup I'd use SMB (Wndows built-in default) or SFTP (default on Linux). Less configuration, less programs to work with. The standards.
I've read your responses to my toot twice. Thank you 💕 for reacting.
IMHO your though process does not justify the hate you've got for localsend.
Your hate towards, the for you unknown program, localsend is **unfounded*"
Cherish the fact that there is choice and diversity in OpenSource programming.
Stable release versions for synchronizing files exist since the 1970s, not the 1990s. You've clearly not been around long enough to realize that fact **
Ever since plain simple sh existed, such programs were coded. One such program was coded more than fifty years ago and is still in active use.
Please be so kind to use wisdom and intelligence when you react and respond to toots. You acted like a typical snobbish Linux user. Reactions like yours don't contribute anything positive, no one learns from toots like the ones you posted in this thread.
I've never had such responses from the people in the BSD range of Operating Systems.
Even here on the FediVerse the diverse responses from Linux only users and programmers were not of such nature and low caliber.
I'm surprised, yet paradoxically expected your motivational chain.
** If you have been around long enough, to know open source code from the 1970s, look in the mirror and ask yourself why you have reacted in such a manner .
I will still wish you a good day / night, wherever you may reside.
EOF
^Z
#KDE #Gnome #Cairo #library #Xfce4 #airdrop #localsend #kdeconnect #ftp #Linux #ARM #SBC #programming #opensource #technology
@Dendrobatus_Azureus frankly, I dont get hype around localsend. Never used it but I hate it. You must install on both ends, like KDE connect, but KDE connect gives you a lot more than just sharing a file. And if the only thing you need is filesharing, then you have plenty of solutions to choose from - most of them only need serverside, and nothing new to be installed on client. So where is benefit of localsend?
Thank you for your reaction.
Your statement
'never used localsend but hate it'
fascinates me. Can you elaborate on how your process of thought flows when you say that?
I cannot hate something I don't know, I don't test, I don't try out, and I do not even hate things or people, because it is positive energy, that I flipped around to negative energy, which benefits no one; not even me
#KDE #Gnome #Cairo #library #Xfce4 #airdrop #localsend #kdeconnect #ftp #Linux #ARM #SBC #programming #opensource #technology
The WalnutPi 2B is a credit card-sized single-board PC with an Allwinner T527 chip with 8 Cortex-A55 CPU cores, a Mali-G57 MC1 GPU, 2 TOPS NPU, and 200 MHz RISC-V co-processor. https://linuxgizmos.com/walnutpi-2b-is-a-raspberry-pi-style-sbc-with-allwinner-t527-and-2-tops-npu/ #WalnutPi2B #WalnutPi #SBC #AllwinnerT527
I should note that you can not make the mistake of comparing KDEconnect extended capabilities with those of localsend.
They operate on totally different realms.
KDEconnect has a set of plugins which work like functional libraries. There so many that I will have to include a screenshot, just to give you a sample of what KDEconnect can actually do.
Local follows The Unix Principle; it does One thing in a does it very well.
In case you've gotten curious; you can install KDEconnect with its accompanying libraries on another working environment apart from KDE. You do not need to run a full KDE Desktop Environment.
Over here I run KDEconnect on machines which have Xfce4 running, while it's counterpart runs on a couple of Androids.
KDEconnect also runs on Ancient Android Operating Systems
The programming team of KDE does not care where you run it's wonderful software as long as you can enjoy it.
The same goes for The GNOME programming team. I run Cairo Dock ** and GPartED also on Xfce4. In fact I run many Gnome libraries in Xfce4 to have crucial functionality in many parts of the Xfce4 Desktop Environment. Without those wonderful libraries I would run a crippled version of Xfce4.
I have include screenshots from one of my energy efficient desktop computers where I will show you that I run GNOME software and KDE software in Xfce4 DE
I've just finished configuring the weather applet in Cairo Dock which gets its feed from OpenMeteo (not visible in screencap01)
**Update: Cairo Dock is programmed by it's own dedicated team. They have been doing the awesome work since 2007
In screencap 01 you see
* KDEConnect to the left
* Thunar from XFce4 to the right with important GNOME libs giving it extra functionalities
*Cairo Dock from GNOME at the bottom with advanced launch capabilities
#KDE #Gnome #Cairo #library #Xfce4 #airdrop #localsend #kdeconnect #ftp #Linux #ARM #SBC #programming #opensource #technology
Michael Dexter
boosted
Just put FreeBSD 15 on a new Radxa Zero 3E. Was relatively painless. Per the wiki, got the ROCKPRO64 image and dd’ed it to SD, then dd’ed the two files from u-boot-radxa-zero3 package. Booted while monitoring via UART/serial. ntpdate to sync time. And that’s it. Network working. Temps look good. No hacks required.
Now to put it to the test. More to follow. #FreeBSD #Radxa #sbc
Just put FreeBSD 15 on a new Radxa Zero 3E. Was relatively painless. Per the wiki, got the ROCKPRO64 image and dd’ed it to SD, then dd’ed the two files from u-boot-radxa-zero3 package. Booted while monitoring via UART/serial. ntpdate to sync time. And that’s it. Network working. Temps look good. No hacks required.
Now to put it to the test. More to follow. #FreeBSD #Radxa #sbc
Ok, so me and @squeakypancakes dug deep in the sysadmin mines to investigate the disk space issue on our server.
So it turns out the folder /var/services/mastodon/public/system/cache/preview_cards/images is HUGE. 600 GB and all tiny files so it took ncdu SO long to scan.
Does anyone know if we just delete all that cache? We ran tootctl cache clear and it did nothing.
Masto is a strange piece of software isn't it
@ramin_hal9001
Tomorrow. It's actually one of those unreasonably big and hot sbcs. I'll get smaller auxilliary ones. The display has one of those foldy magnetic stands, though I haven't found a configuration that actually holds up the display properly yet.
@moses_izumi
#2026 Travel #sbc
Sorry about the blurry photo!
Some of the kinks are that the palmshell sbc's usb-c is "power only", so I need the hdmi as well. Then, the charger only has one powerful output, so the charger goes into the screen, and screen plugs into the sbc's power.
Perhaps there is a better configuration.
Only FreeBSD has an "expect bugs" driver for the wifi device, so linux currently.
Server full, standby. One of us will get to it asap.
The Akasa Skyline 3 Pro is a new aluminum fanless case for the Asus Tinker Board 3 and 3S (single-board PCs with RK3566 quad-core Arm Cortex-X55 processors). https://akasa.co.uk/search/SKYLINE+3+PRO #Akasa #AsusTinkerBoard3 #SBC #FanlessPC #AkasaSkyline3Pro
3 media
James Valleroy
boosted
Raspberry Pi Imager tool has been updated to v. 2.0.0
Raspberry Pi Imager tool has been updated to v. 2.0.0
Stefano Marinelli
boosted
I've taken the time to read this IT notes Story where we are reminded to use Open Source Code in the diverse way it's intended
I can give you an example regarding the _if tools_
**ifconfig** is in my _muscle memory_ the things that I need executed from this program just fly out of my fingers in reflex mode
I've been using the if tools ever since we needed to _compile everything_ ourselves, when we wanted to run an Open Source Environment, where the kernel was written and delivered in source code only.
If this is the first toot you read by me, I've been with the Open Source community on the Linux side since the alpha versions were coded and distributed through Usenet, in comp.os.unix.*
In that period you were grateful when a task set that you needed to execute, had a program, which would either make your task easier or better manageable, than doing everything by hand in a laborious manner
Ever since the beginning there are different GNU programs, written in the Richard Stallman period, that can do similar things. All you need to do is choose what you like and stick with it
If you do not like the way it works, you can fork it & change the code, if you don't know how to write a line of code, there are _manual pages_ available which you can use as teaching methods to learn how to code yourself
All you need to be for that is an _autodidact_
You have the power of the **Source Code** readily available right in front of you
At a certain point in time _Bram Molenaar_ did not like the way VI worked; he want it more than vi offered. At this point in time Bram Molenaar programmed vim on the _Amiga_ computer. Since the true Open Source form was followed vim was also distributed in Source form and was happily adopted by others who were thinking in a similar manner as Bram Molenaar and they started to contribute to that program.
vi is a vital program on UNIX systems. What Bram has made, is create a _choice_ for people who want it more than what vi offered.
# vim & vi happily coexist!
## This is the beauty of Open Source
At a later point in time this is also what happened with the programmer who wanted more than what the if-tool set offers. Thus the command set of _ip_ was programmed. Similar to vi and vim they happily coexist.
### However on the distribution level something changed.
After a couple of decades I noticed that traditional tools, that have been tried, tested, stable and have withstood the test of time, were dropped from the base installations. You have to go and fetch them yourself. It was even done with _critical tools_ like the if tool set. It's not just one distribution that's doing it but different distributions.
I was busy with an installation; at a certain point I needed **ifconfig** to work on my network interface devices; I needed to configure something on the fly. Imagine my facial expression when I detected that ifconfig wasn't in the base installation!
The machine was in a _chicken egg_ situation because I had &no access to the network_ I had to stop, go to another place fetch the if tools separately, find out that they were dropped for reasons which were totally irrelevant to my work, go back to the machine, install them separately and in the process waste many valuable minutes of time.
It was then that I started to notice the pattern a pattern of **polarization** removing tools which are critical to base installations without leaving a warning
I had to _change_ my setup routine which has been working for decades in a _flawless_ manner, because someone somewhere decided that a good tool set became obsolete.
This polarization is not only in the choice of what commands are chosen to be in the base installation of a distribution, it's in many different sections of the open source community which is what Stefano has shed some light upon.
Polarization because of diversity is totally unnecessary, happy and peaceful coexistance is key
* You can love vim yet cherish vi
* You can glorify emacs yet admire vim
* I can love XCFE cherish LXDE, admire KDE & like GNOME all simultaneously
Depending up on what I'm doing, what machine I am working on (SBC server embedded system), what is needed on the task at hand, I simply adapt and work with the diverse tools available for free.
There is absolutely now need for polarisation or Toxic behavior in the Open Source ENV:
Another example is the direction that Gnome went many years ago.
In that period I used Enlightenment, Gnome, KDE and FVWM simultaneously on different machines. All WM are working in a manner that I like. When however the Gnome programmers decided to strip configuration features of the Desktop Environment, I didn't go on a rant, I didn't bother to fork, because of the massive amount of work involved.
I just left in Peace
Diversity is Vital. GNOME is Vital! We need them all
🦋💙 #Lobi 💙🦋
#Story #Stefano #Programming #FVWM #LXDE #OpenSource #BSD #freeBSD #Linux #POST #X86 #technology #SBC
I've taken the time to read this IT notes Story where we are reminded to use Open Source Code in the diverse way it's intended
I can give you an example regarding the _if tools_
**ifconfig** is in my _muscle memory_ the things that I need executed from this program just fly out of my fingers in reflex mode
I've been using the if tools ever since we needed to _compile everything_ ourselves, when we wanted to run an Open Source Environment, where the kernel was written and delivered in source code only.
If this is the first toot you read by me, I've been with the Open Source community on the Linux side since the alpha versions were coded and distributed through Usenet, in comp.os.unix.*
In that period you were grateful when a task set that you needed to execute, had a program, which would either make your task easier or better manageable, than doing everything by hand in a laborious manner
Ever since the beginning there are different GNU programs, written in the Richard Stallman period, that can do similar things. All you need to do is choose what you like and stick with it
If you do not like the way it works, you can fork it & change the code, if you don't know how to write a line of code, there are _manual pages_ available which you can use as teaching methods to learn how to code yourself
All you need to be for that is an _autodidact_
You have the power of the **Source Code** readily available right in front of you
At a certain point in time _Bram Molenaar_ did not like the way VI worked; he want it more than vi offered. At this point in time Bram Molenaar programmed vim on the _Amiga_ computer. Since the true Open Source form was followed vim was also distributed in Source form and was happily adopted by others who were thinking in a similar manner as Bram Molenaar and they started to contribute to that program.
vi is a vital program on UNIX systems. What Bram has made, is create a _choice_ for people who want it more than what vi offered.
# vim & vi happily coexist!
## This is the beauty of Open Source
At a later point in time this is also what happened with the programmer who wanted more than what the if-tool set offers. Thus the command set of _ip_ was programmed. Similar to vi and vim they happily coexist.
### However on the distribution level something changed.
After a couple of decades I noticed that traditional tools, that have been tried, tested, stable and have withstood the test of time, were dropped from the base installations. You have to go and fetch them yourself. It was even done with _critical tools_ like the if tool set. It's not just one distribution that's doing it but different distributions.
I was busy with an installation; at a certain point I needed **ifconfig** to work on my network interface devices; I needed to configure something on the fly. Imagine my facial expression when I detected that ifconfig wasn't in the base installation!
The machine was in a _chicken egg_ situation because I had &no access to the network_ I had to stop, go to another place fetch the if tools separately, find out that they were dropped for reasons which were totally irrelevant to my work, go back to the machine, install them separately and in the process waste many valuable minutes of time.
It was then that I started to notice the pattern a pattern of **polarization** removing tools which are critical to base installations without leaving a warning
I had to _change_ my setup routine which has been working for decades in a _flawless_ manner, because someone somewhere decided that a good tool set became obsolete.
This polarization is not only in the choice of what commands are chosen to be in the base installation of a distribution, it's in many different sections of the open source community which is what Stefano has shed some light upon.
Polarization because of diversity is totally unnecessary, happy and peaceful coexistance is key
* You can love vim yet cherish vi
* You can glorify emacs yet admire vim
* I can love XCFE cherish LXDE, admire KDE & like GNOME all simultaneously
Depending up on what I'm doing, what machine I am working on (SBC server embedded system), what is needed on the task at hand, I simply adapt and work with the diverse tools available for free.
There is absolutely now need for polarisation or Toxic behavior in the Open Source ENV:
Another example is the direction that Gnome went many years ago.
In that period I used Enlightenment, Gnome, KDE and FVWM simultaneously on different machines. All WM are working in a manner that I like. When however the Gnome programmers decided to strip configuration features of the Desktop Environment, I didn't go on a rant, I didn't bother to fork, because of the massive amount of work involved.
I just left in Peace
Diversity is Vital. GNOME is Vital! We need them all
🦋💙 #Lobi 💙🦋
#Story #Stefano #Programming #FVWM #LXDE #OpenSource #BSD #freeBSD #Linux #POST #X86 #technology #SBC
Grinn GenioBoard is a single-board PC with MediaTek Genio 510 or 700 chips featuring Arm Cortex-A78 + Cortex-A55 CPUs, up to 8GB RAM, and M.2 slots for PCIe 2.0 x1 storage and a wireless module. https://linuxgizmos.com/grinn-genioboard-offers-mediatek-genio-700-som-dual-m-2-expansion-and-cra-ready-security/ #SBC #SingleBoardComputer #GrinnGenioBoard
deutrino
boosted
I really wish the Banana Pi BPI-R3 mini came with a USB3 port and two A7x cores in addition to that quad A53
it's an interesting little device though! I just wouldn't use it for any sort of USB NAS ... it's really gonna be best as a router (especially with 4G support!) and not much else, but it could act as a light-duty data sink in a role like keeping a Syncthing hot copy of your personal documents if you put a tiny NVMe stick in it though.
that Mediatek SoC should have good #OpenWrt support - keyword *should* - don't trust Me (I haven't checked), do your due diligence before buying one!
https://www.banana-pi.org/en/bananapi-router/149.html #DIY #SBC @bananapi
I really wish the Banana Pi BPI-R3 mini came with a USB3 port and two A7x cores in addition to that quad A53
it's an interesting little device though! I just wouldn't use it for any sort of USB NAS ... it's really gonna be best as a router (especially with 4G support!) and not much else, but it could act as a light-duty data sink in a role like keeping a Syncthing hot copy of your personal documents if you put a tiny NVMe stick in it though.
that Mediatek SoC should have good #OpenWrt support - keyword *should* - don't trust Me (I haven't checked), do your due diligence before buying one!
https://www.banana-pi.org/en/bananapi-router/149.html #DIY #SBC @bananapi
The Arduino Uno Q is a weird hybrid SBC
https://www.jeffgeerling.com/blog/2025/arduino-uno-q-weird-hybrid-sbc
#HackerNews #ArduinoUnoQ #SBC #HybridTech #MakerCommunity #TechInnovation
