ShittyKopper
@ShittyKopper@lemmy.blahaj.zone
"reddit refugee" i guess? i mean -- i was on masto under a few different aliases over time as well so i'm not a stranger to fedi, it's just that i'm boring and that's my only personality trait on here
they/them
- Comment on Hel lo tim 4 weeks ago:
epic megapost Image
- Comment on 2 months ago:
it’s called microblogging
- Comment on 3 months ago:
how many times did you edit that post per chance? Lemmy seems to boost edited posts for some odd reason
- Comment on Leaving the bidet on "feminine" mode is the female equivalent of leaving the toilet seat up. 4 months ago:
alternatively: why are you linking to an image at all and not just making a text post
- Comment on How I cannot be worry?? 4 months ago:
I wish I was in the us lol
- Comment on How I cannot be worry?? 4 months ago:
sure let me just walk to a better country
hey wait why are there people with guns around me
- Comment on Fediverse link-aggregator PieFed launches in beta test 4 months ago:
FYI misskey does not implement the masto api. some software like pleroma/akkoma, gotosocial and yes, a few misskey forks do (in various states of brokenness, with iceshrimp being the most compliant one) but misskey itself does not.
- Comment on Lemmy MAUs climbing back up! You love to see it. 4 months ago:
I think fedibird is a hard fork, so I guess it makes sense to count it separately compared to a soft fork like glitch or chuckya
I’m more surprised why there aren’t any misskey instances on the list. if fedibird is on there misskey should certainly be there
- Comment on If we're going to have an effective strategy against FB/Meta, we should clear up some misconceptions around defederation 4 months ago:
you can disable the webpage and unauthorized API if you so choose. mastodon and pleroma/akkoma provide these settings. gotosocial hides all unlisted posts from public pages.
authorized fetch only provides protection for activitypub, it’s just a single component of a layered stack of protection you can enable depending on your exact threat model.
the privacy threat model of Lemmy is significantly different from a microblog, which is the current target of threads.
(also have none of you heard of consent?)
- Comment on If we're going to have an effective strategy against FB/Meta, we should clear up some misconceptions around defederation 4 months ago:
no, not really.
i have attempted to build my own federated stuff (none of them actually federated “in real life” though) so i did read the specs but quite a lot of these are from my memory and if there’s anything i know is that my memory fuckin sucks lol
- Comment on If we're going to have an effective strategy against FB/Meta, we should clear up some misconceptions around defederation 4 months ago:
Which could still be millions?
sharedInbox handles this.
mastodon.social sends a single federation activity to www.threads.net’s sharedInbox. threads’s internal systems handle all the visibility and routing to followed users and whatnot. the same thing happens in the opposite direction for threads->mastodon (or whoever).
now in theory this is an optional part of the specification and you can in fact send one activity per person if you really want to, but considering how widespread it is you’d have to be intentionally and explicitly malicious to not use a sharedInbox if the remote server indicates it supports it.
- Comment on If we're going to have an effective strategy against FB/Meta, we should clear up some misconceptions around defederation 4 months ago:
just want to clarify something:
However, the way that activitypub works, the outgoing data is publicly available. Defederating with Meta doesn’t prevent that,
there is a technical solution to this in the form of authorized fetch: hub.sunny.garden/…/what-does-authorized_fetch-act…
mastodon implements it, pleroma/akkoma probably implements it, pixelfed implements it, firefish and iceshrimp implement it (sharkey has a PR implementing it opened just today), gotosocial not only implements it but enforces it, with no ability to turn it off
notably, none of the threadiverse software implement it, and no software other than the aforementioned gotosocial enable it by default.
- Comment on 41% of fediverse instances have blocked threads so far!!! 4 months ago:
if you were to focus this on just Lemmy itself as opposed to the wider fedi (“Especially given that there was just an update allowing for individuals to block instances they don’t like” implies that’s the case) you already have nothing to worry about as you encountering a threads user here will be even slimmer than encountering a mastodon user.
threads is primarily targeting the microblog/personal side of fedi. the incentives and privacy expectations are quite different compared to this side of fedi
- Comment on 41% of fediverse instances have blocked threads so far!!! 4 months ago:
re active users: they’re a large open registration instance, they likely have a fair chunk of twitter people who joined during one of the many migrations and decided not to stick around.
- Comment on Integrating f-droid to lemmy 5 months ago:
there was a fdroid client that did something similar using mastodon and hashtags but I can’t remember which one it was and if it’s still doing that
- Comment on Manager: This task only takes 30 minutes. Why did it take you the whole day? 5 months ago:
git commit -m $(date)
- Comment on @PostWatchBot - notify new comments on a post 5 months ago:
I didn’t tested non-followed community, but the bot works with mention event instead of comment. But still not sure, I’ll test this one 🙏
oh, I meant for the actual post watching part, summoning via mention should work without any subscription
- Comment on @PostWatchBot - notify new comments on a post 5 months ago:
in theory as you operate both the server and the bot you could modify lemmy to tell the bot when a new comment hits a thread instead of polling, which would be more efficient (but definitely harder to do!)
also does it handle the case where nobody from your instance is following a community? to make sure you get all the replies reliably the bot would need to subscribe to each community it’s watching a post from
that said, great work. I may end up using it if I don’t end up forgetting about its existence :p
- Comment on What is enterprise.lemmy.ml? 5 months ago:
.world is a newer gTLD whereas .ml is a more well known country code TLD. whatever auto linking code the lemmy UI uses likely just isn’t up to date with all these comparatively recent TLDs
- Comment on Pleroma vs Mastodon vs Misskey 5 months ago:
fedidb.org/software/iceshrimp is a thing, and there are several general purpose instances such as fedia.social and iceshrimp.social (which isn’t anything official despite the name)
not having an (open) flagship is, to the best of my knowledge, an intentional choice as moderating it would take time away from development
- Comment on Pleroma vs Mastodon vs Misskey 5 months ago:
I personally find the development to be more “sensible”. firefish bungled up their flagship with a (imo) failed transition to scylladb and hasn’t been doing much of importance since then (they changed the boost icon to s rocket though!)
compared to that, iceshrimp rewrote their mastodon api compatibility layer to the point where it may be the most compliant one among misskey forks, uncovered several perf bottlenecks (one really big one related to word mutes since fedia migrated over), fixed the http signature security vuln ahead of firefish (and provided the patch to them, which they didn’t put in a stable release for something like two days even after merging)
quite a lot of firefish instances seem to be migrating over to sharkey for similar performance and stability reasons, but if you like the firefish UI/UX compared to the “classic” misskey one (or want a smoother migration path from firefish that doesn’t involve a major version bump) then iceshrimp is the one to check out imo
- Comment on Pleroma vs Mastodon vs Misskey 5 months ago:
one of the misskey forks. imo “vanilla” misskey is lacking a fair bit of essential stuff (post editing being a giant one)
the most interesting ones to watch for now are iceshrimp (misskey v12 hardfork based on an early version of firefish, mainly focused on backend tech work compared to new features) and sharkey (misskey ”v13” softfork, aimed at qol changes and other feature work while keeping up to date with misskey itself)
akkoma is alright if you need something light on resources but I personally can’t get used to it’s interface)
and mastodon is just… too bland in comparison to both
- Comment on Chrome’s next weapon in the War on Ad Blockers: Slower extension updates 5 months ago:
They aren’t forced to do anything. Manifest v3 is just a part of the WebExtensions API (which is not a standard and is really just “whatever Chrome does except we ctrl+f’d the word chrome to browser”) which both Safari and Firefox chose to implement in order to make porting of Chrome extensions easier.
Before that, Firefox had a much more powerful extension system that allowed extensions quite a lot of access to browser internals, but that turned out to be a maintenance nightmare so they walled those APIs off (not a coincidence that Firefox started getting massive performance improvements after that, and extensions stopped breaking every other release) and decided to go the WebExtensions route. I have no clue what Safari was up to but I think they implemented it after.
If they don’t implement Manifest v3, extensions that want to work across multiple browsers need to support both the older Manifest v2 and the later Manifest v3, which would be a burden not many extension authors would want to bother with, which would make them just say “yeah we’re not supporting anything outside Chrome”. Firefox avoids this problem by extending the v3 API to allow for the functionality necessary for powerful ad blocking Google removed in v3 (webRequestBlocking) while also implementing the new thing (declarativeNetRequest), so extensions that want to take advantage of the powerful features can do so, while Chrome extensions that are fine with the less powerful alternative can still be ported over relatively easily.
- Comment on Why do a lot of fediverse instances put their software (i.e. Lemmy/Mastodon) in their name somehow? 5 months ago:
ActivityPub does not govern how user handles work. All AP actors are defined by their IDs (which in Lemmy’s case happens to be the URL their profile is hosted in)
AFAIK the @username@instance convention is Webfinger’s doing, and (to the best of my very incomplete knowledge) the convention of “preferredUsername @ the hostname of the object ID” is a hack Mastodon pulled that got adopted as a de-facto standard (as is quite a lot of other things in AP).
- Comment on Why do a lot of fediverse instances put their software (i.e. Lemmy/Mastodon) in their name somehow? 5 months ago:
You also can’t reuse a domain between software installations (some exceptions apply when migrating between software of the same “family tree”, e.g. migrating from a mastodon instance to glitch, or migrating between misskey forks) due to how federation works. Hell, reinstalling the same exact software can break federation if you wiped your database in the meanwhile.
Some software offer a “split domain” approach where the software itself is installed in a subdomain like mastodon.example.com but with user handles on a separate domain (usually the root domain, like @example.com) but I am not too sure on the reusability of that, and it’s not an easy thing to implement (Lemmy won’t deal with that correctly and will always use the full domain for anyone on a split domain instance).
- Comment on I’d like to hel, do any fediverse apps use node on their backend? 5 months ago:
activitypub isn’t something you can abstract into a library in a clean way in my experience. the best attempt here seems to be go-fed. most projects i know of implement it in their own way, specialized to the kind of platform they’re planning to build.
- Comment on I’d like to hel, do any fediverse apps use node on their backend? 5 months ago:
misskey and it’s forks (firefish, iceshrimp, sharkey, and the approx. million others) use a node/ts backend with a vue/ts frontend. peertube also uses node to the best of my knowledge.
- Comment on Introducing the Lemmy Tagginator 5 months ago:
i can see why you may not want this but have you potentially considered rehosting/attaching any images from image posts in the bot’s replies? as lemmy doesn’t federate those properly just yet (github.com/LemmyNet/lemmy/pull/4035 will fix it AFAIK) it’d make the bot quite a lot more useful and things like memes do tend to get boosted a lot more widely than links, though i can definitely see why it may feel a bit like freebooting (so, it could perhaps be a per-community option for non-OC-heavy communities?)
- Comment on Introducing the Lemmy Tagginator 5 months ago:
interesting idea
one thing I like from kbin is that because it does this natively I can follow a kbin magazine from an empty unused account and create a misskey antenna pointed at the hashtags in question (with replies hidden) which allows me to subscribe to kbin communities without getting spammed with boosts of replies, so I may end up making use of this depending on how widely it gets adopted
that said I’m still not convinced that increasing lemmys reach outside the threadiverse makes sense just yet while its federation is so buggy, case in point: brain.d.on-t.work/notes/9md8phwlkzlj0xe9 (edits on posts are repeatedly re-boosted, which likely wasn’t noticed as mastodon only ever allows one boost from an actor)
- Comment on how do you even use twitter? 5 months ago:
i tried but i can’t lookup your comment because your instance is returning html instead of activitypub data
