Add new thread page is where you can fill all needed fields.
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!
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
Paste the tags: devrant drcj jam hackathon entry
Mark your work as OC, if all qualities specific to a devRant clone were implemented by you and you only.
Attach an image before submitting. It may be your main page or whatever makes the thread appealing and unique.
Press "Add new thread" button to publish!
Post additional screenshots via comments below, if any.
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.
After some work by contributors of #Mbin to introduce an indication of magazine in the top bar, I'm happy to say that it's more clear now WHERE on the site you happen to be. Happily, my little CSS trick has adapted to it quickly, but I made #dRBB icon smaller to prevent it stealing space.
Again, thanks to the Mbin contributors! There is a lot of work done already, and I feel confident with this fork of #Kbin to improve one of the store fronts of Fediverse.
This is terrible news. :( Sorry to hear that work makes you download from proprietary store front. I suppose, expecting phones with LineageOS, CalyxOS, GrapheneOS, etc given for work purposes is a bit much at this moment, but at least side-loading should be provided if we're to avoid monopoly. To me, it's never healthy if organization is fixated on using only the single app kit for everything.
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.
Add new thread page is where you can fill all needed fields.
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 Cloneto that, and your title is ready!Fill out the body with optional, but contextually interesting, information and links:
Paste the tags:
devrant drcj jam hackathon entryMark your work as OC, if all qualities specific to a devRant clone were implemented by you and you only.
Attach an image before submitting. It may be your main page or whatever makes the thread appealing and unique.
Press "Add new thread" button to publish!
Post additional screenshots via comments below, if any.
@joewilliams007, 4 days ago:
More like "rants the web" 😏
@joewilliams007 Mbin contributors have caught up and it seems we're not so far away from flairs/badges support!
What about "We Fedicast"?
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.
After some work by contributors of #Mbin to introduce an indication of magazine in the top bar, I'm happy to say that it's more clear now WHERE on the site you happen to be. Happily, my little CSS trick has adapted to it quickly, but I made #dRBB icon smaller to prevent it stealing space.
Again, thanks to the Mbin contributors! There is a lot of work done already, and I feel confident with this fork of #Kbin to improve one of the store fronts of Fediverse.
This is terrible news. :( Sorry to hear that work makes you download from proprietary store front. I suppose, expecting phones with LineageOS, CalyxOS, GrapheneOS, etc given for work purposes is a bit much at this moment, but at least side-loading should be provided if we're to avoid monopoly. To me, it's never healthy if organization is fixated on using only the single app kit for everything.
What you guys call "swipe typing" is actually a glide typing, right?
Sadly, not yet. (Also missing this feature.)