Totes good!

Finnegan wins!

Vote on devRant

Vote on devRant

Vote on devRant

Screenshot taken from the livestream, 1:50:02 timestamp:

@sidtheitguy’s note: https://kbin.melroy.org/m/drbboard/p/21872/Hi-all-I-want-to-do-a-code-competition-It-s#post-comment-24463

How to post your devRant clone

It is pretty simple.

1. Add new thread page is where you can fill all needed fields.

2. Use a unique name for your application - it must not nonchalantly use the word “devRant”, as it is taken and is a trademark. Append | devRant Clone to that, and your title is ready!

3. Fill out the body with optional, but contextually interesting, information and links:

   My synopsis of what my application does that resembles devRant.
   
   - Used tech stack
   - Used data
   - It took me  hours
   - What is different
   
   ---
   
   - Demo
   - Screencast
   - Source code
   - Screenshots come in the comments below
   

4. Paste the tags: devrant drcj jam hackathon entry

5. Mark your work as OC, if all qualities specific to a devRant clone were implemented by you and you only.

6. Attach an image before submitting. It may be your main page or whatever makes the thread appealing and unique.

7. Press “Add new thread” button to publish!

8. Post additional screenshots via comments below, if any.

@melroy@kbin.melroy.org OK, it seems like the post with underlying thread of replies disappears from the Microblog tab in /m/testing when author removes their parent post, but it’s still accessible here by URL and says “deleted_by_author”. I think all is fine except “deleted_by_author” part :)))

test reply on mbin 1

test reply 2

test subreply 1

test reply 1

@joewilliams007, 4 days ago:

i will use node, as i want it to be fast (unlike python🫣 ahmm ahm). And i expect to get login going and rant posting.

deleted by creator

@joewilliams007 Mbin contributors have caught up and it seems we’re not so far away from flairs/badges support!

What about “We Fedicast”?

Pretty much same thing. I want niche creators to see that their content is appreciated (in lack of paid subscription), and Piped with a bunch of other frontends are simply not a way for this.

I think some people don’t give any room to breathe to projects that just want major contributors be paid, even when, as you rightfully say, XMPP had the same compatibility struggles in its infancy as Matrix implementations now have.

So far, there is a lot of FUD around newer protocol and that it lacks in openness. But if you look again, it recognizes versions and differences between them in the specification. Every MSC proposal covers the context of change and recommendations to implement, while keeping backwards-compatibility with older software in mind. If you make a proposal, it will be reviewed. If you need someone else besides Spec Core Team members to move it forward, flag to you - fork. But I rather prefer this model in upstream than beating around the bush and electing someone who might have lost an idea of why they are still in the project.