Posts by chebra@mstdn.io
(DIR) Post #AozohnMz51Cm2y8s3k by chebra@mstdn.io
0 likes, 0 repeats
@santiago @tilvids @mmu_man @Framasoft @peertube Why not #fdroid ? Easy way to avoid these walled gardens. Maybe we should promote it more by making releases there first!
(DIR) Post #AozrCcBstQssGFm2vw by chebra@mstdn.io
0 likes, 0 repeats
@peertube more work than Apple and Google? Like who should we be bending out backs for? The oppressors, or the users?
(DIR) Post #AqMli8xj0xl5aZOaNk by chebra@mstdn.io
0 likes, 0 repeats
@dansup I wonder if those VCs contributed to the kickstarter... lol no, I don't wonder.
(DIR) Post #AqRH8NaJ97EXgCGwFs by chebra@mstdn.io
0 likes, 0 repeats
@dansup Speak about what you need. Constantly.
(DIR) Post #Aqsn1y5LpGmV8olwNU by chebra@mstdn.io
0 likes, 0 repeats
@mntmn I'm running a group of 60 students and my family on Matrix. The most common problem is Android battery optimization will put the app in background and people stop receiving notifications if they didn't open the app for 3 days. Second problem is losing the recovery phrase and losing the ability to read old messages. Some combinations of client and server make this worse by strange UX around recovery phrases or unimplemented parts but that's slowly improving.Otherwise all good, recommended.
(DIR) Post #AtxK7J9QD3UPzZCkBk by chebra@mstdn.io
0 likes, 0 repeats
@krille @matrix special reactions... so that means zero interoperability with other clients?
(DIR) Post #AtxK7KHc05dRVG2naq by chebra@mstdn.io
0 likes, 0 repeats
@krille @matrix Well thanks.. but I'm in matrix and open-source exactly for the interoperability. What's the motivation behind breaking it? I'd expect that from Microsoft or Apple...
(DIR) Post #AtxKp1lkCENWpBycAC by chebra@mstdn.io
0 likes, 0 repeats
@matrix Guys, I'm talking about real use-case - imagine a group of 70 people where everyone has different client app and on a different homeserver. Suddenly one guy posts a new cool checklist.. what will happen? You really haven't considered this scenario?
(DIR) Post #AvWjyOQ7Cvyx8OZHhg by chebra@mstdn.io
0 likes, 0 repeats
Dear @matrix , what is the point of maintaining specs of a protocol, if you then decide to break it on matrix.org server so all client apps have to choose between following the specs XOR being compatible with your server? If the Foundation is really the steward of the protocol, then do something about this. It is happening way too often. Currently here https://spec.matrix.org/v1.14/client-server-api/#client-behaviour-9
(DIR) Post #AvWjyT2Y1z6LSka2AC by chebra@mstdn.io
0 likes, 0 repeats
@andybalaam @matrix Unfortunately no, this is not a synapse problem, only matrix.org instance problem and I don't see any way to report issues just for that instance. Context: spec says that there is a POST route for deleting devices. Client apps implement it. Now matrix.org decides to do things differently without telling anyone. This route returns 404 from matrix.org, but works on any other synapse. Some people in some random chat rooms discovered that we are supposed to use account.matrix.org
(DIR) Post #AvWjyTygXpbcN3mSmW by chebra@mstdn.io
0 likes, 0 repeats
@andybalaam @matrix Here Cinny chat recently encountering the issue with "tulir" (seemingly representing matrix.org?) confirming that this break of all spec-following clients was done by design
(DIR) Post #AvWjyVxhAU0CWZKhW4 by chebra@mstdn.io
0 likes, 0 repeats
@andybalaam @matrix So would you say that this is the bug of specs? So in case of differences client developers should take the matrix.org server as canon? Because I still don't think that's the right way. Matrix.org server is the one failing to implement the specs here.
(DIR) Post #AwfenqdDH2tdtg0AWO by chebra@mstdn.io
0 likes, 0 repeats
@aesthr - variable shadowing, otherwise known as reusing the same variable name for a new thing- snake case (I will die on this hill!!)
(DIR) Post #AxINoCToC17AETF9Hc by chebra@mstdn.io
0 likes, 0 repeats
@gyptazy hmm that snac url with `/inbox` didn't work for me #snac 2.81 (got 405). I used the one with `/actor` and that passed successfully.
(DIR) Post #B1h2e6T6F7Cmt7h9qC by chebra@mstdn.io
0 likes, 0 repeats
@organicmaps @Kalytis @grischard really smooth changing the scope of the question. And I still want to know whether the person who got you kicked from github for vacationing in a "disputed territory" is still on your team? Will they be receiving some of the donations?
(DIR) Post #B1i0qSL4kUBNRXfFXU by chebra@mstdn.io
0 likes, 0 repeats
@organicmaps @Kalytis @grischard my goal is to avoid supporting putin's supporters. I've been asking you directly about this many times before, you were gaslighting. This is the first time you said anything about a hijacking attempt and it raises more questions than answers. Come clean or I'll have to continue asking.
(DIR) Post #B1iAsfgB7TqCwFEJlI by chebra@mstdn.io
0 likes, 0 repeats
@organicmaps oh I do believe the part about the contributors and relatives. But what about the leadership? Put this https://github.com/vshymanskyy/StandWithUkraine/ in your main github readme if you mean it.
(DIR) Post #B1iCqL1x7WB2E6QiQq by chebra@mstdn.io
0 likes, 0 repeats
@organicmaps @grischard Are you talking about CoMaps? You think people here don't know about that project? If the position of your board were clear, we wouldn't be here asking. You really need to stop talking in riddles, it makes you look untrustworthy. I'm gonna ask CoMaps for the story too and if only one of you is able to give a straight answer, I think that will make it pretty clear.
(DIR) Post #B2AndZ1MvffCaCo4um by chebra@mstdn.io
0 likes, 0 repeats
@matrix @bagder Half of the problems are caused by matrix.org instance not following the actual matrix protocol specs, or matrix.org instance introducing changes that break compatibility with other (non-synapse) servers or othe (non-element) clients.
(DIR) Post #B2B4v17zNeVDtkoN1s by chebra@mstdn.io
0 likes, 0 repeats
@matrix should, but often aren't. I'm saying as a long time daily user of matrix. The number of problems caused by this is so high that I totally understand how a non-technical person will end up with a broken account sooner or later, and never come back. Dismissing feedback won't help. Prioritize compatibility. Prioritize stability. Prioritize "users will never see Unable to decrypt". New features don't matter if it keeps breaking.