…and I thought of a web game you can make with this, if anyone’s bored and looking for something to do: https://brain.d.on-t.work/notes/9on0iba4evg40hic
- pick a random page
- find all pages nearby
- make the player guess the random page from the nearby pages
- if they haven’t guessed the exact page, compare the coordinates and score based on distance to the correct page
I have just been informed you can also see pages nearby other pages with a special URL query (apparently no interface exists for this yet)
yeah same here unfortunately. but then I am currently somewhere I’d consider middle of nowhere
actually there was one plane crash but that’s not necessarily an article I’m interested in
alternatively: why are you linking to an image at all and not just making a text post
it used to have it hardcoded in software but I believe they made it an instance option a bit before the reddit exodus
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
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.
so, are you paying for it?
git commit -m $(date)
I’m mildly worried I know (as in, am aware of their existence, thankfully not having interacted with them) who you’re talking about
well I just checked and while “sync contacts” did not turn itself on, “allow contacts to add me” did. there’s definitely something going on
.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
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 find/replace’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) side by side, so extensions that want to take advantage of the powerful features on Firefox can do so, while Chrome extensions that are fine with the less powerful alternative can still be ported over relatively easily.
Firefox does have it’s fair share of extensions on top of the WebExtension API already (sidebar support for one), so adding one more isn’t too big of a deal.
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
i tried but i can’t lookup your comment because your instance is returning html instead of activitypub data
also remember just like how lemmy has it’s kbin, mastodon has it’s interoperable alternatives.
i bet a fair bit of the complaints i hear from people on lemmy (low character count, wanting to follow topics instead of people) would be solved by trying out a misskey fork such as firefish, iceshrimp or sharkey.
i don’t think there’s any instance out there with a char count lower than 1000, and antennas are really good (why limit youself to following a single hashtag when you can follow any number of arbitrary keywords?) if you’re in a well federated instance (provided you’re ok with them not feeding into your home feed and them not being retroactive (so after you set up an antenna you’ll need to wait for new posts to filter in))
they aren’t as polished as mastodon since mastodon kinda ate everyone’s lunch in terms of developer attention (and upstream misskey is an almost one-man-show mess developed entirely in japanese which is why everyone prefers to fork instead of collaborating), but they’ve been getting really good.
just avoid flagship instances (> 1k active users) for the time being. scaling is still something not many of them have solved just yet
i was half considering boosting it outside lemmy out of context tbf
the rule of thumb here is that you should really just use one browser ad blocker. having multiple will conflict especially regarding anti-adblocker prevention (as uBO will try to hide itself and redirect to a “defused” version of an ad script and whatever other ad blocker you have will think that’s an ad and block it)
not entirely sure how well DNS ad blockers fit into this. there is a chance they could make your ad blocking detectable by blocking a request uBO intentionally lets through (possibly in a modified state), but as far as i’m aware there haven’t been too many issues stemming from combining DNS blockers with uBO and the likes.
.world is unique in that because of its size it has kinda ended up being “Lemmy” to most people. I very much doubt the people posting porn on .world care about instances and federation and just treat .world as a centralized site