Broke the #bicycle out for the first time this summer. I got this thing second-hand from Facebook marketplace a couple years back and never really had it serviced. I know I probably should.
Anyhow, the brakes were feeling kind of off, so I decided to have a look at them to see if it was a simple enough problem that I could fix myself. I don't know the first thing about bike repair, but after a few moments of following cables and using my eyes and brain, I was able to determine that whoever last did the brakes on this thing knew even less about what they were doing than I did.
Long story short, my rear brakes actually work now—though I should probably have someone who knows what they're doing have a look at it. I just lack the funds to do so at present.
Also, bike repair is less scary than I originally thought.
DFX4509B (Joshua Mason)
in reply to Misty • • •SkyBlitz
in reply to DFX4509B (Joshua Mason) • • •@dfx4509b even the so called "sovereign" @nextcloud still ignore our call to remove github in the client side (meanin replacing app update and server update) forced call to github for critial update.
because if github close they lose any medium to update their client.
And since they completly ignore the problem that show their hypocrisy.
DFX4509B (Joshua Mason)
in reply to SkyBlitz • • •SkyBlitz
in reply to DFX4509B (Joshua Mason) • • •@dfx4509b @nextcloud i don't even ask that much, i ask at the minimum, removing the hard dependency on github for client update / app install.
because they have backup of their source so be in github will not completly kill them if it stop.
Client update suddently broken with no other way to update than manual update is a ticking bomb waiting to explode.
DFX4509B (Joshua Mason)
in reply to SkyBlitz • • •SkyBlitz
in reply to DFX4509B (Joshua Mason) • • •@dfx4509b @nextcloud people could but i find highly hipocrit to them that they simply ignore the issue.
Because again i can understand CI/CD on github make it harder, but i find unacceptable to force the user server to connect to github for actual update / app install.
Even more when they host themselve a file to "check" if there is an update only the download come from github.
Meaning to make ridiculous small economy of server bandwidth, they prefer endanger the update integrity of their user (if github come to block them).
DFX4509B (Joshua Mason)
in reply to SkyBlitz • • •SkyBlitz
in reply to DFX4509B (Joshua Mason) • • •@dfx4509b @nextcloud not really since, all the binary are in github you would have to make a clone of it and to maintain it up to date clone it often.
but if github block them the "clone" would fall out of date too.
DFX4509B (Joshua Mason)
in reply to SkyBlitz • • •So much for being decentralized and open-source then if even self-hostability and the ability to fork fails you.
This could extend to the entire Fediverse too as given A) a lot of the platforms are also hosted on Github or Gitlab and B) the large instances are hosted on Hetzner VPSes, the US could hypothetically block all three and it's byebye Fediverse.
SkyBlitz
in reply to DFX4509B (Joshua Mason) • • •@dfx4509b @nextcloud it's why i stopped to use them and push people to NOT use them until they fix the issue.
I won't be complicit in sovereinty washing.
DFX4509B (Joshua Mason)
in reply to SkyBlitz • • •At the same time, NextCloud still lets you host your own cloud and doesn't lock your stuff behind a subscription ala Google Drive or OneDrive, either.
And one can still self-host Fediverse instances locally if they have the hardware to spare for it.
Surely there are other open-source, self-hosted cloud alternatives besides NextCloud, though.
Still don't help that the US could hypothetically drop a digital nuke on basically the entire open-source ecosystem, the Fediverse included, by blocking GitHub and GitLab if they ever actually get hostile enough to do that.
Misty
in reply to Misty • • •alexandra catalina
in reply to Misty • • •Misty
in reply to alexandra catalina • • •keithzg
in reply to Misty • • •withinity
in reply to Misty • • •Matt Panaro
in reply to Misty • • •Lunaphied
in reply to Matt Panaro • • •Yora
in reply to Lunaphied • • •Mx. Aria Stewart
in reply to Misty • • •Graeme Hilton
in reply to Mx. Aria Stewart • • •Offbeatmammal
in reply to Graeme Hilton • • •Mx. Aria Stewart
in reply to Offbeatmammal • • •gary
in reply to Misty • • •Misano
in reply to Misty • • •ǝʌɐp
in reply to Misty • • •Verena Rupp
in reply to Misty • • •Passwordsarehard4
in reply to Verena Rupp • • •Laura
in reply to Misty • • •Denis
in reply to Misty • • •Yora
in reply to Denis • • •SpaceLifeForm
in reply to Misty • • •This applies even if you are in the US.
You should avoid any cloud dependency.
Karl
in reply to Misty • • •SkyBlitz
in reply to Karl • • •@karl jut hope it's not one of those who run on us infrastructure, use US CDN and hide everything behind cloudflare ...
because making EU on US server is still US cloud.
Karl
in reply to SkyBlitz • • •ilia
in reply to Misty • • •Yes, it is 100% risk, but the same risk exist with any in-the-cloud service no matter the geography.
Gov't overreach, or corporate decision/malfeasance can remove/restrict access.
NA
in reply to Misty • • •dana
in reply to Misty • • •obrhoff
in reply to Misty • • •@ricobeck Well tbf there is a lot of decoupling happening. It takes time but things are moving. I‘m currently also part of such a project.
Entikan
in reply to Misty • • •DFX4509B (Joshua Mason)
Unknown parent • • •Entikan
Unknown parent • • •JustBob 🪖🇺🇸♒️
in reply to Misty • • •