livingcoder

joined 1 year ago
[–] [email protected] 2 points 1 year ago

Yeah, looking at these notes, they don't appear particularly useful for my purposes either. It's a challenge to find good, ready-to-use material. Thanks for sharing them, though.

[–] [email protected] 3 points 1 year ago (1 children)

If I wanted to use these notes as direct source material for an open source quiz project, would that be okay? I've been looking for good, free, open source notes, Q&As, and diagrams but it's not easy.

[–] [email protected] 1 points 1 year ago

I appreciate everyone's feedback! I'll report back if I have any issues in my specific case, but hopefully I have the same experience all of you have had.

[–] [email protected] 1 points 1 year ago

I had issues searching for Lemmy communities until I updated my docker-compose to give the "lemmy" container it's own network.

https://lemmy.austinwadeheller.com/comment/14247

[–] [email protected] 2 points 1 year ago

I don't know... if joins are so good, why did it take so long for them to show up via SQL? /s

[–] [email protected] 1 points 1 year ago

Here's a post on Mastodon that links to their blog where they describe different clients.

https://writing.exchange/@erlend/110616473377954593

[–] [email protected] 2 points 1 year ago

I haven't experienced any crashes. I'm just getting annoyed with it resetting the view when I rotate my phone by accident. It takes me back to Local and changes my filter back to default. Painful.

[–] [email protected] 0 points 1 year ago (1 children)

Yeah, I was imagining that it was connected to my phone, but I'm not sure how to setup my phone such that it responds to messages like that - I've never tried sending my phone bluetooth messages and I don't know if that would be possible (to go watch to phone via BT and phone to self-hosted server via mobile network). Can I have an app always listening for messages over BT? Hopefully I don't need a PiZero W in my pocket: watch to Pi via BT as a relay, Pi to phone via Wifi hotspot, and phone to self-hosted server via mobile network. Sounds like a lot of work, lol. I'll think about applications for it. They'd have to be pretty awesome.

[–] [email protected] 3 points 1 year ago

I feel like putting it in a VM is probably overkill. I just have everything running in Docker containers and it's pretty good like that.

[–] [email protected] 0 points 1 year ago (3 children)

https://lupyuen.github.io/pinetime-rust-mynewt/articles/watchface

Section 1, step 2 states "update: To update the Watch Face with the current date and time. This is called every minute by the PineTime Firmware to refresh our Watch Face."

Good to know that it's touch screen. I would love if I could push a button on this watch and run a POST request to my server. Do you happen to know of that's possible?

[–] [email protected] 0 points 1 year ago (1 children)

I think we may be talking about two different things with regards to corporate control. I'm saying that, in the case with Redhat specifically, that their injection of a fee to access the source code now no longer makes the code freely available to downstream repositories. If they comically charged a billion dollars to access the source code (with a GPL) it would practically become closed source, so I'm curious why any entity can charge any amount to access open source software. And if it's totally legal with this type of license, doesn't that mean that we should be avoiding GPL at all costs?

[–] [email protected] 1 points 1 year ago (3 children)

Correct me if I'm mistaken. What I read from your post sounds to me like you think that we should accept that a company will inject a revenue stream into the process that we all were working on as an open source project. We weren't expecting to get paid, so why not allow the company to get paid, regardless of the downstream impacts for other projects that once relied on the project being completely free and open. Do I understand that properly? I don't want to misrepresent your intent. I feel like I must be misunderstanding something.

view more: ‹ prev next ›