Fediverse.app VS Mastodon

https://github.com/Big-Fig/Fediverse.app client for Mastodon and Pleroma social networks

Fedi is an open-source client for Pleroma and Mastodon social networks written using Flutter available on iOS and Android

I am started freelancing almost 10 years ago when I was in my first year in university. I was an Android dev freelance, so my experience should be similar to Flutter(currently flutter dev):- it is really hard to freelance and study in university, especially until you have enough experience. In my case, during 2-3 years my life had only two parts: study and work. Work experience is very helpful now, but such schedule not for everyone;- I started from 100$ per app contracts on Upwork (something like quiz guess 1 from 4 ). At the start one app took 100+ hours so my actually rate was ~1 per hour- Motivation: I really like making mobile apps from scratch. Not just finish my own tasks in big thing. I choose project where I can be more like product owner. Help client choose features, prepare AppStore/GooglePlay metadata, do ASO, hire translators + UI/UX designers if need etc. Of course, money is good to point too. I am from Eastern Europe and work for US/Western Europe clients, so I was always satisfied with my salary.- No reputation is ok. I suggest making a small Github sample project to be able to show your code quality for clients. Or you can join an existing open source project. For example https://github.com/Big-Fig/Fediverse.app (Flutter mobile client for an open-source alternative to Twitter on which I working on). Having several articles about Flutter on Medium is useful too.- I prefer small businesses because I like to make app from scratch myself. Another side is big companies where you work only in one specific area in big team. Small business app usually takes ~1 year to develop, so you will have not problems with finding a new job each month.- Currently, work 30h per week. At the start of the career, it was 50-70 per week to maintain a comfortable release schedule for clients. Several years ago worked ~10h. When you have experience work hours is flexible.- Salary. Flutter is really hot right now. I think you can expect to find 10-20$ per hour job if you have a small GitHub project as a code sample + several medium articles about Flutter. Median on Upwork, I think, it is 30-50$ per hour on Upwork. However, I know devs who workin for 75$, 85$ and even 150$ per hour for US-based clients through Upwork and LinkedIn

Interestingly there is some discussion for Mastodon with people asking the limit to be smaller, which raises the question as to the purpose of alt text, and how to properly handle larger text lengths in screen reader programs.

https://github.com/mastodon/mastodon/issues/12268

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Mastodon DMs have absolutely no privacy: https://github.com/mastodon/mastodon/issues/18079

For a decentralized protocol doing things right is much more important than doing things fast, it is very difficult (and in a lot of cases impossible) to break backwards compatibility.

Postmortem on what happened here: https://news.ycombinator.com/edit?id=39305884

The v1 API of Mastodon limits the size of the tree that it will expand for users who are not logged into the server: https://github.com/mastodon/mastodon/blob/main/app/controllers/api/v1/statuses_controller.rb . I am guessing that this or some similar limit applies to threads being returned to unauthenticated users of the web UI. It just arbitrarily stops expanding the replies at some point, including the main thread from the OP.

If a thread is truncated, users expect it to expand automatically and autoscroll when you hit the bottom. In my desktop browser, that does not occur, and there is no indication that there is more to see. This is the situation of the web interface as of Mastodon version 4.2.5.

The issue is very sensitive to observer conditions. If you are logged into the server, the behavior is different. If you use a Mastodon app instead of the web, the behavior might be different. As the tree expands, the cutoffs become different. If you look at the thread on a different Mastodon server, the tree is different because every server has its own view of the Fediverse.

HN needs a best practice for linking to Mastodon threads in a way that provides a consistent experience to HN readers. The average Mastodon server would be crushed by hundreds of HN readers grabbing the entirety of a huge thread all at once, so this might involve some thread-unroll-and-cache service. I tried https://mastoreader.io/ but it did not solve the problem.

Alternately, we push changes into the Mastodon web UI to warn users when they need to click to see more and assume that people will get used to the navigation.

Suggestions?

Fixed in Mastodon v4.2.5 https://github.com/mastodon/mastodon/releases/tag/v4.2.5

>You can defeat the Affero clause by putting the software behind a proxy, for example

Could someone elaborate on this? This is NOT my understanding of the license, and it seems absurd considering e.g. Mastodon is AGPL but the standard install requires a reverse proxy[1]. If using a proxy defeats Affero, why would the Mastodon team do this? Are they stupid?

[1] https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

Mastodon is free and open-source. Go ahead and add the flag:

https://github.com/mastodon/mastodon/blob/main/CONTRIBUTING....

Didn't say anything about freedom of speech. And again: I'm not the one to talk to. I don't have any strong feelings on the topic, but if you do, you should take it somewhere that people who can do something about it will see.

I tried to find an existing discussion to help get you started, but couldn't. You can start one here: https://github.com/mastodon/mastodon/issues

It's easy to sit here on Hacker News and say "they should just..."

Coming up with a standard for an international project will be a long, noisy discussion. You'll tread on internecine conflicts you had no idea about. Old wounds from past related discussions will come out. People will soapbox.

This is why I have no interest in discussing it. It probably won't go anywhere in a place where it actually could. It definitely won't here.