CPAPtalk.com

Sansnap wrote: ↑

Tue Feb 12, 2019 11:46 pm

New member here and sad to see this turn of events. Regardless of egos involved, blame placed and insults hurled I urge the folks involved in this kerfuffle to sort it out. For those of us who with serious apnea Sleepyhead is indispensable. It saves lives.

Let's review: Sleepyhead SAVES LIVES.

Please consider this carefully as you slug it out. Real people depend on Sleepyhead and are affected by this recent turn of events.

You're quite right.

Unfortunately, the original author of sleepyhead never has cared about the people that need to use it. It was his own personal project, he just happened to make it available for others to use.

His care and concern for the users is exhibited by his decision to shut down the project, instead of trying to work with others.

This entire fuss came about because people on his dev team wanted to help the users by getting a more usable version available to YOU, the users... and ... well, you see what Mark Watkins preferred.

Sleeprider wrote:Have you looked for the Facebook group? Gone.

Not gone, just closed! And I know why: the group SleepyHead was open to view, but when I wanted to thank him for bringing the downloadpagina back and reminding people of Bob's Birthday, I had to fill a firm... Obviously I was banned there too. Now it is entirely closed with 944 members and my solicitation still open. I just am not allowed to read it anymore...


Verzonden vanaf mijn iPhone met Tapatalk

A KLERK wrote: ↑

Wed Feb 13, 2019 12:35 am

Not gone, just closed!

Closed facebook group for open-source software. That is unusual.

yrnkrn wrote: ↑

Wed Feb 13, 2019 1:38 am

A KLERK wrote: ↑

Wed Feb 13, 2019 12:35 am

Not gone, just closed!

Closed facebook group for open-source software. That is unusual.

He can't control the narrative as easily if other people are allowed to post. It takes time to delete all the posts he doesn't agree with.

Dog Slobber wrote: ↑

Tue Feb 12, 2019 2:19 pm

• While often complaining that his contribution has not been respected, his actions demonstrate a complete lack or respect for the contributions of others to the project.
• Almost every post by those close to him (and now considered his traitors), expressed gratitude and flattery that was completely dismissed by him.

This was /thread for me. Seems to say it all.

palerider wrote: ↑

Wed Feb 13, 2019 1:40 am

yrnkrn wrote: ↑

Wed Feb 13, 2019 1:38 am

A KLERK wrote: ↑

Wed Feb 13, 2019 12:35 am

Not gone, just closed!

Closed facebook group for open-source software. That is unusual.

He can't control the narrative as easily if other people are allowed to post. It takes time to delete all the posts he doesn't agree with.

This is one of the things that blows my mind in the world today. I don't have facebook and I am am astonished at the RULES and "moderation" people follow and that they don't speak freely. Some seem to still participate and try to get their point across under the burden of these rules in "covert" ways like children in detention?

Clearly you can control and make totally false realities on the internet ... which sure doesn't seem healthy to *me*?

...but what do these people do in real life when faced with words or ideas that they cannot just delete? Do they crumble? Become violent? Freeze up until someone takes them by the hand and leads then to safety?

I guess if you wanted to fight a war and everyone has forgotten that "sticks and stones might break bones but words can never hurt me" ... well then it would be pretty easy to just control people with words?

I thought it was just a "phase" but ... are we really devolving like that?

Seems like the future is in FREE SPACES ... Where are the calls to LET FREEDOM RING?

I know HOAs and gated communities are becoming a joke (finally ... like, duh!) and the real property value is in good zoning and the bundle of rights that allow you to USE and ENJOY your land.

Seems like that should be the trend on the internet too?

All people use whatever tools are at hand to do their best to control the narratives about themselves; it's just that some are better at it than others.

Well, with the possible exception of those attempting to use the George-Costanza-Opposite method for public relations.

https://youtu.be/RerJWv5vwxc

And in Cyberspace, no one can hear you be honest about yourself.

All in all, I find this entire thread makes about as much sense as someone deciding to edit the editors out of the Oscars. Hey, just me.

So I think I'll do the board a favor and unsubscribe from this thread so I'm not tempted to post more in this thread. I'll do my damage in other threads.

Thanks for all the fish.

Sleeprider wrote: ↑

Tue Feb 12, 2019 8:26 pm

it was a shared effort that included countless hours by others, and he has erased all of our records, correspondence and files on every internet venue he controlled.

I can't really speak to motives or what has/hasn't happened. I noticed the drama on a forum just today.

However, this is one of the reasons why I tend to avoid participating in forums like facebook/discord/etc for FOSS work. No way to just download the data/etc and it tends to be susceptible to this sort of thing.

