Your posting this on KBin which implements the twitter style fediverse API and federates with Mastodon.
Click the microblog button … Behold twitter replacement
Your posting this on KBin which implements the twitter style fediverse API and federates with Mastodon.
Click the microblog button … Behold twitter replacement
Engineering is tradeoffs.
A command shell is focused on file operations and starting/stopping applications. So it makes it easy to do those things.
You can use scripting languages (e.g. Node.js/Python) to do everything bash does but they are for general purpose computing and so what and how you perform a task becomes more complicated.
This is why its important to know multiple languages, since each one will make specific tasks easier and a community forms around them as a result.
If I want to mess with the file system/configuration I will use Bash, if I want to build a website I will use Typescript, if I want to train a machine learning model I will use Python, if I am data engineering I will use Java, etc .
You’ve just moved the packaging problem from distributions to app developers.
The reason you have issues is historically app developers weren’t interested in packaging their application so distributions would figure it out.
If app developers want to package deb, rpm, etc… packages it would also solve the problem.
Nice out of date dependencieswith those lovely security vulnerabilities
This could be achieved within the UI and seems like a good idea.
Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.
Having the UI retrieve all local posts with the same magazine/community name (e.g. m/star_trek@kbin.social c/star_trek@lemmy.world). Wouldn’t be hugely difficult, I believe Kbin uses postgres database as the local store. The community/instance should be columns you can search for, it would be a small SQL change.
Even if that wasn’t an option, there is a means to get all of the magazines/communities from the kbin UI and retrieve all posts for a specific magazine/community. So you could do it entirely in a web client.
The combined view wouldn’t change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).
The solution here would be to default to the local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop downso users can choose.
Just to add.
Look at any hobby in your life and break out the money spent vs the enjoyment you got out of it.
For example the Cinema costs me £10 and a film is 2 hours long, meaning my fun time costs £5 per hour.
A £100 console would have to provide me 20 hours entertainment for it to be comparable to going to the cinema.
These days any PS4 game will have 10-40 hours content, but buying them costs money. Popping on CEX website the most expensive PS4 games are £12. Assuning you only get 10 hours of fun from a game…
The question you should ask yourself is are there 3 games on the PS4 you are interested in playing?
The admins to perform upgrades, monitoring, fixes, etc… will require root access to the database. That means they can alter all your posts to say *blah blah blah" if they wanted.
Similarly passwords will be encrypted within the database and encryption algorithms have to be able to go in both directions. Normally they need a seed value to start random generation. The admin defines the seed as a result an admin can decrypt everything in the database.