Dang, I’m not even sure if I implemented the cake symbol in my Lemmy client
Dang, I’m not even sure if I implemented the cake symbol in my Lemmy client
Clients can work around it by making a search on the home instance that filters by community id and submitter id. Something like this.
You can’t have content addressing because it’s mutable. On the other hand, UUIDs are made for that. There’s even multiple types of UUIDs made for distributed computing with namespaces and such.
Amazing. One feature that is desperately needed on Lemmy is to open a post in another instance, not just a community or a user.
Well, that reminds me that Mastodon has huge, unresolved problems, such as tags being part of the post’s body like Twitter rather than being a separate field like Tumblr.
Reading tweets with a hundred hashtags at the bottom seem really thirsty for attention, which is bad because Mastodon wants to fundamentally work with these, yet doesn’t have good in-post integration for them. It makes interactions less genuine, more performative.
Rome wasn’t built in a day, and Mastodon won’t be good tomorrow either. In the meantime, you can vote to make it better on https://github.com/mastodon/mastodon/issues/10743.
Cats are all the rage on Lemmy at the moment
Tumblr is a blogging experience that’s similar to Twitter, but more focused on the user itself than on the central feed.
It’s still like that with programming languages like Go and Rust. Job offers are exclusively for senior staff engineers with 5 years of language-specific experience.
Yep. And clients would be able to participate to the seeding.
Servers software developers would still have a massive amount of work to do to implement IPFS integration, but it’s doable. IPFS also has work to do here to make IPFS work natively with cloud storage protocols (like Amazon S3), but it already exists.
One issue with open source software is that you often have to pick the least-effort solution to avoid burning out your free labour. Free time is limited, and if IPFS takes slightly too much work to add, then it’s off the table.
That only-one-ignore-without-premium thing is really asshole design, though
It’s already happening on Pixiv…
You don’t need to be at the mercy of Google to keep your phone updated!
The whole point of having a Google phone is that you can easily flash it after its planned obsolescence date.
I don’t think there’s a “better” option, but Graphene’s maintainer throwing tantrums at people who criticize him doesn’t inspire confidence
Android 14 Beta 5
I prefer my own app, but that’s a given :P
I did like many aspects of the official Reddit app until they enshittified it, so I’m reusing some concepts it had. It’s still in alpha phase, and even then, there’s some things I liked that I’m not sure I’ll implement. I particularly liked the second tab in the bottom navigation bar when it had your list of subscribed subreddits and an alphabetical scrollbar. That was super awesome. I’ll definitely try to add something like that in the future, probably after I get feature parity with the official UI.
I’m avoiding pop-ups by editing the current relevant components. So, when you press “submit”, the error message will be inside the form instead of as a pop-up. Or when you report a post, the form appears inside the post instead of as a pop-up. It’s much more intuitive to use and I think I can make it faster to use.
And have you seen the prices of Jerboa, Connect, Liftoff and Thunder?
Technically, they could publish a ReVanced patch…
I also paid with my Google Opinion Rewards even though I didn’t use it, but this price is literally double what I’ve gained in a year. A bit greedy, innit?
“An ex-Netflix engineer’s take on piracy; in a YouTube drama near you”