@BeAware@social.beaware.live@darth@silversword.online@nilesh@fosstodon.org Part of making standards and stuff like that is making sure that whatever you end up doing doesn't break preexisting expectations and code. That is why a bunch of standards are so messy - they can't disrupt existing behaviour, only add on to it.
The profile:username tag is complicated in this regard because (1) you can't guarantee that you won't break any existing expectations & code, as well as (2) it's very ambiguous.
Every other OpenGraph tag has a clear usecase. The username tag on the other hand does not. If you are making something that uses it how can you tell what platform that username is meant to point to? Is it Facebook (most likely the idea when making it)? Twitter? Reddit? The same random blog/news site it comes from?
And your idea about formatting - how can you guarantee that the username is a fediverse username and not, for example, a defederated chat apps username (or even a fediverse clone that doesn't interoperate with the fediverse!)). You just can't, all you can do is guess.
Making a whole new tag with a very clear usecase is a much better solution than taking over a very ambiguous tag which may or may not break preexisting expectations and code.
First of all we need to understand that OpenGraph isn't an open W3C standard. It was made by Facebook so URLs posted on Facebook can look prettier and have more info. It later went on to just become the de facto standard as, well, why reinvent the wheel.
Now with that explained, let's look at the actual tags. There is a profile:username tag in the OpenGraph docs, but it isn't used... at all... and it's uncertain why it exists, if there is already an expectation on what it should be and for what platforms the username would be given. Given it's a Facebook project, it might be meant for Facebook usernames, but, who knows, even they don't mention it.
So, instead of potentially breaking preexisting functionality and "taking over" a tag, they made a new one with the fediverse prefix. Seems like the safest option IMO, especially since with the fediverse prefix everyone (and every piece of code that looks for it) knows, without a doubt, that it is meant to be a fediverse username.
Experience has been pretty good both on iOS and Android. Place keeping works well on Android and I quickly tested it on iOS and it seems to work well (at least for a minute or two, I'll test it better later).
Maybe give it another shot?
edit: iOS 18 dev beta. PWAs on iOS had notification support since one of the iOS 16 versions.
@BeAware@social.beaware.live I've thought about playing on 2b2t but the queue times without paying are so insane that I just give up. As I do not want to spend money on the fast queue, I might just think up of some weird remote desktop solution in order to offload MC (& the queue) to a different machine.
@BeAware@social.beaware.live I agree and I think people should be made aware of these kinds of things especially if the user themselves can make a change. I also think more tools should be made for privacy. Just wanted to point out that expecting privacy is a bit dumb on the internet as a whole, even with measures taken :) (but the more swiss cheese slices you add, the better!!)
@BeAware@social.beaware.live Well, Google has done so in order to get around Chinese censorship (started redirecting google.cn to google.com.hk). I would call them a legitimate business.
Also, on the topic of Google, search engines sell your posts as well! They're usually free for users, but API access is always paid. Google had a paid API, Bing has it, Kagi has it, etc. That means that currently I can pay Kagi to return a post of yours, based on a query, with a snippet (granted, not the full thing). Same goes for enterprise - always paid.
Now, from what I can see, the website doesn't inspire trust, their tactics are invasive and it either intentionally doesn't respect opt-out sometimes (& instance blocking) or has a few bugs that conveniently aren't fixed. So, I don't like the execution. I do like the idea however - index and provide alerts based on keywords. If one is made that is much less invasive, more trustworthy and respects opt-out, I would have no problem with it. Charging for API access and Enterprise is also fine since that kind of service requires infrastructure that isn't exactly cheap.
In summary: Pricing model seems fair to me, and I like the idea but their execution (invasiveness, dubious respect for opt-out & trustworthiness) is bad and I think if it either fixes its flaws or a competitor is made, I would have no problem with it.
@BeAware@social.beaware.live Nah, just rightfully skeptical. If scrapers didn't exist I'd say he has a valid point that giving your data to random servers isn't great, but since scrapers have been around forever, that is already happening!
As someone already replied to one of his quote posts, treat everything you post as something that will stay on the internet forever, because most likely it will due to scrapers, etc.
@BeAware@social.beaware.live I was going through DMs and found the fediseer one, so decided to endorse since why not. Think of it as a small apology for making you think your posts take up 85 GB haha.
@BeAware@social.beaware.live@bnewbold.net@bsky.brid.gy To me it seems like they're right. Whilst (at a quick glance) you can't host your own UI, the PDS acts as a backend that you can connect to through clients (something like Akkoma), and I remember that iOS had alternative bluesky clients.
So yeah, it doesn't go through bsky servers to log in and do stuff (apart from the client itself), but since most users are on the Bluesky server, it has to interact with it for content (similar to a self hosted instance with mastodon.social).
Maybe it's not like that though, idk, I don't have any PDS's to test it on.
Back when I ran a Latvian instance I thought about making an LV relay but then there were like 4 LV instances (incl. mine) and basically only one wasn't de jure or de facto single-user, so no real point in that.
@BeAware@social.beaware.live Yeah but big tech companies aren't exactly helping by making search engines with AI (especially if they then market themselves as a scientific-esque engine with good references etc).
@BeAware@social.beaware.live Is it that fedicraft server I saw you reply to a few days ago? Regardless, I imagine you can ask the mods to consider enabling it, perhaps theres other players who also would like it.
If not, one way I've minimised my anxiety is by using Xaero's Minimap which has death waypoints.
Iirc you did mention that you like vanilla+ and not heavily modded, but I personally would consider this mod a vanilla+ mod, as it just adds a very helpful utility (waypoints are so useful).
Though I did basically grow up modding both Minecraft and Elder Scrolls/Fallout so what I classify as a light mod might be heavy for some haha. I can help if needed :)
Full-stack developer, getting back into gaming with my Steam Deck.Currently working on a project involving Cloudflare Workers and IMAP, which includes writing a lib for IMAP on CF Workers - https://github.com/Exerra/cf-imapCoincidentally, starting to dislike e-mail.Latvietis 🇱🇻