henfredemars

@henfredemars@lemmy.world

List of secondary accounts:

henfredemars@lemdro.id

henfredemars@infosec.pub

This profile is from a federated server and may be incomplete. Browse more on the original instance.

henfredemars,

Snowballs chance unfortunately. I understand getting a Democrat to win in Texas is effectively impossible.

henfredemars,

Oh cool, thanks. I have friends in Texas and they make it sound like it could never happen.

henfredemars,

How do we know this post isn’t fake? Perhaps it’s all part of the ruse.

henfredemars,

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.

henfredemars,

Is there a problem upvoting on other instances? I’ve never noticed it not working.

henfredemars,

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?

henfredemars,

As someone who has lived in the plains all his life, the idea of hills being a real thing that actually exists outside of movies seems strange.

Absolutely magical!

henfredemars,

It is annoying, but at least it makes sense considering the few orders of magnitude growth they’ve experienced in two days and given that we are not the customer nor the product. Nobody is making money from this. Instead, we are benefiting from the generosity of those who host the service, much like Wikipedia.

henfredemars,

I think that the problem you describe is self-limiting because users can easily make accounts to get around an instance that limits the content users can view or just add an account for a more permissive instance. However, consider the following: humans tend to fixate on loss, and users aren’t tied down to using any particular instance or even just one, so they don’t have to compromise. You don’t lose anything by adding another account on another instance to your client. There are already clients that let you pull from multiple instances automatically.

Defederation that hurts users, by the judgment of those users, on a platform where it’s easy for your users to just join any other competing instances on a whim, tends to select against instances that defederate excessively. That is my hope.

henfredemars,

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.

henfredemars,

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.

henfredemars,

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.

henfredemars,

Hello, and thank you for taking the time to compose this response.

I think that I may have conflated the choice of language with the choice of distribution. I believe the choice of language is independent of the choice to distribute apps as native or not, for at least Java because Java has solutions for AOT compilation not the least of which was actually used before in Android 5 according to another response, and it was used prior to Android 7 according to this resource.

For the sake of discussion, I propose that this existing AOT compiler for Android Java applications (used today in the hybrid solution) be run in its entirety on a server instead of on the user devices. I don’t see a motivating reason to have the compiler on every user device to include a complex profile-guided optimization framework and hybrid JIT compiler (described in my third link in the original post) when we could ship the finished code and be done with it.

The benefit would be lower maintenance of the Android platform through a simpler design. (This benefit might shake out, but I get to that later.)

The migration process would consist of doing nothing for the typical app developer making this change quite cheap. The same languages would be supported as they are now. Indeed, this transition has already happened before and shows that this approach works, except with the build process happening on the device in earlier Android versions. I don’t understand why Google did not go a step further and ship the binaries, instead choosing to take a step back and ship a JIT compiler with the AOT compiler. Why ship the intermediate bytecode representation and insist on a complex on-device build and optimization runtime?

From the responses that I have received so far, I think the true answer as to why distribution isn’t native is likely composed of a combination of the following factors:

  • Android’s heritage and if it ain’t broke, don’t fix it mindset (very respectable IMHO).
  • Android practically supports more platforms than arm64 even if not officially stated, such as Chromebooks and some x86 tablets. Shipping native would make this cross-arch support a lot more complicated.
  • Loose coupling between hardware and software platforms as a good design decision.
  • JIT performance can actually exceed AOT because more information is available at runtime.
  • Backwards compatibility is very important to Android, and the impacts of not shipping bytecode to these old versions could be profound or practically impossible depending on how far back we wish to consider.

I’m sure that I’m making further assumptions, and surely there are oddball apps out there that really depend on having dynamic optimization to be performant, but I suspect these apps are in the minority. At a glance, the current solution seems too complicated, but I think understanding the history of the platform and the selection of devices that are supported today mostly answers my original question. Briefly, arm64 is absolutely not the end of the story even if it’s listed as the supported CPU architecture, and officially committing to just one now and forever could come home to roost.

henfredemars,

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!

henfredemars,

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.

henfredemars,

It’s been said to death but at heart, I’ve always felt that when it comes to piracy, it’s a service issue, not a cost issue.

Except for you Adobe. That’s a cost issue.

Do you feel that there's a lack of discussion on Lemmy on stuff besides the current Reddit and Twitter controversies?

I’ve been on Beehaw and Lemmy.world for the past two weeks now and while people seem to be posting content that isn’t about Reddit or Twitter or how great federated platforms are, such content does not receive as many comments/discussion as topics about the Reddit API controversy, or the current Twitter controversy, etc....

henfredemars,

Somewhat, but it’s just the “how’s the weather?” of this community because most everyone is here from Reddit, so it’s a starting point to me. I don’t think Lemmy exists just to spite Reddit, and I participate in discussions having nothing to do with the subject.

henfredemars,

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.

henfredemars,

We do have privacy laws today (USA user), but they are so weak that near my office I regularly see ads advising businesses to treat it as a liability problem and instead buy insurance as a faster and cheaper alternative to good practices.

And it works! This approach should not be feasible to address the costs of violating user privacy. It reiterates to me that we are far too lax.

henfredemars,

This is hilarious. On my Desktop, which is quickly becoming my preferred interface for the moment, I just keep opening new tabs and letting it work when I post so I can move on with reading other content.

I ain’t even mad. You’ve got a good heart, soldier.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • InstantRegret
  • magazineikmin
  • thenastyranch
  • modclub
  • everett
  • rosin
  • Youngstown
  • slotface
  • ethstaker
  • mdbf
  • kavyap
  • osvaldo12
  • DreamBathrooms
  • anitta
  • Durango
  • ngwrru68w68
  • tester
  • khanakhh
  • love
  • tacticalgear
  • cubers
  • GTA5RPClips
  • Leos
  • normalnudes
  • provamag3
  • cisconetworking
  • JUstTest
  • All magazines