parse-server
Mastodon
Our great sponsors
parse-server | Mastodon | |
---|---|---|
39 | 1,224 | |
20,613 | 45,874 | |
0.2% | 0.8% | |
9.4 | 10.0 | |
about 20 hours ago | 2 days ago | |
JavaScript | Ruby | |
Apache License 2.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
parse-server
-
The 2024 Web Hosting Report
Backend as a Service (BaaS) goes back to early 2010โs with companies like Parse and Firebase. These products integrated everything a backend provides to a webapp in a single, integrated package that makes it easier to get started and enables you to offload some of the devops maintenance work to someone else.
- Placemark is going open source and shutting down
- Thoughts on Parse Platform / Server
-
Tools for scanning commits?
Prototype Pollution Fix
-
How to set up a Parse Server backend with Typescript
Parse Server is a great way to quickly spin up a backend for your project. Parse is a Node based utility that sits on top of ExpressJS.
-
A Guide On Appwrite
Parse
- [SERIOS] Solutie backend + DB pentru o aplicatie web
-
Free online DB for production app
You can try https://parseplatform.org/, it is self-hosted if you need. And also there are a number of cloud services with compatible API, like https://www.back4app.com/ It has dart-friendly generated API client, much simpler than firebase and is built on top of postgresql and mongodb.
-
Backend (auth/payment) options for Flutter app and web.
Parse - https://parseplatform.org/
-
Supabase Series B
Not to crash the party or anything. Supabase is great and all but in terms of feature completeness and getting actual products built, it doesn't come close to Parse[0].
Same with Appwrite. Both of these are very popular but they either lack essential features or have them behind a subscription wall. For example, the OSS version of Supabase (last I checked) doesn't include the edge functions which are really important for easily computing stuff on the server side. Parse on the other hand is 100% open source and has a huge feature set. It's older than all of these lo-code tools and actually helps solve the issues one comes across when using such tools.
Another thing is extending these tools which is a pain. For example, Parse supports multiple databases by default (postgres & MongoDB) and the ability to write a custom adapter if you need something else. Similarly, if you at any point need to go 100% custom it also makes that possible so you are never locked in. These tools however don't have that level of low-level control and are general all or nothing kind of tools best for small-to-medium sized problems which don't have a lot of room to grow.
But both of these (Appwrite & Supabase) are super markety. Appwrite is all over the place with their ads, Supabase got a huge trend when it launched etc. Parse on the other hand is not too good at marketing their product being fully community run which is one reason not many know of it. Another is their not-so-fancy docs.
I have no stake in any of these products: just my conclusion after having tried all of these.
Mastodon
-
Open source at Fastly is getting opener
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).
-
Bluesky announces data federation for self hosters
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.
- External OpenID Connect Account Takeover by Email Change
-
Ask HN: Best practice for posting links to large Mastodon threads?
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?
-
CVE-2024-23832 Mastodon Vulnerability: Remote user impersonation and takeover
Fixed in Mastodon v4.2.5 https://github.com/mastodon/mastodon/releases/tag/v4.2.5
-
Unity's Open-Source Double Standard: The Ban of VLC
>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...
-
You Can't Follow Me
Mastodon is free and open-source. Go ahead and add the flag:
https://github.com/mastodon/mastodon/blob/main/CONTRIBUTING....
- Change Referer value to something generic such as "urn:activitypub:Mastodon"
-
Welcome to the public domain, Steamboat Willie
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.
-
Mastodon with Docker rootless, compose, and Nginx reverse proxy
I've written down how I set up my Mastodon server here. This includes some topics that seem not well covered currently:
- use nginx reverse proxy with the official nginx.conf [1], but with some changes needed for compatibility with docker
- use rootless docker, for security, together with bind mounts, for maintainability
- use compose, with some modifications to the official docker-compose.yml [2] that make life easier and are compatible with the reverse proxy
[1]: https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...
[2]: https://github.com/mastodon/mastodon/blob/main/docker-compos...
What are some alternatives?
Appwrite - Build like a team of hundreds_
diaspora* - A privacy-aware, distributed, open source social network.
supabase - The open source Firebase alternative.
Misskey - ๐ An interplanetary microblogging platform ๐
nestjs-graphql - GraphQL (TypeScript) module for Nest framework (node.js) ๐ท
Lemmy - ๐ A link aggregator and forum for the fediverse
ObjectBox Java (Kotlin, Android) - Java and Android Database - fast and lightweight without any ORM
Friendica - Friendica Communications Platform
MongoDB - The MongoDB Database
GNU social - GNU social is social communication software for both public and private communications.
Vapor - ๐ง A server-side Swift HTTP web framework.
nostr - a truly censorship-resistant alternative to Twitter that has a chance of working