ShittyKopper [they/them]

  • 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle



  • Lemmy’s cross posts are separate posts that just happen to link to the same thing. so only replies to the original post would be sent with the current design.

    that said, i severely doubt Lemmy will gain anything from this. publishers will not be sending out their posts to any communities, and i highly doubt they will expose any fep-1b12 group actors you can subscribe as a community.

    kbin/mbin with it’s ability to follow users may work better, assuming people test their federation with software other than mastodon, and accept any of the interoperability bugs as actual bugs instead of ignoring them. (lemmy itself is no stranger to this: the fact that users and communities can share the same username break quite a bit)




  • (talking about microblog fedi here, Lemmy/threadiverse is it’s own thing)

    don’t do hashtags. hashtags (especially common ones like #memes) are overrun by repost bots and low quality garbage.

    the trick is to be on a small-to-medium instance you vibe with (1k active users seems to be the sweet spot. anything larger than 2k I’d avoid. do NOT join any flagship instances like mastodon.social), follow fun people from your local timeline, and see who they boost. and follow up the boost chain until your timeline is sufficiently fun.



  • I’m not entirely sure if such an instance exists, but just letting you know that in case you can’t find any, a reasonable compromise would be to join an instance that’s enforcing authorized fetch (and is blocking threads)

    this will make it harder for facebook to read your data through federation alone (i.e. even if a post of yours get boosted by someone with followers from threads, it won’t “leak” there)

    there are ways to bypass this of course but if facebook is found to do something of that sort they would out themselves as actively malicious which would definitely get a reaction even from the “wait and see” crew






  • TLDR of linked gist: wayland is not X therefore it is bad. end of.

    Wayland breaks Xclip: As you said it yourself, Xclip is an X11 application, so it doesn’t work on Wayland. Of course it wouldn’t work on Wayland. With Wayland, we’re trying to prevent what happened with Xorg from happening again, or am I wrong?

    also, https://github.com/bugaevc/wl-clipboard. perhaps all OP (of gist) needs is a simple shim that can convert calls to xclip to wl-copy/paste? that doesn’t seem too hard to make compared to keeping X.org alive I’d say (perhaps they should try making it if it’s that much of a problem)

    Wayland breaks screensavers: Yeah, that seems to be the case.

    from the dev of xscreensaver at https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/ :

    […] Adding screen savers to Wayland is not simply a matter of “port the XScreenSaver daemon”, because under the Wayland model, screen blanking and locking should not be a third-party user-space app; much of the logic must be embedded into the display manager itself. This is a good thing! It is a better model than what we have under X11. […]

    […] Under X11, you run XScreenSaver, which is a user-space program that tries really hard to keep the screen locked and never crash. It is very good at this, but that it needs to try so hard in the first place is a fundamental design flaw of X11. […]

    other people can comment on the parts they know about, these are two i know of off the top of my head



  • In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.

    Oh - this sounds interesting.

    Whenever I needed to jot down any notes I’ve been finding myself just writing plain .txt files with bullet points, and trying tools like Obsidian or TiddlyWiki I always ended up being overwhelmed with the amount of stuff I could do (and with all the customization options) that I never got around to actually writing things down. I’m definitely gonna look into how Logseq works.

    (Although I have to say, their website does look a bit “too hype-y” for my liking. IDK how to explain it, just a gut feeling. Still, at least it’s FOSS so it can’t be too bad)





  • Another thing I would like to suggest is a change in recruitment strategy. At this point it seems like we are unlikely to pull a significant amount of users from Reddit without more reddit-policy-driven migration, but there are tons of highly educated and engaged users over on Mastodon that would make serious positive contributions to the tone and quality of the discourse over here. For some reason there seems to be minimal overlap between the two communities and that blows my mind. Not only that but I actively see folks disparaging Mastodon in fediverse related communities on a regular basis (and even sometimes in the Mastodon communities themselves). As far as I can tell, these are largely lingering sentiments from a Reddit/Twitter dichotomy. Remember, as things develop the lines between threaded social media and microblogging are likely to blur. A significant number of Mastodon apps already provide a threaded view and one of kbins explicit goals is very much to bridge the gap. With this in mind, Mastodon (and federated microblogging more generally) seems like the best source for new potential users.

    A thing to look out for is that the microblog fedi (outside the big handful of instances that fill .world’s role there) is strongly in favor of stricter instance-level moderation compared to the more “individualistic” view a lot of the Reddit migratees tend to have. If we want people from the microblog fedi to participate we (collectively) need to up our moderation game. (And in my personal opinion instances like .world have grown too large to accomodate any reasonable expectation of moderation, except for select individual communities set up there)