RunAwayFrog @ RunAwayFrog @sh.itjust.works

Posts

3

Comments

66

Joined

2 yr. ago

There is also a serious bug regarding contexts and replies BE | UI.

Not rushing to update is proving to be very wise

There is the option to upgrade with the sanitization commit reverted of course.

Holding off from updating is probably advisable at this point, at least until the effects of blanket sanitization on input are better understood. Three issues [1]|[2]|[3] have been already discovered, and there is probably more to come, as the change doesn't appear to have been well thought out.

From a technical point of view, I'd rather Lemmy didn't federate except with itself, and maybe possibly also with similar networks, but only as long as that doesn't hold Lemmy back from doing its own thing.

Getting ActivityPub federation to work reliably between Lemmy instances alone is already proving challenging for developers.

From a personal point of view, I have zero interest in what I consider a shit paradigm of social communication. The "micro" lie in micro-blogging, as you quickly conceded, is long gone. The interface is horrible for effective exchange of well-thought ideas. The social networks formed are hypernormalized echo chambers of unhinged ranting faux intellectuals and champagne activists, usually led by a cult of personality or two who are tasked with making sure the one-upping posturing game continues forever.

When you are about to "micro"blog, presumably you will be writing something coherent enough that it relates to a certain subject of interest to a section of the public. It is also presumably meant to be viewable by the public since you're not sharing it in a private group chat.

If that's the case, there should be a community in Lemmy where those interested in that subject congregate. That community would either be low-traffic, then you can make your "micro"blog a post there breathing more live into it. Or it would be a high-traffic one, in that case a lounge/chat/MegaThread post should exist where you can chat with people interested in that subject, in an interface that actually facilitates good discussion.

Sort by "best" is coming to Lemmy, in case you didn't know.

Your aggressive tone is predictably inappropriate considering your failure at applying simple logic. You would only have a partial excuse if you're 11y/o or something.

There is f-droid the app store, and f-droid.org's main repo. See, it's not that hard.

just because they have an app that allows you to add other repos doesn’t mean those other repos are a part of f-droid

And that app is called... get it?

Because those other repos are not f-droid repos

Repos made to work in the f-droid app are not f-droid repos... wow

Is the f-droid.org's archive repo not an f-droid repo, too. lol.

Please tell me you're not an adult!

The thing is, you started on the right track:

Sync is not open source and Fdroid only allows open source.

Here, you are on the right. And you could have followed up later by simply pointing out that "Will it be released to F-Droid" usually means "Will it be on f-droid.org's FOSS-only main repo", but you decided to rant some weird incoherent shit, and insisted on dying on a hell of straws instead!

I’m not sure about the impl thing, care to elaborate?

See this serde-derive code.

Basically, you're wrapping your impl in a dummy const, so your impl lives in its own lexical scope.

You can set attributes on that scope, define consts/statics, import stuff that will not interfere with anything outside the generated code...etc.

So, just add your use lines. You can allow unused imports on the scope too, no conditional imports needed to avoid warnings. You don't have to worry about anything 😉

Imagine if media in Lemmy was all hosted in a distributed network filesystem like Iroh, where instances only function as inserters and exit nodes for that media.

This way, smaller instances can have a smaller cache corresponding to the media that was actually needed by it (recently). And independent peers can help by participating in the distributed file-system network without running instances themselves.

If you don't mind a quick review:

Another thing worth noting is that it's as if the proc macro literally injects a bit of source code in-line where you call derive. This means that if you are going to refer to any structs/crates/modules etc.. it makes things a lot easier to refer to them via their full path.

I since that someone doesn't know about putting their impls in a:

    
const _: () = {
}

  

Also, using quote!{} instead of quote!() will make your indentation life easier.

anyhow instead of thiserror in your API is...

Otherwise, good, if very basic, write-up.

PS: How dare you post this to Reddit you Fediverse traitor 😉

JannieReplacer

1

Would you have escaped them a priori?

Do you consider markdown-it's typographic replacements common knowledge, and thus intuitively escapable?

Should lemmy apps be pushed to use markdown-it, in your opinion?

their live demo

I meant the markdown-it live demo.

I wrote a separate post about this.

While it may seem nice

No, it really doesn’t, its a horribly bad design choice.

I wanted to give some balance to my argument. I guess I was over-cautious with that one.

@dessalines@lemmy.ml

And btw, that's '../lemmy' in the comment above with two dots. I didn't write it wrong. The third dot comes from markdown-it (confirmed using their live demo)!!

Good, because I speak Rust, so, if there is an itch to scratch, I will scratch it, even though I'm not a UI guy.

I tried running the UI yesterday standalone and had 'error loading' message or something like that.

btw, mentioning needing '../lemmy' available in path, and needing the wasm target installed (via rustup target install wasm32-unknown-unknown) may help non-rustaceans in particular, if added to the contributing instructions.

Also, the UI was listening on *:1237, not just localhost, so maybe a WARNING regarding that is advisable, together with explaining the purpose behind leptos also listening to port 3001.

All trending communities' icons are shown. So the fix appears to be working.

Thank you.

Will there be a way to run the UI in client mode only, without being attached to a running instance?

The codec is basic, uses decades-old tech, and was trivially REed.

Lemmy instance choice does not check out ;)