There was once a time when I swore I would not buy any phone larger than 5", that was when I had a 4.7" and couldn’t find it comfortable to reach the notifications one handed on anything larger. I’m now using a 6" and swearing I will stop here. At this point I’m really tempted to just keep buying new-old-stock pixel 5’s for the rest of time because I’ve moved the goalposts too many times now.
Is there any way to connect the bsky android app to the atproto.africa relay or a third party appview that uses the atproto.africa relay? I wouldn’t mind using bsky more if there was a clone of the android app that doesn’t use the bsky relay/appview. Looking at whtwnd it appears to be just web and not native apps?
I would like to host my own PDS and access bsky through a native app using third party relay+appview, but I haven’t seen a way to do this yet.
I’m not sure if you realize, but the meme responses are to bump the post activity and increase visibility. I’ve personally fulfilled a handful of requests there and often the op doesn’t update the post, which I personally don’t care about - people are struggling and I’m happy to chip in. As it happens, I’ve given to this particular user twice.
Some foreign language communities don’t seem to have their language marked so they still show up despite my language settings, so I blocked them to make things easier.
Yes this and also scrubs and smart tests. I have 6 14TB spinning drives and a long smart test takes roughly a week, so running 2 at a time takes close to a month to do all 6 and then it all starts over again, so for half to 75% of the time, 2 of my drives are doing smart tests. Then there’s scrubs which I do monthly. I would consider larger drives if it didn’t mean that my smart/scrub schedule would take more than a month. Rebuilds aren’t too bad, and I have double redundancy for extra peace of mind but I also wouldn’t want that taking much longer either
3 is my preferred method for a couple reasons:
Splitting the crossing way into 3 parts let’s you mark the node at the kerb as kerb=*
To me it makes most sense to mark the stubs on either end of a crossing as matching the sidewalk or footpath itself as long as that stub isn’t significant enough to be it’s own path with unique properties.
Aiui, back-feeding uncurated slop is a real problem. But curated slop is fine. So they can either curate slop or scrape websites, which is almost free. So even though synthetic training data is fine, they still prefer to scrape websites because it’s easier / cheaper / free.
No problem! I don’t really do much road mapping so I’m still figuring it out, I do mostly just sidewalks and parking lots, but I’m noticing some intersections near me also have some messed up lane configurations.
Another thing that might help is ab-street, if you download the desktop version you can import an area using an overpass query and view it using the viewer program bundled with ab-street, and it lets you click on segments and view where the turns connect from and to. It might not be 100% accurate but it’s another thing that helps to debug. I found that a road near me shows up in ab-street with the wrong number of lanes which pointed me to an issue.
I have no clue about the whole problem, but I looked at what I think is the first issue where it looks like it tells you to turn left where the sliplane splits to go right into the shred right parking lot.
My guess is that turn:lanes is supposed to be tagged immediately before the intersection it applies to, and since the turn:lanes are tagged on the way before the sliplane attaches, it’s applying left|none|none to the sliplane junction, where it sees 2 outgoing ways and applies “left” to old Shakopee (going straight) and probably “none” to the sliplane. I would try removing the turn:lanes from the old Shakopee section before the sliplane but keep it on the way that is actually connected to the main intersection there.
I also noticed that there is a turn restriction for coming out of the shred right sliplane entrance and then turning 180° to go eastbound on Shakopee. Since that sliplane entrance is one way, I don’t think that turn restriction is necessary or really helps, and it might be confusing to osmand. Without that turn restriction, I don’t think it would be necessary to have the old Shakopee split into 2 ways before the sliplane and after up until the intersection, so merging those 2 segments of old Shakopee (immediately before the sliplane entrance to shred right and up until the intersection itself) might simplify things.
So I guess that’s 2 ideas that I think might fix the issue. Hopefully that works and can be applied to some of the other issues, I’m not sure about the intersection itself, I’ll have to look at it closer later.
Edit: on second thought, I think the convention is to have turn:lanes marked whenever there are turn markings on the asphalt, so I would suggest removing the turn restriction on the sliplane and merging the 2 ways on either side of where the sliplane connects - I think that way it maybe won’t try to apply the turn:lanes to the sliplane since it won’t be attached to the end of a way with turn:lanes but in the middle (I’m guessing that’s how it works). Removing the turn:lanes on the west section I think would go against the wiki guidelines. If it was necessary to have 2 segments for shakopee then a hack would be to attach the sliplane a few feet before or after where the 2 segments of shakopee join, but that shouldn’t be necessary here.
The !mutual_aid@hexbear.net community seems similar to what you’re asking for. I’m not sure if there are more similar comms on other instances but that’s just the one I know of.
Yeah I thought odometer fraud was like a serious thing, I wonder if it applies here.
The other servers do cache the content for some time yes, but if your server is based in a country not friendly to your posts then you are vulnerable to takedowns as you say and you could be inconvenienced by having the admins of your server delete your account or something.
The benefit I’m saying we have in the fediverse is that you can pick a server in a politically safe area (ie outside Turkey in this case), so they are less likely to comply, especially if they are small or don’t care about being blocked by that country (that’s usually the only thing they can do unless you have an office or staff there that can be arrested - less likely to be the case if your server is run by some dude in another country).
I’m saying that if your home server (mastodon.social) is outside of Turkey, then there is less reason for them to comply in the first place because they only risk the mastodon.social server being blocked in Turkey. That one is a bad example because they’re one of the largest, so if you want to be extra safe, you’d want to pick a server that isn’t so big so that they are less likely to care about complying with some other county that they might not have any users from.
If the server you use is based inside the country that has a problem with your content, then you’d be screwed - though all the other servers will still mirror and cache your content for a bit even if you get taken down.
The resiliency lies in the fact that you can choose to register in a country that is politically friendly towards your posts or if your home country is friendly but you want to avoid being taken down, you can self host a single user instance and refuse any requests from other countries.
I’m saying that if your home server (mastodon.social in your example) is outside of Turkey, then there is less reason for them to comply in the first place because they only risk the mastodon.social server being blocked in Turkey. That one is a bad example because they’re one of the largest and they might have a bunch of users in Turkey, so if you want to be extra safe, you’d want to pick a server that isn’t so big so that they are less likely to care about complying with some other county that they might not have any users from.
If the server you use is based inside the country that has a problem with your content, then you’d be screwed - though all the other servers will still mirror and cache your content for a bit even if you get taken down.
The resiliency lies in the fact that you can choose to register in a country that is politically friendly towards your posts or if your home country is friendly but you want to avoid being taken down, you can self host a single user instance and refuse any requests from other countries.
Edit: Now that I think about it, there’s also the fact that as long as the account itself isn’t limited by their home server, the content in question would be accessible through the federated copies, so if the home server isn’t within Turkey / jurisdiction and doesn’t take down the account, the country trying to take down the content would need to send takedown requests or request to geofence the content to each individual server on the entire fediverse - since the home server would be freely federating it to every server with users who follow the content, otherwise they would need to block every fediverse server and every new one every day that more pop up.
The difference is that if your home server is outside of Turkey then you can tell them to kick rocks. Bluesky probably complies because they don’t want to be blocked from Turkey. In a truly decentralized system like activitypub, only the server hosting the account / content in question risks being blocked, which means almost nothing the closer you get to a single account instance. Meanwhile every other server not in Turkey would not notice a difference.
Edit: this was under the assumption that they took it down completely, but it looks like they only geofenced it. Regardless, if they are pressured enough they would be capable of completing hiding an account worldwide, which isn’t possible with activitypub without the legal alignment of every instance’s country since bluesky on the other hand has sole control of the only relay.
I think we’ll have to agree to disagree then, I don’t think that is at all the obvious interpretation and I don’t think everyone needs to clarify where they live when talking about it to “avoid the issue”.
Imo if people making assumptions about others living in the US annoys you then you should find it more annoying when someone assumes where you live AND assumes you intended to be presumptuous about it.
Is it wrong to want to talk about the place you live in without telling people where you live? Should everyone be required to state the place they live in any time they talk about it? I don’t really see what the problem is with speaking about your place of residence without revealing where you live. I don’t get how not mentioning where you live means you assume everyone knows. Maybe you not knowing is intentional.
While I think it’s annoying when people assume others live in the US, I think it’s even more annoying to both assume people who don’t mention where they live must live in the US and also assume they intended you to know that they live in the US.
Doesn’t “as a city” just tell you who the “we” refers to? As in “we, the people of our city, need x”? That’s how I understand it.
They used nagarjuna cement
https://youtu.be/95-KgsbjZ_s