Avatar
ElectronicMonkey
45c41f21e1cf715fa6d9ca20b8e002a574db7bb49e96ee89834c66dac5446b7a
Author of nostr blogging client: https://flycat.club/

it is not true that everyone will run their own relay. but it is true that some tech people will(like they doing open-source things) and some non-tech people will too once they have the tool and be capable of. And I believe it is also true that most people will find one of their friends/families/public figures willing to offer them relays as public goods. so that is why relay-client mode makes sense to me other than p2p.

こんにちは、何か手伝えることはありますか ?

wrong. if that is the case, relays should be force to communicate with each other.

ok just finished our first design call. at first there is only me talking plan to myself, and then somebody pop in and I was kind of panic lol. I went through the things we want to ship in the next version(v0.2.2) of flycat this week and then found the guy just pop out. I spoke pretty awful and sorry if that scare you off. anyway the next iteration release looks like this, you can check out here https://github.com/users/digi-monkey/projects/1/views/1 and next desgin-call meeting will be in the next wednesday, I will keep trying

primal 这里我的 following 的 feed 在哪看,找半天没找到..

As development goes by, I slowly realized that there is so much needs to be done in order to make a good client and it will be hard to keep on if there is only me in the project. So here are three things I am trying to do to bring better open-source development to flycat.

1. I am using Public GitHub Project to manage the development of flycat. What to ship, Which version to release, and when is the next iteration, everything is fully open for anyone to check and contribute. https://github.com/users/digi-monkey/projects/1/views/1

2. Another thing I am trying to do is to build a routine to ship the regular versions. it will be one minor version a week. Previously there is little planning going on. And it is bad.

3. I love nostr:nprofile1qqs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qf3fjwq 's idea about hosting a regular habla.news design-call meeting. It seems like a great way to do open-source and communication. So the third thing I want to do is to copy that nice mechanism and apply it to my project. the first meeting will be tonight at 9 PM nostr:note1wcw0wuzk2j50ls22e2rrp5xd8sshu3flcgk5f3hjhnvqpvxx6y9q72tpd4 If there is no one attended I will still go through agenda by myself. so, no worries.

Finally, if you are reading here, it is obvious that you are chosen by god to help me so just read the following contributing instructions and get involved https://github.com/digi-monkey/flycat-web/blob/master/docs/develop.md

as for why under the global mode, previous there are some different modes, and global mode means using a fix group of relays and it turns out other modes might not be a good idea(like the one fastest), you can click the about relay mode under the dropdown. we plan to remove other modes later anyway.

hi sorry to hear that. under the drop-down, click global mode and there should be a group named nip65 relay list in the submenu, can you see it on your side? If not, can you share the screen shot maybe encounter bugs.

did you know that flycat supported PWA? That means you can install flycat as a web app on your phone via Safari (ios) or Chrome (android). It still has a log of things to fix before we get you an acceptable mobile experience but you can try it now at https://flycat.club/landing We greatly value your feedback and hold it in high regard.