I see this upcoming election will be the final one. Nice work.
Oh cool, thanks. I have friends in Texas and they make it sound like it could never happen.
Snowballs chance unfortunately. I understand getting a Democrat to win in Texas is effectively impossible.
Very cute! The grooming must be a task.
How do we know this post isn't fake? Perhaps it's all part of the ruse.
Is there a problem upvoting on other instances? I've never noticed it not working.
Even more, make it more like a backup feature that's opt out not opt in. Thus, when a server goes away, the user still has their community list to import somewhere else.
Ehh, I'd like to think so. It looks like a ton of work to replace the single USB port in my center console. Most places want me to buy an entire radio kit that's like $400 just to get a new port. I've looked into it briefly, but it looks like it's financially untenable to replace what should be a $2 part if that.
Thank you so much for this effort. I've only installed the app this afternoon, but it's completely usable despite the occasional bug or instability from the upstream server's API. It's become my go-to for Lemmy on mobile, and with all this being made available for free, you have my appreciation.
This might be the wrong place for this question, but I have heard criticism that real rust programs contain lots of unsafe code. Is this true?
Sounds like they lucked out into an awesome job with no real work required.
This sounds like a bug to me. At a minimum, it should be renamed to local subscribers rather than imply that it's the total count.
This is definitely a sink-or-swim moment for Lemmy. If this is going to work, this is the chance. Twitter and Reddit are imploding. Users have a reason to try something new and are willing to deal with young, buggy platforms because it's better than the alternative and they needed an Internet home. My upvote taking ten seconds to register is itself the knife's edge of creation, a new birth.
Just not using the app is better than using the app.
So often I've pulled up my phone while it's connected just to try looking up a destination while I'm parked. Being forced to use only the car interface for Maps while plugged in has always been awkward.
Shame that my single USB port that supports Auto is wearing out! Soon I'll be reduced to Bluetooth only, and maybe a mount for the phone to keep the screen in arm's reach without having to look away from the road.
I love that a service that isn't making a buck off of us gets levels of engagement that for-profit social networks would kill for.
This is happening because:
- Novelty, because new is fun. This will go down over time.
- The most passionate users are more likely to be early adopters. More casual users are coming.
- Smaller network means your content is less likely to be covered before. This factor will go down over time.
- Fediverse encourages multiple related communities, which means your specific contributions are more likely to be seen by other users.
- Lack of bots/astroturfing leads to more positive interactions. Bots will likely increase over time.
Therefore, I expect engagement will go down over time, but I am hopeful it will reach a higher point of stability because the fediverse design seems better at getting more varied content seen by its users, and it makes it harder for a small group of people or posts to dominate the discussion space.
PS: Anybody know how to add a space after the last bullet in a list?
I swear there's at least one of these ladies in every restaurant I've attended in recent memory. Now I'm going to be imagining what their salad just told them.
QED, I think this response completely addresses my concerns. I often miss the social aspect of systems that involve people. I can't think of any further questions.
I reverse native binaries across a few different platforms for a living, but I'm just getting into Android. I will definitely take a look at those systems!
I have a love/hate relationship with desktop web apps on Linux. They are a great blessing in some ways because I get to run apps that just wouldn't be available to me otherwise because Linux typically isn't a priority for consumer-focused services. Often support exists as a convenient bonus because it came with the web app platform choice.
On the other hand, you get a web app, which looks nice (hopefully) but gobbles down your resources.
Underrated comment. I picked it because I had no idea what I was doing and it sounded all-encompassing and I wanted access to everything. I didn't even know what an instance was. I just picked it because it sounded like a good guess to get access to all of Lemmy.
More concretely, I'm asking this: why aren't applications compiled fully to native code before distribution rather than bytecode that runs on some virtual machine or runtime environment?
Implementation details aside, fundamentally, an Android application consists of bytecode, static resources, etc. In the Java world, I understand that the main appeal of having the JVM is to allow for enhanced portability and maybe also improved security. I know Android uses ART, but it remains that the applications are composed of processor-independent bytecode that leads to all this complex design to convert it into runnable code in some efficient manner. See: ART optimizing profiles, JIT compilation, JIT/AOT Hybrid Compilation... that's a lot of work to support this complex design.
Android only officially supports arm64 currently, so why the extra complexity? Is this a vestigial remnant of the past? If so, with the move up in minimum supported versions, I should think Android should be transitioning to a binary distribution model at a natural point where compatibility is breaking. What benefit is being realized from all this runtime complexity?
Complete list of secondary accounts across Lemmy, claimed here to all be the same human:
henfredemars@lemdro.id henfredemars@infosec.pub henfredemars@hexbear.net