No bio yet.
Lots of UI improvements and addressing API spam issues/errors reported by in this release. Next let's aim to get the test version on the playstore!
Big release for the flutter app. Writes are now native! Frontend post filters, account details, etc. Eager to hear what you guys think to iron out inevitable quirks.
The big thing is to gather enough test users, and establish an audience within the required metrics for Google to allow us to publish it even as a fully free app. But In the coming days I'll at least get it to the alpha stage, send out test invites so that its more official.
Do you think it's easy to publish it to the App Store? I've never done mobile dev.
Big! I'll keep the community posted on the improvements as they come
It's live! Have fun with your client :) thanks!
likewise. Its just nice to have an "even playing field" without any perceived hierarchy or weird material incentives to perform the way you'd be pushed to on regular SM.
I stopped interacting much with social media years ago and am honestly not sure how to do this any more… but I like the shape of what is starting here.
Good morning! Just in time for coffee and unpaid work!
mornin' i can't believe i slept like 15 hours.
Basically I'm describing early days Twitter, which this platform embodies quite well imo
One idea off the top of my head is to just.. keep it "boring" and casual in terms of content. The silly, whimsy, and genuine stuff naturally doesn't appeal to money-chasing slop bros and makes it not worth their time.
One idea off the top of my head is to just.. keep it "boring" and casual in terms of content. The silly, whimsy, and genuine stuff naturally doesn't appeal to money-chasing slop bros and makes it not worth their time.
any ideas on how to prevent ai-generated stuff on this platform?
This is certainly one of the ways
Made barbecue this evening. Lamb and chicken for meat, pepper and zucchini for veggies. Yummy! Kids loved it, the boy's sleeping now, the girl is reading a book, the wife's out with her girls, I'm with wine. Life's good.
Big list of events you've attended! Definitely dump more photos when you find the time. I'm more of a casual Nu-Metal enjoyer myself, but I can also appreciate some of the classics.
Sharing a link to my music blog: https://crusty-metallian.net Not a lot of content yet, it's a work in progress :)
Wow! thank you for even considering that!
I took the liberty and added a big fat "get mobile app" button for agents at the footer on the web app pointing to your repo! Hope it's fine with you. Tysm!
Ty for the quick fix 🙂
I think it fixed by my change, the current client no longer does it and I don't see any reconnection on the server.
Ty for the informal beta testing hahaha I've found that the connection drops from the server's heartbeat are treated as errors by my client. Pushing a fix in 0.0.6 to reconnect quick and reconcile missed msgs.
Another thing I'm noticing is the firehose endpoint is reconnecting every few seconds instead of being kept alive. Is this a limitation of some sort of the EventSource client you're using? Because it might omit some messages, the reconnection doesn't do any replay.
I agree with this. The core you're building is around a deliberate minimalist philosophy. I was happy to build an opinionated client for my own use-case, but it should imo stay on the fringes for those seeking it.
I've tested MD and honestly I don't like it. Bold/italics add unnecessary noise/clutter and the font is already monospace, suited for code, so inline code & code fences are not needed. If 3rd party clients want to implement them it's fine but I'm sensitive to visual noise.
v0.0.5 now has session caching for replies and threads. Should be a lot more conservative on hitting those endpoints.
hey I see a lot of spamming on the
/posts/NNN/repliesendpoints in the logs, are these intentional? They might cause rate-limiting.
I added a section for building it from source for iOS , but I know its a tall ask. There is no other "free and open" solution available to me ATM. In the future, if an Apple licensed dev could do us the favor, by all means!
Hmm, as an iPhone user here, do you have plans to support iOS? Last Android based phone I owned was the HTC Hero.
Ah, woops! I will take a look at agressive caching for nested threads. I think I overlooked that part while implementing replies. Good catch!
hey I see a lot of spamming on the
/posts/NNN/repliesendpoints in the logs, are these intentional? They might cause rate-limiting.
Yes, exactly! I really like how mature and robust it feels to work with, especially since I don't necessarily want to deal with too much platform-specific headaches (last iPhone I owned was the 4S on release).
That would make sense, I agree. Did you pick Flutter because it is easier to develop cross platform?
Maybe frontend clients can be left to implement more of these nice-to-haves to cater to specific audiences. That's also why I started building a flutter client for .
Maybe implementing a subset of Markdown would be a good thing. I am thinking about bold, italics, inline code, and code block, mostly. Oh, and links.
I pushed a small fix for the reply behavior, now it should just use your cached browser info to make writing easy.
Hey this looks cool! I wasn't able to "write" because the email link wouldn't see the app, but probably that isn't implemented yet as well since we don't have API POST endpoints? Other than that it looks promising! Thank you for this!
Thanks! Yeah indeed, for now its very much Read-only. Maybe I'll tinker around and make a PR for POST endpoints, but as it stands I think there's enough to still improve on the UX for listing, themeing, etc to keep me busy as feedback hopefully rolls in.
Hey this looks cool! I wasn't able to "write" because the email link wouldn't see the app, but probably that isn't implemented yet as well since we don't have API POST endpoints? Other than that it looks promising! Thank you for this!