As far as I can tell 1.1 is untagged but just uses commits from https://gitlab.com/sleepyhead/sleepyhead-code.git, so the source is still around, which is probably the most important thing. I'm sure it has been cloned dozens of times by now, and is GPL, so it will live on under one name or another.

I did appreciate Mark's tremendous contributions. I got out when it was ported to QT5 and that was obviously a ton of work. I think the move to modular importers makes sense, though I don't really see the point in allowing them to be proprietary. They're just file formats - it isn't like they contain some kind of critical IP even if vendors tend to be secretive about such things. I doubt most vendors would be any more likely to release importers even if they didn't have to be GPL, but then again I haven't talked to any.

Hopefully everybody will cool down and we'll continue to see new machines get supported. I do miss having SleepyHead, but all the ASV support was reverted in 1.0 I believe and now I'm on a new machine that doesn't seem to be supported. Maybe one of these days I'll take another look at it.

Have you tried 1.1?

1.0 beta 2 used QTWebKit which got deprecated, stalling SleepyHead development. 1.1 was an attempt to remove all the QTWebKit bits for the newer Qt versions.

Mark also added a couple of new machines supported.

I think Mark is taking a much needed break away from this. Some people are working on a fork of SleepyHead to improve the stability of 1.1 The GitHub code has 3 commits, IIRC, after the testing builds. I think they mainly affect Linux though.

prodigyplace wrote: ↑

Wed Feb 20, 2019 5:45 pm

Have you tried 1.1?

No. Is the source posted somewhere? The repository on the sleepyhead site doesn't have a tag for 1.1. I know there are binaries floating around out there, but getting precompiled binaries working on random distros on Linux tends to be painful, and I'll probably package it up which requires the sources anyway...

rich0 wrote: ↑

Wed Feb 20, 2019 7:07 pm

prodigyplace wrote: ↑

Wed Feb 20, 2019 5:45 pm

Have you tried 1.1?

No. Is the source posted somewhere? The repository on the sleepyhead site doesn't have a tag for 1.1. I know there are binaries floating around out there, but getting precompiled binaries working on random distros on Linux tends to be painful, and I'll probably package it up which requires the sources anyway...

There's a statically compiled binary here:

https://www.sleepfiles.com/SH-test/1.1. ... a7-linux64

I'm using it on ubuntu 18.04

palerider wrote: ↑

Wed Feb 20, 2019 7:17 pm

rich0 wrote: ↑

Wed Feb 20, 2019 7:07 pm

prodigyplace wrote: ↑

Wed Feb 20, 2019 5:45 pm

Have you tried 1.1?

No. Is the source posted somewhere? The repository on the sleepyhead site doesn't have a tag for 1.1. I know there are binaries floating around out there, but getting precompiled binaries working on random distros on Linux tends to be painful, and I'll probably package it up which requires the sources anyway...

There's a statically compiled binary here:

https://www.sleepfiles.com/SH-test/1.1. ... a7-linux64

I'm using it on ubuntu 18.04

Not looking for a statically compiled binary. I'm looking for the source for that binary.

I don't get why they're even distributing the binary without the source being obviously available. If Mark is ticked at them aren't they concerned about getting sued over a GPL violation?

rich0 wrote: ↑

Wed Feb 20, 2019 7:31 pm

Not looking for a statically compiled binary. I'm looking for the source for that binary.

Never mind - a kind soul sent me the hash - it just isn't tagged.

Hopefully those who fork the project will continue to keep the development branches public.

rich0 wrote: ↑

Wed Feb 20, 2019 7:31 pm

palerider wrote: ↑

Wed Feb 20, 2019 7:17 pm

rich0 wrote: ↑

Wed Feb 20, 2019 7:07 pm

prodigyplace wrote: ↑

Wed Feb 20, 2019 5:45 pm

Have you tried 1.1?

No. Is the source posted somewhere? The repository on the sleepyhead site doesn't have a tag for 1.1. I know there are binaries floating around out there, but getting precompiled binaries working on random distros on Linux tends to be painful, and I'll probably package it up which requires the sources anyway...

There's a statically compiled binary here:

https://www.sleepfiles.com/SH-test/1.1. ... a7-linux64

I'm using it on ubuntu 18.04

Not looking for a statically compiled binary. I'm looking for the source for that binary.

I don't get why they're even distributing the binary without the source being obviously available. If Mark is ticked at them aren't they concerned about getting sued over a GPL violation?

"them" isn't distributing anything, that's the mirror that mark put that binary on.

I'm not even sure that a single line of code has been written on a fork yet...

The source should be at: https://gitlab.com/sleepyhead/sleepyhead-code

Whatever gets done--will get done when somebody DOES it.
---Whichever "somebody" cares enough (and can) to just DO IT.
Thanks to Mark for starting this project.
Thanks to whoever continues it.
It is not about "who" so much as what.